McAfee EPOLICY ORCHESTRATOR 4.5 Product Manual page 76

Distributing Agents to Manage Systems
Installing the McAfee Agent
The force installation option is not available if Install only on systems... is selected.
NOTE:
including policies, tasks, events, and logs before the new agent is installed.
Enabling and disabling the agent on unmanaged McAfee products
Before acquiring ePolicy Orchestrator, you might have already been using McAfee products in
your network. Some of the more recent McAfee products that use AutoUpdate, such as VirusScan
Enterprise, are installed with the agent in updater mode. To start managing these products
with ePolicy Orchestrator, you can enable the agent that is already on the system.
Enabling the agent on each system saves significant network bandwidth over deploying the
agent installation package. However, existing McAfee products were probably installed with an
older version of the agent, and these agents are not automatically upgraded to the latest
version on the ePO server.
In some situations, you may want to convert a system that has been managed by ePolicy
Orchestrator to updater (unmanaged) mode. Information is provided for converting from
managed mode to unmanaged mode.
Use these tasks to enable agents on existing McAfee products in your environment so that they
work with ePolicy Orchestrator or to disable management of systems by ePolicy Orchestrator.
Tasks
Converting the agent mode from unmanaged to managed mode in Windows
Converting the agent mode from unmanaged to managed on UNIX-based platforms
Converting the agent mode from managed to unmanaged mode in Windows
Converting the agent mode from managed to unmanaged on UNIX-based platforms
Converting the agent mode from unmanaged to managed mode in Windows
Use this task to convert the agent from unmanaged (updater) mode to managed mode in a
Windows environment.
Before you begin
Before converting the agent mode, consider the following:
• By default, the FrmInst.exe file is installed in this location:
FRAMEWORK
• You should not change the agent installation folder without removing and reinstalling the
agent. Agents that you enable might be in a different folder than agents that you deploy in
your network by another method.
• Assigning sorting filters or domain names to specific System Tree segments saves time.
Without such designations, systems are placed in Lost&Found and you will have to move
them from that location.
• You must copy the SiteList.xml (repository list file) from the ePO server to the target systems.
The repository list contains network address and other information that the agent requires
to call in to the server after being installed.
• SiteList.xml must be in the same location as srpubkey.bin and reqseseckey.bin.
76 McAfee ePolicy Orchestrator 4.5 Product Guide
If you use the force installation option, the agent is removed in its entirety,
.
C:\PROGRAM FILES\MCAFEE\COMMON