2.3. Installing Dr.Web Enterprise Agent under Windows® OS

 

Enterprise Agent should be installed under Administrator account of the respective computer.

 

If Enterprise Agent is installed on the computer, you must uninstall the Agent before the installation.

 

Enterprise Agent and the anti-virus package can be installed in two ways:

1.Remotely – on the Server through the network. Performed by the anti-virus network administrator. No user interference required. You can find detailed description in the Remote Installation of the Dr.Web Enterprise Agent (for Windows® OS) section.

2.Locally – directly on the user’s machine. May be performed both by the administrator or the user. For installation, you can use the following files (see Installation Files for details):

esinst.exe Installation Package.

drwinst Agent Network Installer.

For installation of Enterprise Agent on LAN servers and cluster computers, consider the following:

For installation on computers which implement terminal servers functions (the Terminal Services are installed on Windows OS), to provide Agents operation in user's terminal sessions, Agents software must be installed locally, via the Add or Remove Programs Wizard on Control Panel of Windows OS.

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

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 scan by the SpIDer Guard and confine by regular checks of the resource via Scanner launched by scheduler or manually.