Dr.Web Server Management under Windows OS

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 Dr.Web Server.

Elements for configuration and management Dr.Web Server are placed during the installation to the Programs main Windows OS menu, to the Dr.Web Server folder:

•The Dr.Web Server control folder contains the following commands:

▫Detailed logging—set the All level of detail for the Dr.Web Server operation log.

▫Start—start the Dr.Web Server service.

▫Stop—stop the Dr.Web Server service.

▫Reload repository—reread the Dr.Web Server repository from disk.

▫Reload templates—reread the administrator notifications templates.

▫Restart—restart the Dr.Web Server service.

▫Verify database—start the verification of the embedded database.

▫Default logging—set the Information level of detail for the Dr.Web Server operation log.

Corresponding commands are described in detail in the Appendices document, G2. Dr.Web Agent for Windows.

•The Web interface item opens Dr.Web Security Control Center and connects to Dr.Web 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 Dr.Web 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 Dr.Web 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 Dr.Web 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.

General Configuration Files

Start and Stop Dr.Web Server

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 Dr.Web Server installation folder (see also the Appendices document, G3. Dr.Web Server):

▫drwcsd start—start Dr.Web Server.

▫drwcsd restart—total restart of the Dr.Web Server service.

▫drwcsd stop—normal shutdown of Dr.Web Server.