45
ePolicy Orchestrator
®
3.6 Walkthrough Guide
Deploying the Agent and Products
About deploying and updating products
4
3
A SuperAgent wakeup call with the
SITESTAT
.
XML
file is broadcast to all agents. This
file lists the contents of the master repository. If a package the managed systems
requires is in the list, the agent goes to a distributed repository to get the package.
4
All agents go to their local distributed repositories for new updates.
Requirements
The following requirements must be met to implement global updating:
A SuperAgent is installed on each broadcast segment. Managed systems cannot
receive a SuperAgent wakeup call if there is no SuperAgent on the same broadcast
segment. Global updating utilizes the SuperAgent wakeup call to alert agents that
new updates are available.
Distributed repositories are set up and configured throughout your environment.
McAfee recommends SuperAgent repositories, but they are not required — global
updating functions with all types of distributed repositories.
If using SuperAgent repositories, managed systems must be able to “see” the
repository from which it updates. Although, a SuperAgent is required on each
broadcast segment for systems to receive the wakeup call, SuperAgent repositories
are not required on each broadcast segment, but the managed systems must “see”
the SuperAgent repository from which to update.
Pull tasks
Use pull tasks to update your master repository with DAT and engine update packages
from the source repository. DAT and engine files must be updated often. McAfee
releases new DAT files daily and engine files less frequently. Deploy these packages to
managed systems as soon as possible to protect them against the latest threats.
A scheduled pull task runs automatically and regularly at times and days you specify.
For example, you can schedule a daily repository pull task at 5:00 AM.
You can also use the Pull now task to check updates into the master repository
immediately. For example, when McAfee alerts you to a fast-spreading virus and
releases a new DAT file to protect against it.
If a pull task fails you must check the packages into the master repository manually.
Once you have updated your master repository, you can distribute these updates to
your systems automatically with global updating or with replication tasks.
Considerations when scheduling a pull task
Consider the following when scheduling pull tasks:
Bandwidth and network usage. If you are using global updating, as recommended,
schedule a pull task to run when bandwidth usage by other resources is low. With
global updating, the update files are distributed automatically after the pull task
completes.
Frequency of the task. DAT files are released daily, but you may not want to use your
resources daily for updating.
Note
EXTRA
.
DAT
files must be checked into the master repository manually. They are
available from the McAfee web site.
Содержание ePolicy Orchestrator
Страница 2: ......
