Connecting Clients to Dr.Web Server

To be able to connect to Dr.Web Server, a client must have the Dr.Web Server certificate not depending on the encryption of traffic between Dr.Web Server and a client.

For the centralized mode of the Agents with connection to the Dr.Web Server, the station must have one or several trusted certificates from Dr.Web Server to which the Agent can be connected.

Certificate that was used at installation and certificates received in the centralized settings from Dr.Web Server are stored in the registry but the files of certificates are not used.

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

If the certificate is absent or the certificate in invalid, the Agent will not be able to connect to Dr.Web Server but will remain operating and updating in the Mobile mode if it is allowed for this station.

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

If you launch the installation package generated in the Control Center, the certificate is included into the installation package and additional specifying of the certificate file is not required.

After the Agent installation, the certificate data are written into the registry and the certificate file itself is no longer used.

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

When establishing a connection between neighbor Dr.Web Servers of version 11 and later, on each configuring Dr.Web Server you must specify the certificate of the Dr.Web Server connection to which connection is establishing (see the Administrator Manual, p. Setting Connections between Several Dr.Web Servers).

If at least one certificate is absent or invalid, you will not be able to establish the multiserver connection.

To connect the Proxy Server to Dr.Web Server with possibility of remote control via the Control Center, you must have a certificate on a station with the Proxy Server installed.

At this, the Proxy Server can also support encrypting. If the certificate is absent, the Proxy Server will continue its operation but remote control and also encryption and caching will not be available.

In case of general update of the 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.

Installation of the Agent distributed with Dr.Web Server of version 11 and connecting it to Dr.Web Server of version 10 and vice versa is not recommended.