McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual page 96

®
ePolicy Orchestrator 3.6 Walkthrough Guide
4 Repeat these steps for other sites.
The agent installations begin immediately.
Deploying agents to systems running Windows 95, Windows
98, or Windows Me
When deploying agents to systems running Windows 95, Windows 98, or Windows
Me remember that the installation does not complete until the next time the system
logs back onto the network. If, after logging off and back into the Windows 95,
Windows 98, or Windows ME client systems, the agent still does not appear, wait 10
minutes, then try deploying it again. If that still does not work, you can install the agent
manually at the client system (see
page 94).
Deploying to systems outside the local NT domain
If the other site(s) contain systems residing in a different NT domain than your ePolicy
Orchestrator server, you may need to specify other domain administrator credentials
for the target domain.
Before deploying the agent, deselect
box, and type an appropriate user name and password with domain administrator rights
in the target domain.
Monitoring the agent installations
It may take up to 20 minutes for all the agents to be installed on all systems in your test
sites, and for the console tree to update with the new covered status. In the meantime,
you can check the ePolicy Orchestrator server for events, which can alert you of failed
agent installations. To view server events:
1 In the console tree of the ePolicy Orchestrator console, right-click your server and
Server Events
select .
Server Event Viewer
2 Skim the
displayed here, but failed installs are.
When agent deployment is complete and the agents have called back to the server for
the first time, the systems in your Directory are marked with green checks.
If the agents have installed and the Directory does not reflect this, manually refresh the
Directory by right-clicking Directory and selecting
not show the systems as managed until they call back to the server, usually within 10
minutes. This is true even though the agent is installed and running on the client
systems.
You can also watch the installation from any of your client systems. The default policy
suppresses the installation interface (which we did not change when we set agent
policies in this example). So you cannot see the installation interface. However, you can
open the Task Manager on the client system and watch the CPU usage spike briefly as
the installation begins. Once the agent is installed and running, two new services
Processes
appear in the window:
because of how we modified the agent policies before deploying, the agent icon
appears in the system tray after installing and reporting back to the server.
Installing agent manually on client systems on
Use ePO server credentials
for events. Successful agent installations are not
Refresh
. Note that the Directory does
and
UPDATERUI.EXE FRAMEWORKSERVICE.EXE
93
Installing and setting up
Install Agent
on the dialog
. Also,
8