Pull content automatically: best practice

Pull the McAfee content from the public McAfee servers. This pull task keeps your protection signatures up to date.

You must schedule your pull tasks to run at least once a day after 3 p.m. Eastern Time (19:00 UTC or GMT). In the following example, the pull is scheduled for twice daily, and if there is a network problem at 5 p.m., the task occurs again at 6 p.m.. Some users like to pull their updates more frequently, as often as every 15 minutes. Pulling DATs frequently is aggressive and unnecessary because DAT files are typically released only once a day. Pulling two or three times a day is adequate.

Note: Testing your DAT files before deployment requires a predictable pull schedule.

Task

  1. Select MenuAutomationServer Tasks, then click ActionsNew task.
  2. In the Server Task Builder dialog box, type a task name and click Next.
  3. Specify which signatures to include in the pull task.
    1. In the Actions dialog box, from the Actions list, select Repository Pull, then click Selected packages.
    2. Select the signatures that apply to your environment.
    Tip: Best practice: When you create a pull task for content, select only the packages that apply to your environment instead of selecting All packages. This keeps the size of your Master Repository manageable. It also reduces the bandwidth used during the pull from the McAfee website and during replication to your distributed repositories.
  4. Click Next.
  5. Schedule your pull task to run at least once a day after 3 p.m. Eastern Time, then click Next.
  6. Click the Summary tab, confirm that the server task settings are correct, then click Save.

Results

Now you have created a server task that automatically pulls the McAfee DAT files and content from the public McAfee servers.