95
ePolicy Orchestrator
®
3.6 Walkthrough Guide
Installing and setting up
Installing agent manually on client systems
8
S
T
E
P
4
Set up master and distributed repositories
Now you have agents installed on your client systems, but what can they do? The
purpose of an agent is to allow you to manage client security software policies centrally
through ePolicy Orchestrator. But until you have security software installed on the client
systems, your agents have nothing to do. The next step is to use ePolicy Orchestrator
to deploy VirusScan Enterprise 8.0i anti-virus software to your client systems.
Software deployed with ePolicy Orchestrator is stored in software repositories. There
are many ways to set up your repositories. This guide demonstrates a typical example
that you can use in your test environment.
About using master and distributed repositories in your test network
ePolicy Orchestrator uses repositories to store the software that it deploys. This section
illustrates using both master and distributed repositories for deploying software and
updating. Repositories store the software, such as the agent or VirusScan installation
files, and updates, such as new virus definition (DAT) files, that you plan to deploy to
client systems. The master repository is located on the ePolicy Orchestrator server, and
is the primary storehouse for your software and updates. Distributed repositories are
copies of the master that reside in other parts of your network. Systems in those other
parts of your network can update more quickly from local servers than across a WAN
to your ePolicy Orchestrator server.
Domains and Active Directory containers can be geographically separated and
connected via a WAN. In this case, create a distributed repository, which is simply a
copy of the master repository, on a system in the remote location. Systems in that
location,
Container1
in our example, can update from the distributed repository instead
of having to copy updates across the WAN.
Systems in the
Domain1
site receive updates and product deployments directly from the
master repository, located on the ePolicy Orchestrator server. Systems located in the
Container1
site, however, receive them from a distributed repository.
Use the following procedure for using and setting up repositories in your test
environment:
1
Add VirusScan Enterprise to the master repository
.
2
Pull updates from McAfee source repository
.
3
Create a distributed repository
.
1
Add VirusScan Enterprise to the master repository
The VirusScan Enterprise 8.0i NAP file, allows you to manage VirusScan Enterprise 8.0i
policies once it has been installed on client systems in your network. However, to be
able to first use ePolicy Orchestrator to deploy VirusScan Enterprise 8.0i to those client
systems, you must also check in the VirusScan Enterprise deployment, or installation,
package to the master software repository. The deployment package file is called
P
KG
C
ATALOG
.
Z
and is contained in the
VSE
80
IEVAL
.
ZIP
you downloaded from McAfee
(see
Get installation files from McAfee
on page 81
).
To check in the VirusScan Enterprise 8.0
i
package to your master repository:
1
In the console tree, select
Repository
.
2
In the details pane, select
Check in Package
. The
Check in package
wizard appears.
Содержание ePolicy Orchestrator
Страница 2: ......