Dr.Web ES Agent establishes connection to the centralized protection server (for example, to Dr.Web Enterprise Server), which allows the network administrator to implement common security policy within the network, in particular, configure the same scanning settings and reaction on threat detection for all network stations and servers. Moreover, the centralized protection server also performs a role of an internal update server on the network, as it stores up-to-date virus databases, (in this case, updating is performed via Dr.Web ES Agent, is not used).
When connecting Dr.Web ES Agent to the centralized protection server, the agent ensures receipt of up-to-date settings for the program components and the license key file, which are then transmitted to the configuration daemon for applying them to managed components. Moreover, the component also receives tasks to scan file system objects on the station (including scheduled tasks).
Dr.Web ES Agent collects and sends the server statistics on detected threats and applied actions.
To connect Dr.Web ES Agent to the centralized protection server, the password and identifier of the host (“station” in terms of the Centralized protection server) are required, as well as the public encryption key file, which is used by the server for authentication. Instead of the station identifier, you can specify the identifier of the main and tariff groups where the station is to be included. For required identifiers and public key file, contact the administrator of your anti-virus network.
Moreover, if this option is allowed on the centralized protection server, you can connect your host with the protected server (“workstation”) as a “newbie”. In this case, after the administrator confirms the request to connect, the centralized protection server automatically generates an identifier and a password, and sends them to the agent for future connections.