Contents
Recommendations on Administration Server installation
This section contains recommendations on how to install Administration Server. This section also provides scenarios for using a shared folder on the Administration Server device in order to deploy Network Agent on client devices.
Creating accounts for the Administration Server services on a failover cluster
By default, the installer automatically creates non-privileged accounts for services of Administration Server. This behavior is the most convenient for Administration Server installation on an ordinary device.
However, installation of Administration Server on a failover cluster requires a different scenario:
- Create non-privileged domain accounts for services of Administration Server and make them members of a global domain security group named KLAdmins.
- In the Administration Server Installer, specify the domain accounts that have been created for the services.
Selecting a DBMS
When installing Administration Server, you can select the DBMS that Administration Server will use. When selecting the database management system (DBMS) to be used by an Administration Server, you must take into account the number of devices covered by the Administration Server.
The following table lists the valid DBMS options, as well as the restrictions on their use.
Restrictions on DBMS
DBMS |
Restrictions |
|---|---|
SQL Server Express Edition 2012 or later |
Not recommended if you intend to run a single Administration Server for more than 10,000 devices or to use Application Control. |
Local SQL Server edition, other than Express, 2012 or later |
No limitations. |
Remote SQL Server edition, other than Express, 2012 or later |
Only valid if both devices are in the same Windows domain; if the domains differ, a two-way trust relationship must be established between them. |
Local or remote MySQL 5.5, 5.6, or 5.7 (MySQL versions 5.5.1, 5.5.2, 5.5.3, 5.5.4, and 5.5.5 are no longer supported) |
Not recommended if you intend to run a single Administration Server for more than 10,000 devices or to use Application Control. |
Local or remote MariaDB Server 10.3, MariaDB 10.3 (build 10.3.22 or later) |
Not recommended if you intend to run a single Administration Server for more than 20,000 devices or to use Application Control. |
If you are using SQL Server 2019 as a DBMS and you do not have cumulative patch CU12 or later, you have to perform the following after installing Kaspersky Security Center:
- Connect to SQL Server using SQL Management Studio.
- Run the following commands (if you chose a different name for the database, use that name instead of KAV):
USE KAVGOALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFFGO - Restart the SQL Server 2019 service.
Otherwise, using SQL Server 2019 may result in errors, such as "There is insufficient system memory in resource pool 'internal' to run this query."
Concurrent use of the SQL Server Express Edition DBMS by Administration Server and another application is strictly forbidden.
Specifying the address of the Administration Server
When installing Administration Server, you must specify the external address of the Administration Server. This address will be used as the default address when creating installation packages of Network Agent. After that, you will be able to change the address of the Administration Server host by using Administration Console tools; the address will not change automatically in Network Agent installation packages that have been already created.