Administration of Dr.Web Server Repository

The repository of Dr.Web Server is designed to store benchmark copies of the anti-virus software and update them from GUS servers.

The repository deals with sets of files called products. Each product resides in a separate subfolder of the var/repository Server folder. The functions of the repository and their management are made separately for each product.

To administrate the updating in the repository product revisions are used. A revision is a correct state of product files at a certain time (including file names and checksums) and has its unique number.

Update of Repository Products

Update of the product revisions can be performed as follows:

a)Download updates to the Server from Dr.Web GUS.

The Server repository updates automatically from GUS according to tasks in the Server schedule.

•To view the tasks for repository updating, go to the General Repository Configuration section, the Task Scheduler tab.

•To change update from GUS schedule, go to the Setting Dr.Web Server Schedule section.

•To check for updates and download them manually, go to the Repository State section and click Check for updates.

b)Propagate updates between different Dr.Web Servers in a multi-server configuration.

If you have several Dr.Web Servers installed in your anti-virus network, you can configure interserver connections to transmit repository updates:

•For the parent-child type of connection, Servers receiving updates from GUS are parent, and child Servers receive all updates from parent automatically.

•For the peer-to-peer type of connection, any of them can receive updates from GUS. At this, other Servers receive all updates from it automatically.

Description of interserver connections configuration is given in the Peculiarities of a Network with Several Dr.Web Servers section.

c)Distribute updates from Dr.Web Server to workstations.

Updates of stations software are checked, downloaded from the Server, and installed on stations automatically at each connection of the Agents to the Server, and also, with some periodicity during the Agents operation (it cannot be configured and performed transparent for the administrator).

If necessary, you can configure limitations for time and traffic of the Agent updates in the Update Restrictions for Workstations section.

Configure of Repository Parameters

The repository allows the anti-virus network administrator to configure the following parameters:

•The list of product update sites in a) operations.

Parameters of connection to GUS are configured in the General Repository Configuration section.

•Restrictions to the number of products requiring synchronization of a) type.

Compound of downloaded products from GUS are configured in the General Repository Configuration and Detailed Repository Configuration sections.

Thus, administrator is enabled to track only necessary changes of certain files or categories of files.

•Restrictions to product components requiring synchronization of c) type.

Administrator of the Server an select what should be installed on the workstation. Anti-virus components list is configured in the Installing Components of the Anti-Virus Package section.

•Control of switching to new revisions.

Revisions are configured for each repository product separately in the Detailed Repository Configuration section.

Independent testing of products before installation is possible.

•Repository content management as files and folders.

The Repository Content section allows to view and manage current repository content as files and folders of repository: perform export and import either separate products or all repository content and its settings.

Composition of Repository Products

Currently, the following products are provided:

•Dr.Web administrative utilities

Utilities for all supported operation systems:

▫Dr.Web Repository Loader (graphical and console versions)

▫Digital keys and certificates generation utility

▫Dr.Web Server remote diagnostics utility

▫Dr.Web Server remote scriptable diagnostics utility

▫Dr.Web Mobile Control Center (the links to App Store and Google Play).

•Dr.Web Agent for Android

Virus databases for stations under Android OS.

•Dr.Web Agent for UNIX

Databases of built-in filters and Anti-spam, and Dr.Web Anti-spam for UNIX engine.

•Dr.Web Agent for Windows

The anti-virus components software for stations under Windows OS.

•Dr.Web Anti-spam databases

Databases of Dr.Web Anti-spam for Windows.

•Dr.Web enterprise products

Installation packages for the following products:

▫Dr.Web Agent for Windows full installer

▫Products for installation on protected stations under UNIX (including LAN servers), Android, macOS

▫Dr.Web for IBM Lotus Domino

▫Dr.Web for Microsoft Exchange Server

▫Dr.Web Proxy Server—package for separate installation of Proxy Server not connected with Dr.Web Agent for Windows

▫Dr.Web Agent for Active Directory

▫Utility for Active Directory scheme modification

▫Utility to change attributes for Active Directory objects

▫NAP Validator.

•Dr.Web Proxy Server

Software to install Dr.Web Proxy Server connected with Dr.Web Agent for Windows.

•Dr.Web Server

▫Dr.Web Server software

▫Dr.Web Security Control Center software

▫documentation.

•Dr.Web Server security data

A bundle of keys, scripts, and certificates ensuring secured update of the anti-virus network components and data exchange between Dr.Web Server and the Agents.

•Dr.Web Updater

Update module for Dr.Web Agent for Windows from version 6 to actual version.

•Dr.Web virus databases

Virus databases, anti-virus engines for stations under Windows OS and UNIX system-based OS.

•Doctor Web News

News feed from Doctor Web company website.

•Hashes of known threats

Lists of hashes of known threats.

•SpIDer Gate databases

Databases of built-in filters of anti-virus components for Windows.

•Trusted Applications

Trusted applications groups for the Application Control component for stations under Windows OS.