The ePO - On-prem repository infrastructure allows you to deploy product and update packages to your managed systems from a central location. Although the same repository is used, there are differences.
Product deployment vs. update packages
Product deployment packages | Update packages |
|---|---|
Must be manually checked in to the Main 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 Main Repository manually. |
Can be replicated to the Main Repository and installed automatically on managed systems using a deployment task. | Can be replicated to the Main Repository 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 Main Repository with a pull task, or manually.
Do one of the following:
If you are using global updating, create and schedule an update task for laptop systems that leave the network.
If you are not using global updating, perform the following tasks.
Use a replication task to copy the contents of the Main Repository.
Create and schedule an update task for agents to retrieve and install the update on managed systems.