Table of Contents
Advertisement
®
ePolicy Orchestrator
3.6 Walkthrough Guide
Repository selection by agents
Selective updating
About the SITELIST.XML repository list
Specific files and signatures that are replicated to the distributed repositories.
Selecting only those types of files that are necessary to each system that checks
into the distributed repository lessens the impact on bandwidth resources. When
you define or edit your distributed repositories, you can choose which packages you
want to replicate to the distributed repository.
This functionality is intended for updating products that are installed on several
systems only in your environment, like GroupShield and Webshield. The functionality
Note
allows you to distribute such updates only to the distributed repositories these
systems check into.
By default, agents can attempt to update from any repository in the repository list
(
.
) file. The agent can use a network ICMP ping or a subnet address compare
SITELIST
XML
algorithm to find the distributed repository with the quickest response time. Usually,
this is the closest distributed repository to the system on the network.
You can also tightly control which distributed repositories agents use for updating by
enabling or disabling distributed repositories in the agent policy settings. McAfee does
not recommend disabling repositories in the policy settings. Allowing agents to update
from any distributed repository ensures they receive the updates.
ePolicy Orchestrator allows you to select which updates (DAT file, engine, and
product-specific updates) you want client systems to receive, so that valuable
bandwidth isn't wasted transferring unnecessary files. You can use selective updating
with both global updating and update tasks.
You can also use this feature to selectively update only those components that you will
want updated as soon as possible once an update is released. For example, DAT files
and VirusScan Enterprise updates.
Due to the challenges customers face, ePolicy Orchestrator 3.6 provides different types
of update repositories and several methods for implementing them:
The
.
file is a repository list containing all of the update repositories you are
SITELIST
XML
managing through ePolicy Orchestrator. These include any source repositories, the
master repository, and any repositories you have created. The repository list contains
the location and network credential information that client systems use to select the
nearest repository and retrieve updates.
When a new update repository is created, the
locations to which agents point for updates are adjusted.
Note
The ePolicy Orchestrator server sends the repository list to the agent during
agent-to-server communication. You can also export it to a file, manually deploy it, then
apply it to client systems using command-line options.
.
SITELIST
XML
47
Deploying the Agent and Products
About deploying and updating products
file is updated and the
4
- Quick Links:
- Policies
Hide quick links:
Advertisement
Table of Contents
