Deployment scenarios - best practices

The following chapters cover deployment scenarios for different network environments.

Best practices for deployment of ESET Security Management Center

Number of clients

Up-to 1,000 clients

1,000 - 5,000 clients

5,000 - 10,000 clients

10,000 - 50,000 clients

50,000 - 100,000 clients

100,000+ clients**

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 replication interval (during deployment phase)

60 seconds*

5 minutes

10 minutes

15 minutes

20 minutes

25 minutes

Recommended replication interval (after deployment, during standard usage)

10 minutes

10 minutes

20 minutes

30 minutes

40 minutes

60 minutes

* Default replication interval of ESET Management Agent. Adjust the replication interval to fit your infrastructure. We recommend that you keep the total number of Agent - Server connections below 1000 per second for high-performance hardware configuration.

** See our recommendations for hardware in the Infrastructure building and sizing chapter

Single Server (Small Business)

To manage small networks (1,000 clients or less), a single machine with ESMC Server and all ESMC components installed on it is usually sufficient. You can think of it as a single server or standalone installation.

Remote Branches with Proxies

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

High Availability (Enterprise)

For enterprise environments (for example, 100,000 clients), additional ESMC components should be employed:

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

SQL database can be implemented on a separate server or Failover Cluster.

ESMC Server can be set up on a Failover Cluster