Table of Contents
Advertisement
Distributing Agents to Manage Systems
Distributing agents
Enabling the agent on unmanaged McAfee products
Use this task to enable agents on existing McAfee products in your environment.
Before purchasing ePolicy Orchestrator, you may have already been using McAfee Enterprise
products in your network. Some of the more recent McAfee products that use the AutoUpdate
updater, such as VirusScan Enterprise, install with the agent in a disabled state. 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 instead of deploying the 3.63MB agent installation package
saves significant network bandwidth.
NOTE:
You cannot change the agent installation folder without removing and reinstalling the
agent. Agents that you enable may be in a different folder than agents that you deploy in your
network by another method.
Assigning sorting filters or NT domain names to the desired System Tree segments saves
valuable time.
You must copy the SITELIST.XML repository list file from the ePO server to the desired systems.
The repository list contains network address information the agent requires to call in to the
server after being installed.
Task
For option definitions, click ? on the page displaying the options.
1
Export the repository list (SITELIST.XML) from the Master Repository page to a temporary
folder on the system, such as
2
Run this command on the desired system:
FRMINST.EXE /INSTALL=AGENT /SITEINFO=C:\TEMP\SITELIST.XML
/SITEINFO
Reference the SITELIST.XML file in the temporary folder. By default, the FRMINST.EXE file
is installed in this location:
C:\PROGRAM FILES\MCAFEE\COMMON FRAMEWORK
NOTE:
Existing McAfee products were most likely installed with an older version of the
agent. These agents are not automatically upgraded to the latest version that is on the
ePO server. Enable and run a deployment task configured to upgrade the enabled agent
on the managed system.
Including the agent on an image
Use this information to install the agent using an image. The first time the user logs on to a
system built using a common image that includes the agent, the system is assigned a unique
ID called a global unique identifier (GUID).
CAUTION:
Before creating an image for this purpose, remove the agent GUID registry value
from the agent registry key. A GUID is regenerated on the first ASCI with the ePO server.
This is a desirable method to use when:
• Your organization uses standard installation images for new systems.
• You have access to some systems in your environment only when they are brought in for
repair.
78
McAfee ePolicy Orchestrator 4.0.2 Product Guide
C:\TEMP
is the location of the SITELIST.XML file that you exported.
.
Advertisement
Table of Contents
