Connecting Clients to Dr.Web Server

In order to connect to Dr.Web Server, a client must have a Dr.Web Server certificate regardless of whether the traffic between Dr.Web Server and the client is encrypted or not.

For Dr.Web Agents to work in centralized mode with a connection to Dr.Web Server, one or more trusted certificates from Dr.Web Servers, to which Dr.Web Agent can connect, must be present on the station.

A certificate that was used during installation and certificates received centrally from Dr.Web Server are stored in the registry; however, the certificate files themselves are not used.

A single copy of the certificate can be added to the Dr.Web Agent installation folder (but not to the registry) and to the shared list of certificates using a command line switch. This certificate is used, among other things, to be able to connect to Dr.Web Server in case of an error in the central settings.

If the certificate is missing or invalid, Dr.Web Agent will not be able to connect to Dr.Web Server; however, it will remain operational and will update using the Mobile mode if it is allowed for this station.

When installing Dr.Web Agent, a Dr.Web Server certificate must be present on a station together with the selected installation file.

If you run the installation package generated in the Control Center, the certificate is included in the installation package and you do not need to additionally specify the certificate file.

After Dr.Web Agent is installed, the certificate data is written to the registry and the certificate file itself is no longer used.

If the certificate is missing or invalid, the installer will not be able to install Dr.Web Agent (applies to all types of the Dr.Web Agent installation files).

When establishing a connection between neighboring Dr.Web Servers, it is necessary to specify the certificate of the Dr.Web Server to which a connection is established on each Dr.Web Server to be configured (see the Administrator Manual, section Setting Connections between Several Dr.Web Servers).

If at least one certificate is missing or invalid, you will not be able to establish a multi-server connection.

To connect the Proxy Server to Dr.Web Server with the option of remote control via the Control Center, you need to have a certificate on the station where the Proxy Server is installed. In this case the Proxy Server can also support encryption.

If the certificate is missing, the Proxy Server will continue to work; however, remote control, encryption and caching will not be available.

When upgrading an entire anti-virus network from a previous version that uses public keys to a new version that uses certificates, no other additional actions are required.

It is not recommended to install Dr.Web Agent bundled with Dr.Web Server version 11 and connect it to Dr.Web Server version 10 and vice versa.