102
ePolicy Orchestrator
®
3.6 Walkthrough Guide
Installing and setting up
Installing agent manually on client systems
8
5
Select
Duplicate the following policy
, then select the policy you created earlier (to display
the agent system tray icon) from the drop-down list.
6
Provide a
New policy name
for the policy (for example,
New Agent Policy--custom
repository
), then click
OK
. The
Policy Settings
dialog box appears.
7
Select the
Repositories
tab, then deselect
Inherit
.
8
Under
Repository selection
, select
User defined list
.
9
In the
Repository list
, deselect all repositories until only your distributed repository is
selected.
10
Click
Apply All
, then click
Close
.
11
Click
Apply
at the end of the
Configuration
row on the
Assign Policies
page to assign the
new policy to the site selected in the console tree.
Now, when the systems in this site require updates, they retrieve them from the
distributed repository.
Again, forcing updates from certain repositories is shown here only for the purposes of
simulating distributed repositories in a lab network. This is not something you would do
in a production environment, where you would want to have some repository
redundancy available for fail-over. Due to faster local network connections, client
systems would likely update from a local distributed repository, rather than over a WAN
to the master repository, even if not specifically configured to do this. On the other
hand, if the distributed repository were unavailable for any reason, the client could still
update from other repositories on the network if necessary.
S
T
E
P
5
Set VirusScan Enterprise 8.0i policies before
deploying
Now that you have created your repositories and added the VirusScan Enterprise
deployment package to them, you are almost ready to deploy VirusScan Enterprise to
your client systems. Before deploying VirusScan Enterprise, however, let’s modify the
policies slightly. Remember the NAP file you checked in? We can use it to configure
how VirusScan Enterprise functions once it is installed on the client system. To
demonstrate, we’ll use a simple example: changing the policies for workstations to
install VirusScan Enterprise 8.0
i
with minimal user interface. Servers keep the default
policy, which is to display the full interface.
This could be a potentially useful implementation in your real network, where you may
want to hide the system tray interface on your workstations to prevent end-users from
easily changing policies or disabling features.
To set these policies, we’ll use the
Workstations
groups created when you made your
Directory. You can change the policy once for each workstation group (within
Domain1
and
Container1
) to have it inherit to all systems within those groups. For servers, we can
leave the default policy, which installs VirusScan Enterprise with the full menu options
available in the system tray.
To change the VirusScan Enterprise policies for workstations:
Summary of Contents for ePolicy Orchestrator
Page 2: ......