McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual page 11

®
ePolicy Orchestrator 3.6 Walkthrough Guide
ePolicy Orchestrator consoles
You can have multiple consoles installed on your network. One resides on the ePolicy
Orchestrator server itself as a local console, and you can install as many as you like
remotely throughout your network.
Typically, you will want one that is accessible to anyone in your environment who needs
to access the ePolicy Orchestrator server. For example, you would want all
administrators to be able to access the ePolicy Orchestrator server from a console to
perform their management tasks. You can assign roles with different rights and
permissions to users.
ePolicy Orchestrator agent
The agent is a vehicle of information and enforcement between the ePolicy
Orchestrator and each managed system. For each of the managed systems, the agent:
Retrieves updates.
Executes scheduled tasks.
Enforces policies.
Forwards properties and events to the server.
Every system you want to manage must have this component installed.
Rogue System Detection (RSD) sensor
Sensors can reside on one or more systems per subnet. The active sensor notifies you
when a rogue system (a system without an ePolicy Orchestrator agent) enters the
environment, and can then initiate a user-defined automatic response on that system,
such as deploying an agent to it.
Sensors "listen" to all broadcast layer 2 communications on the subnets. Although you
can deploy multiple sensors to a subnet, only one is listening at a time. This allows a
minimum of network activity, and ensures one sensor is always listening per subnet.
Master repository
The master repository exists on the ePolicy Orchestrator server and is the central
location for all McAfee product updates. The master repository goes to the McAfee
Download Site (source repository) at defined times to retrieve all available updates and
signatures. The master repository contains a copy of the contents of the McAfee
Download Site that can be accessed by the various update repositories in your
organization.
Update repositories
Update repositories are distributed throughout your environment, providing easy
access for managed systems to pull DAT files, product updates, and product
installations. Depending on how your network is configured, you may want to set up
different types of repositories. You can create HTTP , FTP , and UNC share distributed
repositories anywhere on your network, or you can create an update repository per
subnet by converting an agent on each subnet into a SuperAgent repository.
8
Introduction
Components of ePolicy Orchestrator
1