|
Dr.Web Agent should be installed under the Administrator account of the respective computer. No other anti-virus software (including other versions of Dr.Web anti-virus programs, firewalls or content filters) should be installed on the workstations of an anti-virus network managed by Dr.Web Enterprise Security Suite.
To guarantee proper operation of Dr.Web Agent on server editions of Windows OS starting from Windows Server 2016, disable Windows Defender manually using group policies. |
Dr.Web Agent can be installed on a workstation as follows:
1.Locally.
Dr.Web Agent can be installed locally on a user’s computer or mobile device by an administrator or user.
2.Remotely.
Dr.Web Agent can be installed remotely using the Control Center via LAN. This type of installation is performed by an anti-virus network administrator. Therefore, no user intervention is required.
Dr.Web Agent installation on top of Dr.Web standalone product on stations running Windows OS
If a standalone Dr.Web product version 7.x–12.x is already installed on a station, Dr.Web Agent for Dr.Web Enterprise Security Suite version 13.0 is installed as follows:
•If the Dr.Web Agent installer or installation package is launched in GUI mode on a station where a standalone product version 7.x–12.x is already installed, a corresponding installer will be launched. The user will then be prompted to enter a confirmation code and uninstall the product. After the OS reboot, the GUI version of the Dr.Web Agent installer for Dr.Web Enterprise Security Suite version 13.0 will be launched.
•If the Dr.Web Agent installer is launched in the background mode on a station where a standalone product version 7.x–12.x is already installed, no actions will be performed. In case of remote installation, the installer returns a message to Control Center that a previous version of the standalone product is already installed. In this case, you should manually remove the standalone product and install Dr.Web Agent for Dr.Web Enterprise Security Suite version 13.0 using any method.
•If the Dr.Web Agent installer is launched to install Dr.Web Agent either locally or remotely on a station with a standalone product of version13.0, the installed product will switch from the standalone mode to the centralized protection mode. After connection and authorization on Dr.Web Server, the stations can receive updates, new settings and a list of components to be installed, then a reboot may be required.
When installing Dr.Web Agent on LAN servers and cluster computers, please note the following:
•When installing Dr.Web Agents on computers used as terminal servers (Terminal Services are installed on Windows OS), in order to ensure operation of Dr.Web Agents in user terminal sessions, it is recommended to install Dr.Web Agents locally, using the Add or Remove Programs Wizard in Control Panel of the Windows OS. Remote installation in this case may cause Remote Desktop Protocol errors.
•It is not recommended to install SpIDer Gate, Office Control, SpIDer Mail and Dr.Web Firewall components on servers that perform important network functions (domain controllers, license distribution servers and etc.) to avoid possible conflicts between network services and internal components of Dr.Web anti-virus.
•Installation of Dr.Web Agent in a cluster must be performed separately for each cluster node.
•The operating principles of cluster-based Dr.Web Agents and anti-virus package are similar to those installed on a standard LAN server, therefore it is not recommended to install SpIDer Gate, SpIDer Mail and Dr.Web Firewall components on cluster nodes.
•If access to the quorum resource of a cluster is severely limited, it is recommended to exclude it from the SpIDer Guard scanning and to regularly scan the resource with Scanner either manually or by scheduling such scans.