Below is a sample batch file that checks whether the agent is installed and, if it is not, runs
the FRAMEPKG.EXE to install the agent.
IF EXIST “C:\Windows\System32\ePOAgent\NAIMAS32.EXE”
\\<COMPUTER>\<FOLDER>\UPDATE$\FRAMEPKG.EXE /FORCEINSTALL /INSTALL=AGENT
IF EXIST “C:\ePOAgent\FRAMEWORKSERVICE.EXE” GOTO END_BATCH
\\MyServer\Agent\UPDATE$\FRAMEPKG.EXE /FORCEINSTALL /INSTALL=AGENT
:END_BATCH
NOTE:
The installation folders for your distribution may be different than in this example,
depending on where you have specified to install the agent.
This example checks:
• The default installation location of the older agent version 2.5.1 and, if present, upgrades
it to the agent version 3.5.
• The default installation folder for the agent version 3.5 and, if not present, installs the
new agent.
4
Save the EPO.BAT batch file to the
NETLOGON$
folder of your primary domain controller
(PDC) server. The batch file runs from the PDC every time a system logs on to the network.
5
Add a line to your login script that calls the batch file on your PDC server. This line would
look similar to this example:
CALL \\PDC\NETLOGON$\EPO.BAT
Each system runs the script and installs the agent when it logs on to the network.
Installing the agent manually
Use this task to run the installer locally on a system.
This is a desirable method to install agents for the following circumstances:
• Your organization requires that software is installed on systems manually.
• You intend to use ePolicy Orchestrator for policy management only.
• You have systems running Windows 95, Windows 98, or Windows ME and do not want to
enable file and print sharing on them.
• You assigned sorting filters or NT domain names when creating the segments of your System
Tree.
You can install the agent on the system, or distribute the FRAMEPKG.EXE installer for users to
run the installation program themselves.
After the agent is installed, it calls into the server and adds the new system to the System Tree.
Task
For option definitions, click ? on the page displaying the options.
1
Distribute the agent installation package to the desired system.
If you want end-users (who have local administrator rights) to install the agent on their
own systems, distribute the agent installation package file to them. You can attach it to an
email message, copy it to media, or save it to a shared network folder.
2
Double-click FRAMEPKG.EXE and wait a few moments while the agent is installed. Within
ten minutes, the agent calls in to the ePO server for the first time.
3
As needed, bypass the ten-minute interval by forcing the agent to call in with the
CMDAGENT/p
command line.
Distributing Agents to Manage Systems
Distributing agents
77
McAfee ePolicy Orchestrator 4.0.2 Product Guide
