McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC, Product Manual

Page: 192 / 328

4 Next to
Package types
, select which packages initiate an update.
Global updating initiates an update only if new packages for the components specified here are
checked in to the master repository or moved to another branch. Select these components carefully.
•
Signatures and engines
— Select
Host Intrusion Prevention Content
, if needed.
Selecting a package type determines what initiates a global update (not
what is updated during the global update process). Agents receive a list
of updated packages during the global update process. The agents use
this list to install only updates that are needed. For example, agents only
update packages that have changed since the last update and not all
packages if they have not changed.
5 When finished, click
Save
.
Once enabled, global updating initiates an update the next time you check in any of the selected
packages or move them to another branch.
Be sure to run a Pull Now task and schedule a recurring Repository Pull
server task, when you are ready for the automatic updating to begin.
Pull tasks
Use pull tasks to update your master repository with DAT and engine update packages from the source
site. 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.
With this release, you can specify which packages are copied from the source site to the master
repository.
ExtraDAT files must be checked in to the master repository manually.
They are available from the McAfee website.
A scheduled Repository Pull server task runs automatically and regularly at the times and days you
specify. For example, you can schedule a weekly repository pull task at 5:00 a.m. every Thursday.
You can also use the Pull Now task to check updates in to 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 in to 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 these 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 finishes.
• Frequency of the task — DAT files are released daily, but you might not want to use your
resources daily for updating.
• Replication and update tasks — Schedule replication tasks and client update tasks to ensure
that the update files are distributed throughout your environment.
16 Using tasks to manage products and systems
Server tasks and what they do
192 McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide