Product And Update Deployment; First Time Product And Update Deployment Overview - McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC Product Manual

Package ordering and dependencies
If one product update is dependent on another, you must check in the update packages to the master
repository in the required order. For example, if Patch 2 requires Patch 1, you must check in Patch 1
before Patch 2. Packages cannot be reordered once they are checked in. You must remove them and
check them in again, in the proper order. If you check in a package that supersedes an existing
package, the existing package is removed automatically.

Product and update deployment

The McAfee 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.
Comparison of product deployment and update packages
Product deployment packages
Must be manually checked in to the master
repository.
Can be replicated to the distributed
repositories and installed automatically on
managed systems using a deployment task.
If not implementing global updating for
product deployment, a deployment task
must be configured and scheduled for
managed systems to retrieve the package.
Product deployment and updating process
Follow this high-level process for distributing DAT and engine update packages.
1 Check in the update package to the master repository with a pull task, or manually.
2 Do one of the following:
• Using global updating — Nothing else is required for systems on the network. You should,
however, create and schedule an update task for laptop systems that leave the network.
• Not using global updating — Use a replication task to copy the contents of the master repository
to the distributed repositories, then create and schedule an update task for agents to retrieve
and install the update on managed systems.

First time product and update deployment overview

Follow this process to ensure your product and update deployments are completed successfully.
When deploying products for the first time:
1 Configure server tasks for repository pull and repository replication.
2 Check in product and update packages to the master repository using the Software Manager.
3 Configure product deployment and update client tasks.
Using tasks to manage products and systems
Update packages
DAT and engine update packages can be copied from
the source site automatically with a pull task. All other
update packages must be checked in to the master
repository manually.
Can be replicated to the distributed repositories and
installed automatically on managed systems with global
updating.
If not implementing global updating for product
updating, an update client task must be configured and
scheduled for managed systems to retrieve the package.
® ®
McAfee ePolicy Orchestrator
Product and update deployment
4.6.0 Software Product Guide
16
189