On 9/30/2011, McAfee ePolicy Orchestrator (ePO) 4.0 will reach its end of full service support date.
Continue reading…

ePO 4.5 server task log

The server task log provides information about your pull and replication tasks, in addition to all server tasks. This provides the status of the task and any errors that may have occurred.

Replication task information in the server task log
The following information is available for replication tasks on the Reporting | Server Task Log tab:
• Start date and task duration.
• Status of task at each site (when expanded).
• Any errors or warnings, their codes, and the site to which they apply.

Pull task information in the server task log
The following information is available for pull tasks on the Reporting | Server Task Log tab:
• Start date and task duration.
• Any errors or warnings and their codes.
• Status of each package that is checked into the master repository.
• Information regarding any new packages that are being checked into the master repository.

ePO 4.5 repositories

New distributed repositories are added to the repository list file containing all available distributed repositories. The agent of a managed system updates this file each time it communicates with the ePO server. The agent performs repository selection each time the agent (McAfee Framework Service) service starts and when the repository list changes.
Continue reading…

Use replication tasks to copy the contents of the master repository to distributed repositories. Unless you have replicated master repository contents to all your distributed repositories, some systems do not receive them. Ensure all your distributed repositories are up-to-date.
Continue reading…

Using ePO 4.5 Pull tasks

Use pull tasks to update your master repository with DAT and engine update packages from the source site. DAT and engine files must be updated often. McAfee releases new DAT files daily and engine files less frequently. Deploy these packages to managed systems as soon as possible to protect them against the latest threats.
Continue reading…

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.
Continue reading…

Once an update package has been checked into the master repository and replicated to the distributed repositories, the agents on the managed systems still need to know when to go to the distributed repositories for updates. This is unnecessary if you are using global updating.
Continue reading…

Once you have checked in the product deployment package, use the Product Deployment client task to install the product on managed systems. The task installs any product that is deployable through ePolicy Orchestrator and has been checked in to the master repository.
Continue reading…

The ePO repository infrastructure allows you to deploy product and update packages to your managed systems from a central location. Although the same repositories are used, there are differences.
Continue reading…

Use these tasks to manage policy rule assignments. To perform these actions, go to Systems | Policy Assignment Rules.
Continue reading…