Deployment recommendations

Best practices for deployment of ESET Security Management Center

Number of clients

Up to 1,000

1,000 - 5,000

5,000 - 10,000

10,000 - 50,000

50,000 - 100,000


ESMC Server & Database Server on the same machine




Use of MS SQL Express





Use of MS SQL

Use of MySQL




Use of ESMC Virtual Appliance

Not Recommended




Use of VM server




Recommended connection interval (during deployment phase)

60 seconds

5 minutes

10 minutes

15 minutes

20 minutes

25 minutes

Recommended connection interval (after deployment, during standard usage)

10 minutes

10 minutes

20 minutes

30 minutes

40 minutes

60 minutes

Connection interval

ESMC Server is connected to the ESET Management Agents using permanent connections. Despite the permanent connection, data transmission occurs only once during the connection interval. For example, if the replication interval on 5,000 clients is set to eight minutes, there are 5,000 transmissions in 480 seconds, 10.4 per second. Make sure to set the appropriate client connection interval. Make sure to keep the total number of Agent - Server connections below 1,000 per second even for high-performance hardware configurations.

If a server is overloaded or there is a malware outbreak (for example, we connect 20,000 clients to a server only able to service 10,000 clients at an interval of every 10 minutes), it will skip some of the connected clients. Not connected clients will try to connect to the ESMC Server later.

Single Server (Small Business)

To manage small networks (1,000 clients or less) use a single machine with ESMC Server and all ESMC components installed on it. In SMB / small network environments, we encourage you to consider a Linux ESMC installation or virtual appliance where applicable.

Remote Branches with Proxies

If client machines do not have direct visibility on the ESMC Server, use a proxy to forward the ESET products communication. HTTP Proxy is not aggregating the communication or lowering the traffic of replication.

High Availability (Enterprise)

For enterprise environments (over 10,000 clients), consider the following:

RD Sensor helps to search your network and discover new computers.

ESMC Server can be set up on a Failover Cluster.

Configure your HTTP Proxy for high number of clients.


Web Console configuration for enterprise solutions or low performance systems

By default, the ESMC Web Console installed via All-in-one installer for Windows reserves a memory limit of 1024 MB for Apache Tomcat.

You can change default Web Console configuration based on your infrastructure:

In enterprise environment, the default Web Console configuration can suffer from instability when working with a high number of objects. Change the Tomcat settings to prevent memory shortages. Make sure your system has enough RAM (16 GB or more) before making these changes.

If you have a low performance system with limited hardware resources, you can decrease the Tomcat memory usage.



Memory values provided below are recommendations. You can adjust the Tomcat memory settings based on your hardware resources.


1.Open the tomcat9w.exe or run the Configure Tomcat application.

2.Switch to Java tab.

3.Change the memory usage:

a.Increase (enterprise): Change the values Initial memory pool to 2048 MB and Maximum memory pool to 16384 MB.

b.Decrease (low-performance systems): Change the values Initial memory pool to 256 MB and Maximum memory pool to 2048 MB.

4.Restart the Tomcat service.


Linux and ESMC Virtual Appliance

1.Open the Terminal as root or use sudo.

2.Open the file:

a.ESMC Virtual Appliance / CentOS: /etc/sysconfig/tomcat

b.Debian: /etc/default/tomcat9

3.Add the following line to the file:

a.Increase memory usage (enterprise): JAVA_OPTS="-Xms2048m -Xmx16384m"

b.Decrease memory usage (low performance systems): JAVA_OPTS="-Xms256m -Xmx2048m"

4.Save the file and restart the Tomcat service.
service tomcat restart