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.
Comparison of product deployment and update packages
Product deployment packages
Update packages
Must be manually checked in to the master repository.
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 on managed systems with global updating.
Can be replicated to the distributed repositories and
installed automatically on managed systems with global
updating.
If not implementing global updating for product
deployment, a deployment task must be configured and
scheduled for managed systems to retrieve the package.
If not implementing global updating for product updating,
an update client 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:
Check in the update package to the master repository with a pull task or manually.
Do one of the following:
If 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.
If 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.
Global Threat Condition: Severe
