Specifications

1
Click Menu | Policy | Policy Catalog, then select McAfee Agent from the Product list and General from the
Category list.
2
Click the General tab, and type the Policy enforcement interval as shown in the following example.
Deploying packages
Packages are the binaries or files that can be deployed to an endpoint. All packages that could be
deployed from the McAfee ePO server are located in the master repository.
You do not have to check all packages into the master repository if you do not plan to deploy them
with the McAfee ePO server. If you plan to use a third party tool to deploy McAfee products, you do not
need to check in the package into the master repository. All content that is updated frequently, for
example patches and signature files, can be checked in manually or checked in using an automated
server task.
ePolicy Orchestrator tracks package versions, both major and minor, and ePolicy Orchestrator version
4.5, and later, allows packages to be checked into all three ePolicy Orchestrator repository branches:
Current, Previous and Evaluation.
The branch a package is checked into is selected at the time the package
is checked in and can be modified manually.
The multiple branch feature in ePolicy Orchestrator allows multiple versions of the same package, for
example Virus Scan Enterprise, in the same repository. This allows installation of that package on a
subset of the environment for testing prior to production rollout.
The multi-branch feature for packages is not enabled by default. Enable multiple branches in your
repository.
8
Policies and packages
Deploying packages
60
McAfee
®
ePolicy Orchestrator
®
4.0 and 4.5 Best Practices Guide