Dr.Web Server Interface and Management
As a rule, Dr.Web Server can be managed via Dr.Web Security Control Center which acts as an interface for the Server.
Elements for configuration and management the Server are placed during the installation to the Programs main Windows OS menu, to the Dr.Web Server folder:
•The Server control folder contains the following commands:
▫Detailed logging—set the All level of detail for the Server operation log.
▫Start—start the Server service.
▫Stop—stop the Server service.
▫Reload repository—reread the Server repository from disk.
▫Reload templates—reread the administrator notifications templates.
▫Restart—restart the Server service.
▫Verify database—start the verification of the embedded database.
▫Default logging—set the Information level of detail for the Server operation log.
|
After the execution of the Detailed logging and Default logging commands, the service must be restarted to apply changes. For this, run the Restart command. |
|
Extended logging settings are available in the Log section of the Control Center. |
Corresponding commands are described in detail in the Appendices document, p. H3. Dr.Web Server.
•The Web interface item opens Dr.Web Security Control Center and connects to the Server installed at this computer (at the http://localhost:9080).
•The Documentation item opens administrator documentation in HTML format.
Dr.Web Server folder has the following structure:
Default installation folder (can be changed during the installation): C:\Program Files\DrWeb Server
•bin—Dr.Web Server executable files.
•ds-modules—unpacked script modules.
•etc—general configuration files of anti-virus network components.
•fonts—fonts for PDF documents.
•var—contains the following subfolders:
▫backup—backups of DB and other critical data.
▫extensions—scripts of user hooks meant to automate the performance of certain tasks.
▫file-cache—file cache.
▫installers-cache—cache to store Agent personal and group installation packages when stations are created via the Control Center. Created at installation packages creation.
▫plugins—temporary plug-ins objects.
▫objects—Control Center objects cache.
▫reports—temporary folder for generating and storing reports. Created when necessary.
▫repository—repository folder to store actual updates of virus bases, anti-virus packages files and anti-virus network components. It contains subfolders for the program components software which include subfolders for their versions depending on the OS. The folder should be accessible for writing to the user under which the Server is launched (the LocalSystem as a rule).
▫sessions—Control Center sessions.
▫tmp—temporary files.
▫twin-cache—unpacked virus bases for backward compatibility with previous versions of Dr.Web Agents. Also, can contain other unpacked repository files, e.g., the Agent installer.
▫upload—folder to download temporary files which are specified via the Control Center. Created at large files downloading.
•vfs—packed script modules and language packages.
•webmin—Control Center elements.
•websockets—web sockets scripts.
Backup folder (can be changed during the deinstallation): <installation_drive>:\Drweb Backup.
|
The content of the updates catalog \var\repository is automatically downloaded from the updates server through HTTP\HTTPS protocol according to the Server schedule, or the anti-virus network administrator can manually place the updates to the catalog. |
General Configuration Files
File |
Description |
Default folder |
|---|---|---|
agent.key (name may vary) |
Agent license key |
etc |
certificate.pem |
SSL certificate |
|
database.conf |
database settings template with default parameters |
|
download.conf |
network settings for generating of the Agent installation packages |
|
drwcsd.conf (name may vary) |
Server configuration file |
|
drwcsd.conf.distr |
Server configuration file template with default parameters |
|
drwcsd.pri |
private encryption key |
|
enterprise.key (name may vary) |
Server license key file. The file is saved if it presented after the upgrade from the previous versions. For the new Server 12.0 installation, the file is absent |
|
frontdoor.conf |
configuration file for the Server remote diagnostic utility |
|
http-alerter-certs.pem |
certificates for verification the apple-notify.drweb.com host for sending push notifications |
|
private-key.pem |
RSA private key |
|
yalocator.apikey |
API key for the Yandex.Locator extension |
|
webmin.conf |
Control Center configuration file |
|
auth-ads.conf |
configuration file for administrators external authorization via Active Directory |
|
auth-ldap.conf |
configuration file for administrators external authorization via LDAP |
|
auth-ldap-rfc4515.conf |
configuration file for administrators external authorization via LDAP using the simplified scheme |
|
auth-radius.conf |
configuration file for administrators external authorization via RADIUS |
|
database.sqlite |
embedded database |
var |
drwcsd.pub |
public encryption key |
webmin\install |
By default, Dr.Web Server automatically starts after installation and every time after restarting the operating system.
Also you can start or start, restart or stop Dr.Web Server by one of the following ways:
•General case:
▫Using the corresponding command, located in the Start → Programs → Dr.Web Server menu.
▫Via the services management tools in the Administrative Tools section at the Control Panel of Windows OS.
•Stop and restart via the Control Center:
▫In the Administration section, use buttons: 
to restart, 
to stop.
•Using the console commands run from the bin subfolder of the Server installation folder (see also the Appendices document, p. H3. Dr.Web Server):
▫drwcsd start—start the Server.
▫drwcsd restart—total restart of the Server service.
▫drwcsd stop—normal shutdown of the Server.
|
Please note, if you need the Server to read environment variables, the service must be rebooted via the services management tools or via the console command. |