McAfee EPOCDE-AA-BA - ePolicy Orchestrator - PC, Product Manual

Page: 78 / 328

Repository types and what they do
To deliver products and updates throughout your network, the ePolicy Orchestrator software offers
several types of repositories that create a robust update infrastructure when used together. These
provide the flexibility to develop an updating strategy to ensure your systems stay up-to-date.
Master repository
The master repository maintains the latest versions of security software and updates for your
environment. This repository is the source for the rest of your environment.
By default, ePolicy Orchestrator uses Microsoft Internet Explorer proxy
settings.
Distributed repositories
Distributed repositories host copies of your master repository’s contents. Consider using distributed
repositories and placing them throughout your network strategically to ensure managed systems are
updated while network traffic is minimized, especially across slow connections.
As you update your master repository, ePolicy Orchestrator replicates the contents to the distributed
repositories.
Replication can occur:
• Automatically when specified package types are checked in to the master repository, as long as
global updating is enabled.
• On a recurring schedule with Replication tasks.
• Manually, by running a Replicate Now task.
A large organization can have multiple locations with limited bandwidth connections between them.
Distributed repositories help reduce updating traffic across low bandwidth connections, or at remote
sites with a large number of client systems. If you create a distributed repository in the remote
location and configure the systems within that location to update from this distributed repository, the
updates are copied across the slow connection only once — to the distributed repository — instead of
once to each system in the remote location.
If global updating is enabled, distributed repositories update managed systems automatically, as soon
as selected updates and packages are checked in to the master repository. Update tasks are not
necessary. However, you do need to be running SuperAgents in your environment if you want
automatic updating. You must still create and configure repositories and the update tasks.
If distributed repositories are set up to replicate only selected packages,
your newly checked-in package is replicated by default. To avoid
replicating a newly checked-in package, deselect it from each distributed
repository or disable the replication task before checking in the package.
For additional information, see Avoiding replication of selected packages
and Disabling replication of selected packages.
Do not configure distributed repositories to reference the same directory
as your master repository. Doing so causes the files on the master
repository to become locked by users of the distributed repository, which
can cause pulls and package check-ins to fail and leave the master
repository in an unusable state.
8 Setting up repositories
Repository types and what they do
78 McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide