Table of Contents
Advertisement
Deploying Software and Updates
Product and update deployment
If you are using global updating, this task is unnecessary, although you can create a daily task
for redundancy.
Considerations when creating update client tasks
Consider the following when scheduling client update tasks:
• Create an Update client task to update DAT and engine files daily at the highest level of the
System Tree that is inherited by all systems. If your organization is large, you can use
randomization intervals to mitigate the bandwidth impact. Also, for large networks with
offices in different time zones, run the task at the local system time on the managed system,
rather than at the same time for all systems, to help balance network load.
• Schedule the 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 might 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 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 tasks to update products that do not use the agent for
Windows.
• Create a task to update your main workstation applications, such as VirusScan Enterprise,
to ensure they all receive the update files. Schedule it to run daily or several times a day.
Global updating
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 in to 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.
NOTE:
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 global updating
is much faster than other methods, it increases network traffic during the update.
Global updating process
Global updating updates most environments within an hour using this process:
1
Contents are checked in to the master repository.
2
Contents of the master repository are replicated automatically to the distributed repositories.
3
A SuperAgent wake-up call is broadcast to all SuperAgents, which then send the wake-up
call to all agents within each SuperAgent's broadcast segment. The call contains information
about the updated packages and the repositories containing them. If a package the managed
systems require is in the wake-up call, the agents go to a distributed repository to get the
package.
4
All agents go to their distributed repositories for new updates.
McAfee ePolicy Orchestrator 4.0.2 Product Guide
135
Advertisement
Table of Contents
