Global Updating - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

®
ePolicy Orchestrator 3.6 Walkthrough Guide

Global updating

Considerations when creating client update tasks
Consider the following when scheduling client update tasks:
Create a task to update DAT and engine files daily at the highest level of the
Directory that is inherited by all systems. If your organization is large, you can use
randomization intervals to mitigate the bandwidth impact of all systems updating at
the same time. Also, for large networks with offices in different time zones, running
the task at the local system time on the managed system, rather than at the same
time for all systems, helps balance network load.
Schedule the update task at least an hour after the scheduled replication task, if you
are using scheduled replication tasks.
Run update tasks for DAT and engine files at least once a day. Managed systems
can be logged off from the network and miss the scheduled task; running the task
frequently ensures these systems receive the update.
Maximize bandwidth efficiency and create several scheduled client update tasks
that update separate components and run at different times. For example, you can
create one update task to update only DAT files, then create another to update both
DAT and engine files weekly or monthly — engine packages are released less
frequently.
Create and schedule additional update tasks for products that do not use the agent
for Windows.
Run missed task
Use the option. This can be useful if systems are logged off from the
network at the scheduled update time, ensuring they update after logging onto the
network.
McAfee recommends using global updating with your updating strategy. Global
updating automates replication to your distributed repositories and updating managed
systems. Replication and update tasks are not required. Checking contents into your
master repository initiates a global update. The entire process should complete within
an hour in most environments.
Additionally, you can specify which packages and updates initiate a global update.
However, when you only specify that certain content initiates a global update, ensure
that you create a replication task to distribute content that was not selected to initiate
a global update.
When using global updating, McAfee recommends scheduling a regular pull task (to
update the master repository) at a time when network traffic is minimal. Although
Note
global updating is much faster than other methods, network traffic over the updating
time period is increased.
Global updating process
Global updating updates your environment within an hour in most environments using
the following steps:
1 Contents are checked into the master repository.
2 Contents of the master repository are replicated automatically to the distributed
repositories.
44
Deploying the Agent and Products
About deploying and updating products
4