Release Notes for AV-Desk

Dr.Web AV-Desk service is designed on a client-server software system, ensures the management of the complex anti-virus protection of clients workstations of companies specialized in providing various Internet services (Internet providers (ISP), application services providers (ASP), online banking vendors, etc.).

An aggregate of computers and mobile devices on which Dr.Web AV-Desk cooperating components are installed, represents a single anti-virus network.

Dr.Web AV-Desk anti-virus network has a client-server architecture. Its components are installed on a computers and mobile devises of users and administrators as well as on a computers that function as LAN servers. Anti-virus network components exchange information via TCP/IP network protocols. Anti-virus software can be installed (and manage them afterwards) on protected stations either via the LAN, or via the Internet.

•Dr.Web Mobile Control Center is an easy tool for administrating the anti-virus network based on Dr.Web AV-Desk. The application is designed for installation and operation on mobile devices.

•Dr.Web Repository allows to download products of Dr.Web AV-Desk from the Global Update System.

•Built-in driver of PostgreSQL external database for Dr.Web Server under Windows OS is added.

•Feature that allows Dr.Web Agents to access the Dr.Web Server via the srv protocol is added. Dr.Web Agents search Dr.Web Server service according to corresponding SRV record on DNS server. Registration of SRV record is performed during Dr.Web Server installation on a computer in an Active Directory domain.

•Procedure of Dr.Web Server installation under UNIX system-based OS is changed.

•Back up of critical data during Dr.Web Server installation with backup folder specifying is added.

•Server license key is excluded from the process of Dr.Web Server installation and operation.

•An ODBC driver is now available for connecting external databases under UNIX system-based OS.

•The SQLite3 internal built-in database is added. It id offered as a default variant during installation of Dr.Web Server.

•New network subsystem of the Dr.Web Server is added. This subsystem allows to operate with more stations without significant loss of performance.

•New Network Scanner allows to search for stations from the different domains.

•Dr.Web Server groups of stations now can be synchronized with Active Directory groups.

•Clusters of Dr.Web Servers and the cluster protocol are now supported. Via the cluster protocol, actions on Dr.Web Agents from different Dr.Web Servers can be coordinated.

•The Administrators section and the system of administrator permissions are modified.

•Structure of tools for managing the repository from the Control Center is modified.

•Revisions of Dr.Web AV-Desk products updates that can be managed from the Control Center are added.

•Licenses from one license key now can be distributed between several Dr.Web Servers.

•Centralized replacement of encryption public key on Dr.Web Agents either manually or scheduled is added.

•Dr.Web Agents now may connect to the Dr.Web Server with no encryption public key or with incorrect encryption public key.

•Primary group now can be changed when a stations is automatically allowed to access the Dr.Web Server.

•PAM authorization of administrators in the Control Center is now supported under UNIX system-based OS.

•Testing of external administrators authorization settings for Active Directory, LDAP and RADIUS systems is added.

•Archived log files of the Dr.Web Server and neighbor Dr.Web Servers now can be downloaded via the Control Center.

•New Backup repository, Synchronization with Active Directory and Neighbor server has not been connected for a long time jobs are added to the Dr.Web Server schedule.

•Statistics reports including version in the PDF format now can be sent to an e-mail via the Dr.Web Server schedule.

•Database now can be managed via the Control Center (database cleanup, analysis).

•SQL console is added to run custom SQL queries specified by an administrator. Access to the console is regulated by administrator permissions.

•Lua console is added to run custom Lua scripts specified by an administrator. Access to the console is regulated by administrator permissions.

•New system for administrators notification that is configured via the Control Center is added.

•Stations, Server and neighbor Servers location now can be viewed on the OpenStreetMap, if geographic coordinates of the object are specified.

•Several encryption public keys now are supported for connecting Dr.Web Agents and neighbor Dr.Web Servers.

•Group or workstation configuration now can be exported, imported and propagated to other groups and stations of anti-virus network.

•New Dr.Web Server FrontDoor Plug-in is added for connecting of Dr.Web Server remote diagnostic utility.

•Anti-virus network statistics and some other data now can be exported to a PDF file.

•Anti-virus components settings for stations now can be exported and imported from the Control Center to an XML file.

•The location of unapproved stations in the Control Center is changed. Unapproved stations now displayed in the Anti-virus Network section, in the Newbies subgroup of the anti-virus network tree. Managing of stations approving and rejecting is performed from the toolbar options of the Anti-virus Network section.

•Configuration file with connection settings for Dr.Web Agents under Android OS, OS X and Linux system-based OS now can be downloaded from the Control Center.

•Anti-virus components settings for stations and Dr.Web Agent under Windows OS that are specified in the Control Center are updated on base of the settings provided on the stations themselves.

•Anti-virus components settings for stations under UNIX system-based OS that are specified in the Control Center are updated on base of the settings of corresponding products under UNIX system-based OS.

•Facility to subscribe and view Doctor Web company news via the Control Center is added.

•Facility to configure delayed components update on workstations from the Dr.Web Server is added.

•Facility to view user sessions on stations, the list of inactive stations of anti-virus network and the list of hardware and software on stations is added.

•Facility to configure rules for automatic placing of stations to user groups is added.

•Facility to view information on results of anti-virus software update on anti-virus network stations is added.

•Restriction settings of updates receiving are extended: flexible configuration of receiving components updates from GUS, and propagation configuration of updates on stations and groups are available.

•Interface of the repository status page is improved. Feature to save a report on repository update in the PDF format is added.

•Process of groups synchronizing with Active Directory is improved. Job in the Server schedule on groups synchronizing with Active Directory is disabled by default.

•New feature to control permissions to run, stop and change settings of the workstations Preventive protection component.

•New feature to verify SSL certificate of GUS servers by user-defined certificate.

•Extended list of protected objects in the Office Control for stations under Windows OS.

•New parameter is added into station properties. A user identifier simplifies grouping of subscriptions which are registered by one user.

•New parameter is added into user groups properties. It allows user groups to represent certain organization.

•Parameters for searching the objects in the anti-virus network tree are extended.

•Dr.Web Agent for Windows OS is completely renewed to meet the present requirements for protection of workstations against viruses:

▫The subsystem of noninterruptible background scan and active threats neutralization is implemented. One of the main criteria of this subsystem operation is low consumption of system resources.

▫The preventive protection is implemented. It allows to prevent an operating system infecting from widespread threats of Trojan.Encoder, Trojan.Inject and Trojan.Winlock families.

▫The new algorithm of threats detection is implemented for threats which are packed by the packers that are currently unknown by the Dr.Web Virus-Finding Engine component.

▫The file monitor is improved to increase the performance on stations with intense filestream.

▫The 64-bit version of anti-rootkit module is implemented. It contains improved facilities for neutralization of threats that are directed on 64-bit operating systems.

▫The new version of Office control provides the facilities for administrator to block separate types of devices on a remote station and also limit the access to the Internet or a computer for specified time periods.

▫The Dr.Web Agent module settings are implemented in the single window which provides easier management for the users of the product.

•For stations under Windows OS, the full distribution kit for installation of Dr.Web Agent and all anti-virus components at a time is additionally provided (included into extra distribution kit of Dr.Web Server).

•Settings to connect to the Server are included into personal installation packages for stations under Android, Linux, OS X.

•For stations under all supported systems, the group installer is provided to perform the Dr.Web Agent installation on several stations using one installation package.

•Documentation of Dr.Web AV-Desk anti-virus network administrator is divided into tree general parts:

•Extended list of user documentation in the Help section of Dr.Web Security Control Center.

▫New feature to view the groups hierarchy when assigning a primary group via the toolbar.

▫New feature to assign a primary group for a station according to membership rules.

▫Settings of Preventive protection and Dr.Web Agent are separated in Dr.Web Security Control Center.

▫New feature to configure the operational log of Dr.Web Server via the Dr.Web Security Control Center.

▫New feature for automatic propagation of a license key to the Everyone group during adding a key via the License Manager.

▫New feature in Dr.Web Server Task Scheduler which allows you to transfer tasks from the default schedule.

▫New feature in the Task Scheduler for stations of anti-virus network which allows you to select the launch time: according to the UTC or local time at the station.

▫Redesign in calculation of stations during installation via the group installation package.

▫The system for generating installation packages for Linux and OS X sytem-based OS has been improved. The time of generation of packages has been accelerated and the amount of data in the cache has been reduced.

▫Queries via the Web API are optimized when working with administrators, stations and groups.

▫The documentation in the Help section of Dr.Web Security Control Center is updated.

▫Fixed an error due to which an administrator with limited permissions were allowed to rollback the Server to a backup copy.

▫Resolved an issue that might have caused the appearance of incorrect information on error types and applied actions in the Threats and Errors statistic tables.

▫Third-party software libraries within Dr.Web Server software are updated to eliminate possible errors and critical vulnerabilities.

▫Resolved an issue that caused in some cases an error of the Quarantine section in Dr.Web Security Control Center.

▫Fixed an error of saving settings for administrator notifications on stations events.

▫Resolved an issue that in some cases might have caused degraded performance of Dr.Web Server and Dr.Web Security Control Center during multi-threaded processing of tasks.

▫Resolved issues that might have appeared when collecting information about hardware and software of stations.

▫Resolved an issue that might have caused failure of SQLite3 database file reduction during cleanup on Servers under Windows OS. New feature to change memory mapped database file via Dr.Web Security Control Center is added.

▫Fixed an error that in some cases might have caused problems with the approval of new stations on Dr.Web Server.

▫Resolved an issue that caused an error during downloading/uploading of large files via the Repository content and Quarantine sections of Dr.Web Security Control Center.

▫Resolved an issue that occurred when counting the number of stations in the anti-virus network on request via Web API. In particular, when transmitting data to Dr.Web Mobile Control Center.

▫Time to live of configuration files for stations under Android OS is now unlimited.

▫The package of administrative documentation is updated. The list of supported languages is extended.

▫Resolved an issue that caused in some cases the inability to view the Permissions stations section.

▫Fixed incorrect default settings in the Preventive protection section for stations under Windows OS.

▫Resolved an issue that caused incorrect handling of settings for traffic limitations during Dr.Web Agents update.

▫Resolved an issue of loading personal installation packages from the Server for stations under Linux OS and OS X.

▫Fixed an error that caused incorrect change of installing components list for stations with user tariffs.

▫Fixed an error that caused in some cases abnormal termination of connection between Dr.Web Agents and Dr.Web Server.

▫Time to live of links for downloading personal installation packages for stations under Android OS is now unlimited.

▫The package of administrative documentation is updated. The list of supported languages is extended.

▫Fixed an error that caused in some cases incorrect downloading from the Server of personal installation packages for stations under Linux OS and OS X.

▫Fixed errors in administrative permissions for operations with Dr.Web Server via Web API.

▫New feature to specify limitations on scan priority and computer resources usage when configuring a task to scan stations in the schedule.

▫Fixed an error that forbade to specify juridical tariff during approving a station access by administrator.

▫Resolved an issue that caused incorrect generating of emails contents for installation packages mailing.

▫Fixed errors in managing of administrative accounts and also, errors in administrative permissions.

▫Fixed an error of displaying the Status section when simultaneously selecting stations and groups.

▫Fixed an error that caused in some cases the inability to install Dr.Web Agents via Dr.Web Proxy Server.

▫Resolved an issue that may cause updates speed drop or inability to update Dr.Web Agents from Dr.Web Server.

▫Fixed an error that caused the inability to install Dr.Web Agents on some stations.

•Dr.Web Server should be installed on a computer that have an access to the Internet to receive updates from Dr.Web GUS (Global Update System) automatically;

It is allowed to propagate updates by any other way to the Servers which are not connected to the Internet. Particularly, in multiserver configuration of anti-virus network, it is possible to receive updates from the GUS by only one Server with subsequent distribution to other Servers, or to use the Dr.Web Repository Loader additional utility to download updates from the GUS with subsequent distribution to Servers.

•anti-virus network computers should have access to the Dr.Web Sever or to the Proxy server;

•for interaction between the anti-virus components, the following ports must be opened on used computers:

Port numbers	Protocols	Connection directions	Purpose
2193	TCP	•incoming, outgoing for the Server and Proxy server •outgoing for the Agent	For connection between the Server and anti-virus components and for interserver communications. Also is used by Proxy server to establish a connection with clients.
	UDP	incoming, outgoing
	UDP	incoming, outgoing	For the Network Scanner.
139, 445	TCP	•incoming for the Server •incoming, outgoing for the Agent •outgoing for the computer on which the Control Center is opened	For the Network Installer.
139, 445	UDP	incoming, outgoing	For the Network Installer.
9080	HTTP	•incoming for the Server •outgoing for the computer on which the Control Center is opened	For Dr.Web Control Center.
9081	HTTPS		For Dr.Web Control Center.
10101	TCP		For Server remote diagnostic utility.
80	HTTP	outgoing	For receiving updates from GUS.
443	HTTPS	outgoing	For receiving updates from GUS.

To install Dr.Web Server 10, your computer must meet the following requirements:

Component	Requirement
CPU and operating system	The following operating systems installed on a computer with corresponding CPU are supported: •CPU that supports SSE2 instructions and has 1,3 GHz or faster clock frequency: ▫Windows®; ▫Linux®; ▫FreeBSD®; ▫SolarisTM x86. •V9 UltraSPARC IIIi CPU or later: ▫SolarisTM Sparc. Complete list of supported OS see in the Appendices document, in Appendix A.
RAM	•Minimal requirements: 1 GB. •Recommended requirements: 2 GB and more.
Free disk space	Up to 12 GB: up to 8 GB for a built-in database (installation catalog) and up to 4GB for the system temporary catalog (for work files). Depending on the Server settings, additional space may required to store temporary files, e.g. to store personal installation packages of Agents (app. 8,5 MB for each) in the var\installers-cache subfolder of the Dr.Web Server installation folder. To install the Server, it is required on Windows OS system disk or in the /var/tmp for UNIX system-based OS (or in the other temporary files folder, if it is redefined), not dependently on the Server installation folder, at least 1,2 GB for the general distribution kit and 2,5 GB for the extra distribution kit of free system disk space to launch the installer and unpack temporary files.
Other	For the installation of Dr.Web Server for UNIX system-based OS, the following libraries are required: lsb v. 3 or later, glibc v. 2.7 and later. To use PostgreSQL DB, the libpq is required. To use Oracle DB, the libaio is required. Additionally under FreeBSD OS, the compat-8x library is required.

Component	Requirement
CPU	Intel® Pentium® III 667 MHz or faster.
RAM	not less than 1 GB.
Free disk space	not less than 1 GB.
Operating system	•Windows®; •Linux®; •FreeBSD®; •SolarisTM. Complete list of supported OS see in the Appendices document, in Appendix A.
Other	For the installation of Proxy Server for UNIX system-based OS: lsb v. 3 or later. Additionally under FreeBSD OS, the compat-8x library is required.

Web browser	Support
Windows Internet Explorer 8 and later	Supported
Mozilla Firefox 25 and later
Google Chrome 30 and later
Opera® 10 and later	Allowed to be used, but operating is not guaranteed.
Safari® 4 and later	Allowed to be used, but operating is not guaranteed.

For the Windows Internet Explorer web browser, please note the following features:

▫Full operability of the Control Center under web browser with the Enhanced Security Configuration for Windows Internet Explorer mode enabled is not guaranteed.

▫If you install Server on a computer with a '_' (underline) character in the name, configuration of Server with Dr.Web Security Control Center by use of Windows Internet Explorer will not be available. In this case, use other web browser.

▫For proper operation of Control Center, IP address and/or DNS name of a computer with installed Dr.Web Server must be added to the trusted sites of a web browser, on which you open the Control Center.

▫For proper opening of Control Center via the Start menu under Windows 8 and Windows Server 2012 OS with tiled interface, set the following parameters of a web browser: Tools → Programs → Opening Internet Explorer set the Always in Internet Explorer flag.

b)To use Dr.Web Security Control Center in full, Dr.Web Security Control Center extension must be installed. The extension is distributed with the Server installation package. It installs by browser request when you use elements of Dr.Web Security Control Center which require the extension (for instance, for anti-virus components remote updater or Network Scanner).

•For operation of Dr.Web Security Control Center extension at the Network Scanner page, under both Windows and GNU/Linux OS, you must have administrator (root) rights.

•Under Mozilla Firefox and Google Chrome web browsers, Dr.Web Security Control Center extension is available under Windows OS and Linux system-based OS only.

Web browser	Minimal supported version	Maximal supported version
Windows Internet Explorer	8	11
Mozilla Firefox	25	50.0.1
Google Chrome	30	44.0.2403

c)Recommended screen resolution to use Dr.Web Security Control Center is 1280x1024 pt.

Operating system

Requirement

Operating system version

Device

iOS

iOS® 7 and later

Apple® iPhone®

Apple® iPad®

Android

Android 4.0 and later

–

To install Dr.Web Agent and full anti-virus package of 10 version, your computer must meet the following requirements:

Requirements are differ depending on the operating system on which anti-virus solution is installed (the full list of supported OS see in the Appendices document, in Appendix A):

Component	Requirement
CPU	1 GHz CPU or faster.
Free RAM	Not less than 512 MB.
Free disk space	1 GB for executable files + extra disk space for logs and temporary files.
Other	1.The Dr.Web Agent for Windows context help requires Windows® Internet Explorer® 6.0 or later. 2.For Dr.Web for Outlook extension the Microsoft Outlook client from the Microsoft Office package is required: •Outlook 2000; •Outlook 2002; •Outlook 2003; •Outlook 2007; •Outlook 2010 SP2; •Outlook 2013; •Outlook 2016.

Component	Requirement
CPU	32-bit (IA-32, x86) and 64-bit (x86-64, x64, amd64) Intel platforms.
Free RAM	Not less than 512 MB.
Free disk space	Not less than 400 MB of free disk space on a volume on which Anti-virus folders are placed.

•OS X, Android OS, Novell NetWare OS: configuration requirements coincide with the requirements for operating system.

•Before updating, it is recommended to check the validity of TCP/IP protocol configuration for the Internet access. Particularly, DNS service must be enabled and properly configured.

•In multiserver anti-virus network configuration, consider that interserver updates transmission is not performed between Servers of 10 version and Servers of previous versions and interserver connection is used for transmission statistics only. To provide interserver updates transmission, you must upgrade all Servers. If you need to remain Servers of previous version as a part of the anti-virus network to connect the Agents installed on operating systems which are not supported by the 10 version (see Upgrading Dr.Web Agent), when Servers of 6.XX versions and Servers of the 10 version must receive updates independently.

•After upgrade of anti-virus network Servers is completed, you must configure encryption and compression settings for the connected Servers (see the Administrator Manual, the Setting Connections between Several Dr.Web Servers section).

•During automatic upgrade of Agents, the old version of Agent is deleted and the new version is installed.

Attention! Between the removal of an old Agent version and installing of a new version, stations will have no anti-virus protection.

•Upgrading the Server within version 10 can be also performed via the Control Center. The procedure is described in the Administrator Manual, in the Updating Dr.Web Server and Restoring from the Backup section.

•Not all Server updates within version 10 have the distribution kit file. Some of them can be installed via the Control Center only.

Upgrading of the Server from the 6 version to the 10 version and within version 10 is performed automatically by the means of the installer.

After the Server of 6.X version has been removed, the following files are automatically saved:

File	Description	Default folder
agent.key (name may vary)	Agent license key file	etc
certificate.pem	SSL certificate
drwcsd.conf (name may vary)	Server configuration file
drwcsd.pri	private encryption key
enterprise.key (name may vary)	Server license key file
private-key.pem	RSA private key
dbinternal.dbs	embedded database	var
drwcsd.pub	public encryption key	webmin\install

After the Server of 10 version has been removed, the following files are saved into the backup folder only if the Back up Dr.Web Server critical data option was set:

File	Description	Folder
agent.key (name may vary)	Agent license key file	<backup>
drwcsd.pub	public 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 10 installation, the file is absent
frontdoor.conf	configuration file for the Server remote diagnostic utility
proxy.conf	proxy server configuration file
auth-ads.conf	configuration file for administrators external authorization via Active Directory	•<backup> •<backup>/dbBackup/<version>/
auth-ldap.conf	configuration file for administrators external authorization via LDAP
auth-radius.conf	configuration file for administrators external authorization via RADIUS
download.conf	network settings for generating of the Agent installation packages
drwcsd.conf (name may vary)	Server configuration file
drwcsd.pri	private encryption key
webmin.conf	Dr.Web Security Control Center configuration file
dbexport.gz	database export	<backup>/dbBackup/<version>/
drwcsd.conf.distr	Server configuration file template with default parameters
openssl.cnf	Server certificate for HTTPS

If you are planning to using configuration files from the previous version of the Server, please note:

2.To use internal database and configuration files of the Server and Control Center from the previous version of the Server, they must be converted by the means of the installer. Using of these files from the previous version in original is not supported. You cannot replace these files with a backup copy.

If necessary, copy other critical files you want to preserve to another folder, other than Server installation folder. For instance, report templates which are stored in the \var\templates folder.

Attention! The MS SQL CE database starting from the 10.0 version of Dr.Web Server is no longer supported. During automatic Server upgrade by the means of the installer, the MS SQL CE database is automatically converted to the IntDB internal database.

For Servers with external DB, it is recommended to use standard tools supplied with the database.

Make sure, that Dr.Web AV-Desk DB export completed successfully. If DB backup copy is not available, the Server could not be restored in emergency case.

1.Run the distribution file. A window for selecting the language to run the installation wizard will be opened. Select English and click Next.

2.If on a computer on which you are installing the Dr.Web Server software, the Dr.Web Agent software with enabled self-protection is installed, the wizard prompts you what Dr.Web self-protection component is active. Disable this component via the Agent settings and click ОК to continue, or click Cancel to cancel Server upgrading.

3.The InstallShield Wizard window with information about the program to be installed will be opened. Click Next.

4.The Dr.Web Server Upgrade Notes window displays, which notifies you on the previous Dr.Web Server version installed.

The installation wizard automatically locates the Server installation folder, configuration files and internal DB location from the previous installation.

5.A window with the text of the license agreement will be opened. When you read the agreement, to continue the upgrading, select I accept the terms of the license agreement and click Next.

6.On the following steps of the installation wizard, the upgrading Server is configured as at the installing Dr.Web Server (see Installation Manual) process based on the configuration files from the previous installation (see above). If necessary, you can change locations of the files which were found automatically by the installer.

For the external Server database, also select Use existing database during upgrade.

If you are going to use the Oracle DB as an external database via the ODBC connection, then during upgrading of the Server, in the installer settings, select the Custom option of the installation and in the next window disable the installation of built-in client for corresponding DBMS (in the Database support section).

Otherwise, interaction with the Oracle DB via ODBC will fail because of the libraries conflict.

7.To remove the Server of the previous version and launch the installation process of the 10 version of the Server, click Install.

After upgrading the Dr.Web Server according to the general procedure, perform the following to ensure normal operation of Dr.Web Security Control Center:

1.Clear cache of the Web browser that is used to connect to Dr.Web Security Control Center.

Upgrading the Server software of the previous version to version 10 is possible not for all UNIX system-based OS. Thus, under UNIX system-based OS, in which upgrading is not supported, it is recommended to delete the Server software of previous versions saving the backup copy and install the 10 version based on the saved backup copy.

Upgrading the Server software within version 10 for the same package types is performed automatically.

After the Server of 6.X version has been removed, the following files are automatically saved:

File	Description	Default folder
agent.key (the name may vary)	Agent license key file	•for Linux OS and Solaris OS: /var/opt/drwcs/etc •for FreeBSD OS: /var/drwcs/etc
certificate.pem	SSL certificate
download.conf	network settings for generating of the Agent installation packages
drwcsd.conf (the name may vary)	Server configuration file
drwcsd.pri	private encryption key
enterprise.key (the name may vary)	Server license key file
private-key.pem	RSA private key
webmin.conf	Dr.Web Security Control Center configuration file
common.conf	configuration file (for some UNIX system-based OS)
local.conf	Server log settings
dbinternal.dbs	embedded database	•for Linux OS and Solaris OS: /var/opt/drwcs/ •for FreeBSD OS: /var/drwcs/
drwcsd.pub	public encryption key	•for Linux OS and Solaris OS: /opt/drwcs/webmin/install •for FreeBSD OS: /usr/local/drwcs/webmin/install

After the Server of 10 version has been removed, the following configuration files are automatically saved to the default backup folder:

File	Description	Default folder
agent.key (the name may vary)	Agent license key file	/var/tmp/drwcs/
certificate.pem	SSL certificate
download.conf	network settings for generating of the Agent installation packages
drwcsd.conf (the name may vary)	Server configuration file
drwcsd.pri	private encryption key
enterprise.key (the 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 10 installation, the file is absent
frontdoor.conf	configuration file for the Server remote diagnostic utility
private-key.pem	RSA private key
webmin.conf	Dr.Web Security Control Center configuration file
common.conf	configuration file (for some UNIX system-based OS)
local.conf	Server log settings
dbexport.gz	database export
drwcsd.pub	public encryption key

After the automatic upgrade for Linux OS and Solaris OS, the following files are also saved:

File	Description	Default folder
auth-ldap.conf	configuration file for administrators external authorization via LDAP	/var/tmp/drwcs/
auth-pam.conf	configuration file for administrators external authorization via PAM
auth-radius.conf	configuration file for administrators external authorization via RADIUS

If you are planning to use configuration files from the previous version of the Server, please note:

2.The internal database is upgraded and configuration files of the Server is converted by the means of the installer. You cannot replace these files with a backup copies when upgrading to the Server 10.

If necessary, save other files that you are planning to use in the sequel in another location.

For Servers with external DB, it is recommended to use standard tools supplied with the database.

Make sure, that Dr.Web AV-Desk DB export completed successfully. If DB backup copy is not available, the Server could not be restored in emergency case.

If you update the Server from 6.0 and later versions to 10 version for Linux and Solaris OS, instead of deleting old version and installing new version of the Server, you can use the package update of the Server. For this, launch the installation of corresponding Server package.

All automatically saved files will be stored in corresponding directories and manual replacement is not required.

Figure below illustrates the reinstallation procedure of Dr.Web Server for UNIX system-based OS.

Detailed description of upgrading procedure declared in Dr.Web AV-Desk Administrator manual.

To upgrade Dr.Web Security Control Center extension, delete Dr.Web Security Control Center extension software of current versions and install the new version.

Deletion of the the Dr.Web Control Center Plug-in is described in the Installation Manual, Uninstalling the AV-Desk Software for Windows® OS section.

Installation is described in the Installation Manual, Installing the Dr.Web Security Control Center extension section.

1.Agents must be installed on a computers under Windows OS which are supported for the installation of Agents for Dr.Web AV-Desk version 10 (see the Appendices document, Appendix A. The Complete List of Supported OS Versions).

2.For the automatic upgrade, the following actions are possible depending on the Server settings:

a)Automatic upgrade is performed, if during the Server upgrade, encryption keys and network settings from the previous Server were saved.

•Between the removal of an old Agent version and installing of a new version, stations will have no anti-virus protection.

•After upgrading of the Agent, the anti-virus software operation will be limited without the station restart. At this, the complete anti-virus protection of the station is not provided. User must restart the station on the Agent demand.

2.A popup notification with restart request is displayed on the station. User must restart the station.

4.After the Agent upgrade is completed, the station automatically connects to the Server. In the Status section of the Control Center, the notification on required restart will be displayed for the upgraded station. The popup notification with restart request is displayed on the station. User must restart the station on the Agent request.

Automatic upgrade of the Agent with manual configuring is performed by the following procedure:

1.Configure settings for connection to the new Server and replace public encryption key on station manually.

2.After changing of the settings on the station and connecting the stations to the Server, the Agent upgrade process starts.

4.A popup notification with restart request is displayed on the station. User must restart the station.

6.After the Agent upgrade is completed, the station automatically connects to the Server. In the Status section of the Control Center, the notification on required restart will be displayed for the upgraded station. The popup notification with restart request will be displayed on the station. User must restart the station on the Agent request.

If installation of the new version of the Agent during automatic upgrade failed for any reason, the next installation attempts are not performed. No anti-virus software will be installed on the station, and such station will be displayed as offline in the Control Center.

In such case, you must install the Agent by yourself. At this, after the new Agent installation, you must merge the new station and the old station in the Control Center, in the hierarchical tree of the anti-virus network.

If Agents are installed on stations under OS which are not supported for the installation of Agents for Dr.Web AV-Desk version 10, actions to upgrade are not performed.

Agents installed on unsupported OS cannot receive updates (including virus bases updates) from the new Server. If you need to remain Agents under unsupported OS, you must leave the Server of previous version to which these Agents are connected as a part of the anti-virus network. At this, Servers of 6.XX versions and Servers of the 10 version must receive updates independently.

Recommendations on upgrading the Agents, installed at the stations that implement significant LAN functions, specified in the Appendices document, p. Upgrading Dr.Web Agents on the LAN servers.

Agents installed on stations under Linux system-based OS, Android OS and OS X connect to the Server of the 10 version with complete support of updating process in the following cases:

1.Agents must be installed on a computers under operation systems which are supported for the installation of Agents for Dr.Web AV-Desk version 10 (see the Appendices document, Appendix A. The Complete List of Supported OS Versions).

2.Encryption keys and network settings from the upgraded Server must be set on the stations.

If you encounter any issues installing or using company products, before requesting for the assistance of the technical support, take advantage of the following options:

If you have not found solution for the problem, you can request direct assistance from Doctor Web company technical support by one of the following ways:

This document is the property of Doctor Web. No part of this document may be reproduced, published or transmitted in any form or by any means for any purpose other than the purchaser's personal use without proper attribution.

Dr.Web, SpIDer Mail, SpIDer Guard, CureIt!, CureNet!, AV-Desk and the Dr.WEB logo are trademarks and registered trademarks of Doctor Web in Russia and/or other countries. Other trademarks, registered trademarks and company names used in this document are property of their respective owners.

In no event shall Doctor Web and its resellers or distributors be liable for errors or omissions, or any loss of profit or any other damage caused or alleged to be caused directly or indirectly by this document, the use of or inability to use information contained in this document.