Deployment Task; Update Tasks - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

®
ePolicy Orchestrator 3.6 Walkthrough Guide

Deployment task

Update tasks

2 If using global updating, nothing else is necessary provided global updating has
been configured and enabled.
If not using global updating, use a replication task to copy the contents of the master
repository to the distributed repositories.
3 If not using global updating, create and schedule an update or deployment task for
agents to retrieve and install the update on managed systems.
Once you have checked in the product deployment package, you can use the
deployment task to install the product on managed systems. The deployment task is a
unique client task created automatically when ePolicy Orchestrator installs. It installs
any product that is deployable through ePolicy Orchestrator and has been checked into
the master repository.
Best practices information
You can run the product deployment task at any site, group, or individual system. When
deciding how to stage your product deployment, McAfee recommends considering the
size of the package and the available bandwidth between the master or distributed
repositories and the managed systems. In addition to potentially overwhelming the
ePolicy Orchestrator server or your network, deploying products to many systems can
make troubleshooting problems complicated.
Consider a phased roll-out to install products to groups of systems at a time. If your
network links are fast, try deploying to several hundred client systems at a time. If you
have slower or less reliable network connections, try smaller groups. As you deploy to
each group, monitor the deployment, run reports to confirm successful installations,
and troubleshoot any problems with individual systems.
If you chose to deploy server-based McAfee products, deploy them to specific systems,
rather than groups or sites.
Once an update package has been checked into the master repository and replicated
to the distributed repositories, the agents on the managed systems still need to know
when to go to the distributed repositories for updates. This is unnecessary if you are
using global updating.
You can create and configure client update tasks to control when and how managed
systems receive update packages. If you are not using global updating, creating these
client update tasks are the only way you can control client updating with ePolicy
Orchestrator.
If you are using global updating, a client update task is unnecessary, although you can
create a daily client update task for redundancy.
43
Deploying the Agent and Products
About deploying and updating products
4