Restoring without Dr.Web Server Backup

To restore Dr.Web Server after the failure if no backup had been saved

1.Choose a computer to install the new Dr.Web Server. Isolate this computer from operating Agents: disconnect it from the network in which the Agents are installed or temporarily change its IP address, or use any other method you mostly prefer.

2.Install the new Dr.Web Server.

3.In the Administrating → License manager section, add the license key from the previous Dr.Web Server installation and propagate it on corresponding groups, particularly on the Everyone group. The step is obligatory if the license key was not set during the Dr.Web Server installation.

4.Update repository of the installed Dr.Web Server from the GUS:

a)Open the Administrating → Repository state section of the Control Center.

b)Click the Check for updates button to check whether updates to all of the products are available on the GUS servers and download updates, if any.

5.If new versions of the Dr.Web Server software are available, perform the update to the latest version:

a)Open Administrating → Dr.Web Server section of the Control Center.

b)To open the Dr.Web Server versions list, click the current version of Dr.Web Server or click the Versions list button. This opens the Dr.Web Server Updates section with the list of available updates and backups of Dr.Web Server.

c)To update the Dr.Web Server software, set the option next to the last version in the All versions list. Click Save.

d)Wait for the completion of the Dr.Web Server update process.

6.Change the stations connection settings in the Dr.Web Server configuration:

a)Open Administrating → Dr.Web Server configuration.

b)On the General tab, set the Reset unauthorized to newbie flag.

c)On the General tab in the Newbies registration mode drop-down list, select Allow access automatically.

d)Click Save and restart Dr.Web Server.

7.In the Anti-virus Network section of the Control Center, create user groups in the anti-virus network tree similarly with the previous version. If necessary, create automatic membership rules for stations in the created user groups.

8.If necessary, specify the Agent settings and the Dr.Web Server settings (except the temporary settings from the step 5) similarly with the previous version.

9.If necessary, change the repository settings in the Administrating → Detailed repository configuration section.

10.Restore the Dr.Web Server accessibility for the Agents according to the Dr.Web Server isolation way selected on step 1.

11.Replace the public encryption key on all stations of the network that are planned to connect to the new Dr.Web Server.

•If the self-protection is enabled, copy to a station the public key created during the new Dr.Web Server installation and run the following command:

es-service.exe -p <key>

or

es-service.exe --addpubkey=<key>

As the <key>, specify the path to the public encryption key copied to a station.

In a result, the public key will be copied to the Agent installation folder. By default, it is the %ProgramFiles%\DrWeb folder (for more details, see the Appendix H2. Dr.Web Agent for Windows).

•If the self-protection is disabled on a station, you can take the public key created during the new Dr.Web Server installation and place it into the folder specified above.

12.After all stations will be successfully connected to the new Dr.Web Server, change the Dr.Web Server settings specified on step 5 to the settings adopted according to the policy of your company.