Installing Dr.Web Agent

Dr.Web Agent can be installed on a workstation by one of the following ways:

1.Locally.

Local installation is performed directly on a user’s computer or mobile device. Installation may be implemented either by administrator or by user.

2.Remotely.

Remote installation is performed from the Control Center through via LAN. Installation is implemented by an anti-virus network administrator. Therefore, no user involvement is required.

Dr.Web Agent installation over Dr.Web standalone product on stations under Windows OS

If a standalone Dr.Web product of 7.x-12.x version is already installed on a station, Agent for Dr.Web Enterprise Security Suite version 13.0 is installed in the following way:

•If the Agent installer or installation package is launched in GUI mode on a station with standalone product of 7.x-12.x version already installed, the installer of corresponding version of installed product will start. After this, a user is prompted to enter a confirmation code and uninstall the product. After the OS reboot, the GUI version of Agent installer for Dr.Web Enterprise Security Suite version 13.0 is launched.

•If the Agent installer is launched in background mode on a station with standalone product of 7.x-12.x version already installed, this will not incur any actions. In case of remote installation, the installer returns a message to Control Center about standalone product of a previous version being already installed. In this case, you must remove the standalone product manually and install Agent for Dr.Web Enterprise Security Suite version 13.0 by any of available ways.

•If the Agent installer is launched for local or remote installation on a station with standalone product of version 13.0, the installed product switches from standalone mode to centralized protection mode. After connection and authorization on Dr.Web Server, new updates, settings and a list of installing components can be received, which may or may not require a reboot.

For installation of Dr.Web Agent on LAN servers and cluster computers, consider the following:

•For installation on computers which implement terminal server functions (the Terminal Services are installed on Windows OS), to provide Agents operation in user's terminal sessions, Agents software is recommended to be installed locally, via the Add or Remove Programs Wizard on Control Panel of Windows OS. Remote installation in this case can cause Remote Desktop Protocol errors.

•It is not recommended to install SpIDer Gate, Office Control, SpIDer Mail and Dr.Web Firewall components on servers which implement significant network functions (domain controllers, license distribution servers and etc.) to avoid probable conflicts between network services and internal components of Dr.Web anti-virus.

•Installation of the Agent on a cluster must be performed separately on each cluster node.

•The operation principles for Agents and anti-virus package on the cluster node are similar to those on a standard LAN server, thus, it is not recommended to install SpIDer Gate, SpIDer Mail and Dr.Web Firewall components on cluster nodes.

•If access to quorum resource of a cluster is severely restricted, it is recommended to exclude it from the SpIDer Guard scanning and confine by regular checks of the resource via Scanner launched by scheduler or manually.