Deploying Management Agents

The ESET Management Agent provides communication between ESMC Server and ESET security products on the client computer. The Agent must be installed with Administrator privileges because it runs as a System user application. There are multiple ways how to deploy the Agent to client computers. We highly recommend to use the hierarchical system of static groups to organize computers. You can create a structure of groups and create a custom installer for each group. The client computer is then assigned to the correct group right after the installation.

You can use the script created by the Migration tool in the previous chapter but we recommend to create a custom Live installer script and distribute it.

Once you have the installer created, you need to deploy it, either locally or remotely. There are also other ways of remote installation.

Do you need a proxy?

There are two ways of using a proxy with ESMC:

Use proxy for caching updates, installers and other files provided by ESET servers. We recommend caching when there is a higher number of clients on a local network, and you need to limit the network traffic. This method can be set up after the deployment of Agents.

Use a proxy to forward replication (connection) between ESMC Server and ESET Management Agents. We recommend forwarding only if the endpoint machines cannot reach the ESMC Server otherwise. This method does not save any traffic or bandwidth.

Combination of both functions above is also supported. First set up the HTTP Proxy and later set up the caching policy.

If the target client machine can reach the ESMC Server without proxy, you can proceed to local or remote installation. If not, see the Proxy chapter.