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

100,000+

ESMC Server & Database Server on the same machine

x

x

x

Use of MS SQL Express

x

x

x

x

Use of MS SQL

Use of MySQL

x

x

x

Use of ESMC Virtual Appliance

Not Recommended

x

x

x

Use of VM server

Optional

x

x

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.

See the Web Console configuration for enterprise solutions.

Configure your HTTP Proxy for high number of clients.