Lists of frequently asked questions
Getting distributions and installing them
Obtaining a distribution
Distributions can be obtained:
- Using the Control Center (see the documentation). Starting with Dr.Web Enterprise Security Suite version 13.0, remote installation is available via ssh (for more information refer to the section "Remote Installation of Dr.Web Agent on UNIX system-based OS").
- Using the official Dr.Web repository.
- Using the Download Wizard on the official website (a serial number is required).
How to obtain a distribution via the Control Center
- Create a station according to the instructions in the official documentation.
- To create a station, save:
- The install.cfg configuration file containing the target station’s connection details to Dr.Web Server (login/password of the target station, key (certificate), and server address).
- If necessary, a personal distribution of the product to be installed (in this case, the .run archive will already include the install.cfg file and the .sh script for automatically connecting to the server).
Installing and connecting end stations to Dr.Web Server
The standard installation method — via the command line using the drweb-ctl utility.
Note: Dr.Web anti-virus for Linux can be installed and connected to Dr.Web Server via the graphical interface (if available). The parameters for connection and authorisation on the Server are entered in the “Mode” tab, which is on the Dr.Web Anti-virus for Linux window's settings page.
For more information about connecting in the graphical interface, refer to the official documentation.
If necessary, you can connect the installed product to Dr.Web Server as soon as the installation is complete. A previously installed anti-virus can also be connected to Dr.Web Server.
The utility "help" feature:
drweb-ctl esconnect -h
Options for connecting an existing station:
- Connect the station as a new one. In this case, the settings of the group to which it is assigned will be applied to it:
- Connect the station as an already existing one and get the existing settings:
drweb-ctl esconnect 192.168.1.1 --Certificate /path/to/certificate/drwcsd-certificate.pem --newbie
192.168.1.1 should be replaced with the actual Server address.
Drwcsd-certificate.pem — Server certificate.
drweb-ctl esconnect --CfgFile /path/to/configuration/file/install.cfg
If there is no CfgFile key, the option exists to load the certificate of the Server drwcsd-certificate.pem and execute drweb-ctl esconnect with the full set of parameters for this station:
drweb-ctl esconnect 192.168.1.1 --Certificate /path/to/certificate/drwcsd-certificate.pem --Login 52068a12-e1f2-413a-060a-000000000000 --Password password
192.168.1.1 should be replaced with the actual Server address.
Drwcsd-certificate.pem — Server certificate.
52068a12-e1f2-413a-060a-000000000000 should be replaced with the actual Station ID.
Working with universal .run packages
The entire text of this section refers to the following Dr.Web products:
- Dr.Web Anti-virus for Linux
- Dr.Web for UNIX Internet Gateways
- Dr.Web for UNIX Mail Servers
- Dr.Web for UNIX File Servers
When is it desirable to install the universal .run package?
- If your version of the OS distribution supports neither .deb nor .rpm.
- If the mandatory use of certified assemblies is required.
- If a user wants to perform an installation on a station with no external network access.
In all other cases, the easiest way to install a product is from the repository.
Installation of the universal .run package
Remote installation of .run packages is available via ssh for the following products (for more information refer to the documentation):
- Dr.Web Anti-virus for Linux
- Dr.Web for UNIX File Servers
For Dr.Web Enterprise Security Suite Server (hereinafter, "Dr.Web Server") version 12.0 and later, select the appropriate check boxes in the repository settings. To enable this feature, an extra package (also known as an extra distribution kit) must be installed on Dr.Web Server version 11.0. Find out more about the extra package in the documentation.
Installation of the extra Dr.Web Server distribution kit is carried out according to the instructions and does not require the Server to be stopped.
To perform the installation in this way, you must be able to:
- Connect to a remote station via ssh.
- Elevate privileges on the remote station.
This installation method has two important restrictions:
- Remote installation of the Agent is not available on a computer running the Server from which the installation process is started.
- The installation time may exceed the duration of the session due to the large amount of data. If the session expires before the installation is complete, the process will be terminated automatically and the packages will not be installed.
Dr.Web Server's pre-configuration to receive .run packages:
The path to the required settings is shown in the example of Dr.Web Enterprise Security Suite 13.0.
- In the settings Administration → General repository configuration → Dr.Web installation packages → Dr.Web corporate products, find the desired product on the list:
- Dr.Web Anti-virus for Linux
- Dr.Web for UNIX File Servers.
Next to the found product, select the appropriate check box (you are thus allowing it to be uploaded to the repository).
Next, you need to expand its content and make sure that the check boxes for the required OSs (Linux, FreeBSD) and assemblies for the required platforms are selected.
After that, .run packages can be distributed via http(s). Section address (https://*:9081/install/unix/workstation), where * is the address of Dr.Web Server.
For more information about installing the universal package, refer to the official documentation..
Remote installation of universal .run packages
Remote installation of .run packages is available via ssh for the following products (for more information refer to documentation):
- Dr.Web anti-virus for Linux
- Dr.Web anti-virus for UNIX file servers
For Dr.Web Server version 12.0 and later, select the appropriate check boxes in the repository settings (for more information refer to the instructions). To enable this feature, an extra package (also known as an additional distribution package) must be installed on Dr.Web Server version 11.0. Find out more about the extra package in the documentation.
Installation of the additional Dr.Web Server distribution package is carried out according to the instructions and does not require the Server to be stopped.
How does the type of installation (via a universal package or directly from the repository) affect further product operation?
The selected method of initial installation affects how further updates are obtained. After installing Dr.Web anti-virus for Linux using any of the possible ways, the package manager automatically connects to the Dr.Web package repository. This can cause problems when installing the universal .run package on a station that lacks access to an external network. In this case, the solution is to temporarily disconnect from the repositories during the installation process.
If you encounter any difficulties with the repositories after installing the .run package, please contact our technical support.
Updating databases
By default, the virus databases are updated automatically if you have Internet access.
Updating packages and components (within a current version)
During the initial installation from the repository, the components will be automatically updated from it (provided that automatic updating is allowed and the station has access to it).
If the installation was performed from the universal .run package, the ability to get automatic updates from the repository depends on the specifics of the user's operating system. In this case, updating from Dr.Web Server actually means installing a new .run package over the existing one. The Dr.Web Enterprise Security Suite repository and the repository https://repo.drweb.com, to which the package manager is connected, are different objects with different content.
If a product installed using the .run package is not updated automatically
In this case, the zypper package manager (included in the installed Dr.Web anti-virus for Linux package) should be used to perform a manual update. If this method is not suitable for some reason, you should apply the update commands of the package manager used in your OS.
Updating using zypper, included in the product in Linux distributions, is performed by the following commands:
# /opt/drweb.com/bin/zypper refresh
# /opt/drweb.com/bin/zypper update
For FreeBSD:
# /usr/local/libexec/drweb.com/bin/zypper refresh
# /usr/local/libexec/drweb.com/bin/zypper update
At the same time, repo.drweb.com should be available from the station where the updating process is launched.
Details and examples of commands can be found in the official documentation.
Upgrading to a new version
If a new version of Dr.Web anti-virus for Linux is released, packages containing its components are placed in the section of the Dr.Web repository that corresponds to the new version. In this case, the package manager should be switched to the new section of the Dr.Web repository (for more information refer to "Upgrading to a new version").
Receiving updates on stations without Internet access
A utility for creating a local update mirror is available so that updates can be received on isolated stations. Instructions on its use and more information on this topic can be found here.
Updating the databases of a product installed directly from the repository on an isolated station
The updating process is performed as follows: updates are downloaded to a computer connected to the Internet, copied to a USB drive or network drive, and then installed on another computer that is not connected to the Internet.
The updating process is performed via the command line.
Instructions for receiving updates
- On a computer connected to the Internet, run the following command:
- Copy the received updates to a USB drive or a network drive.
- Mount a network drive or a USB drive on the computer on which you want to install updates. If you receive updates from a USB drive, you will need to run the following commands:
- Install updates using the following command:
$ drweb-ctl update --Path <path to the directory to which updates will be downloaded>
# mkdir /mnt/usb
# mount <path to device> /mnt/usb
$ drweb-ctl update --From /mnt/usb
You can also download new .rpm packages on any other PC with access to https://repo.drweb.com and then transfer them to the target station.
Updating the databases of a product installed from the universal .run package on an isolated station
In this case, the zypper package manager (included in the installed Dr.Web anti-virus for Linux package) should be used. If this method is not suitable for some reason, you should apply the update commands of the package manager used in your OS.
Conditions for the example shown below: there is a second station with Internet access and a .run package installed on it.
- Checking the content of the repository (without updating) for Linux:
- Download everything new by listing all the packages in the command (for Linux):
- Transfer this entire directory with all the attachments to the station with the product that needs updating. The name and path to the directory on the target station are of no importance (for example /tmp/1).
Then, enter the following command (for Linux) on the isolated station:
# /opt/drweb.com/bin/zypper up
For FreeBSD:
# /usr/local/libexec/drweb.com/bin/zypper up
The answer “N” to the question "Continue? [y/n/...? display all parameters] (y):" will complete the command without installing updates.
# /opt/drweb.com/bin/zypper download …
For FreeBSD:
# /usr/local/libexec/drweb.com/bin/zypper download ...
After that, all updates for our run package are available in the catalogue /var/opt/drweb.com/cache/zypp/packages/drweb-11.1/ (for Linux) or /var/drweb.com/cache/zypp/packages/drweb-11.1/ (for FreeBSD).
# /opt/drweb.com/bin/rpm -Uhv /tmp/1/*
For FreeBSD:
# /usr/local/libexec/drweb.com/bin/rpm -Uhv /tmp/1/*
Nothing found
