Installation Files

Installation Packages

Personal Installation Package

After a new stations account is created in the Control Center, a personal installation package for Dr.Web Agent installation is generated. Personal installation package contains Dr.Web Agent installer and the set of parameters for connecting to the Server and for authorization of the station at the Server.

Personal installation packages are available for protected stations under all operating systems which are supported by Dr.Web Enterprise Security Suite. At this, installation packages are generated in the Control Center in base of the Agent installer. Parameters for connecting to the Server and for authorization of the station at the Server are included into installation packages directly.

warning

To have installation packages for operating systems other that Windows OS, you must install extra distribution kit of Dr.Web Server first.

 

Download link for Dr.Web Agent personal installation package for the concrete station is available:

1.After creating of a new station (see the 11 step in the Creation of a New Station Account section).

2.In any time after station creation:

in station properties,

in the Selected objects section for the station selected in hierarchical list.

Group Installation Package

Group installation package of the Agent is generated in the Control Center for installation on stations of a certain user group. At this, you can install the Agent on all stations under the same OS from the one group installation package.

Group installation package contains Dr.Web Agent installer, the set of parameters for connecting to the Server and also the identifier and the password of the user group into which the station will be included after the Agent installation. But parameters for the authorization of the station at the Server and anti-virus components are not included into the group installation package composition.

Download link for group installation package is available in the user group properties.

Installers

Agent installer differs from the installation package that it does not contain parameters for connecting to the Server and for authorization of the station at the Server.

The following types of Dr.Web Agent installers are provided:

For stations under Windows OS, two type of installers are available:

drwinst.exe Network Installer performs the installation of the Agent only. After connecting ti the Server, the Agent downloads and installs necessary anti-virus package components. It is possible either local or remote installation of the Agent via the network installer.

The drwinst.exe Agent network installer resides in the webmin/install folder (the shared hidden resource by default) of Dr.Web Server installation folder. Network sharing at the 10 step during Dr.Web Server installation is set. You can change this resource further.

drweb-11.05.2-<build>-esuite-agent-full-windows.exe Full Installer performs the installation of the Agent and anti-virus package at a time.

For stations under Android OS, Linux OS, macOS, installers for Dr.Web Agent installation similar to the stand-alone version are available.

Dr.Web Agent installers are available on the installation page of Dr.Web Security Control Center.

warning

To have installers for operating systems other that Windows OS, and also for the full installer under Windows OS, you must install extra distribution kit of Dr.Web Server first.

 

Installation Page

At the installation page of Dr.Web Security Control Center you can download:

1.Dr.Web Agent installer.

Installers for protected stations under all operating systems which are supported by Dr.Web Enterprise Security Suite are located in corresponding named folders.

2.The drwcsd.pub public encryption key.

3.The drwcsd-certificate.pem Server certificate.

From any computer with network access to the Server, installation page is available at the following address:

http://<Server_address>:<port_number>/install/

where <Server_address> is the IP address or DNS name of the computer on which Dr.Web Server is installed. And the <port_number> should be 9080 (or 9081 for https).