Best practice: Automating DAT file testing

Use the built-in functionality of McAfee ePO to automatically validate DAT file compatibility and content files that are downloaded from the McAfee public site.

McAfee Labs rigorously tests the content, such as DAT and engine files, before they are released on the public update servers. Because every organization is unique, you can perform your own compatibility validation to ensure the compatibility of DATs and content in your unique environment.

The compatibility validation processes vary by organization. The process in this section is meant to automate much of the compatibility validation process and reduce the need for administrator intervention.

Tip: Best practice: To confirm that only compatible DAT files are distributed in your environment, you might chose move the content manually from the Evaluation branch into the Current branch of the repository.

  1. A server task pulls DAT updates from the McAfee public site to the Evaluation branch of the Master Repository.
  2. A McAfee Agent policy applies the DAT files from the Evaluation repository branch restricted to a group of systems in a Test group.
  3. A McAfee Agent update client task installs the DAT on the Test group systems.
  4. An on-demand scan task runs frequently on the Test group.
  5. Depending on the on-demand scan output, one of these scenarios occurs:
    1. If the DAT is not compatible with the test group, an Automatic Response email is sent to the appropriate administrators. The email tells the administrators to stop distribution of the DAT files from the Current repository.
    2. Otherwise, after a specified time, a server task copies the files from the Evaluation branch to the Current branch of the repository. Then those files are automatically sent to the rest of the managed systems.

DAT file validation overview

Automatic DAT file testing steps