Updating tasks

If you do not use global updating, determine when agents on managed systems go for updates.

You can create and update client tasks to control when and how managed systems receive update packages.

If you use global updating, this task is not needed, although you can create a daily task for redundancy.

Considerations when creating or updating client tasks

Consider the following when scheduling client update tasks:

  • Create a daily update client task at the highest level of the System Tree, so that all systems inherit the task. If your organization is large, you can use randomization intervals to mitigate the bandwidth impact. For networks with offices in different time zones, balance network load by running the task at the local system time of the managed system, rather than at the same time for all systems.
  • If you are using scheduled replication tasks, schedule the task at least an hour after the scheduled replication task.
  • 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 that 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 more tasks to update products that do not use the McAfee Agent for Windows.
  • Create a task to update your main workstation applications, to ensure that they all receive the update files. Schedule it to run daily or several times a day.