McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual page 10

®
ePolicy Orchestrator 3.6 Walkthrough Guide
Update repositories.
Figure 1-1 ePolicy Orchestrator on your network
ePolicy Orchestrator server
The center of your managed environment. One server can manage up to 250,000
systems, but you may be restricted by your bandwidth and other considerations. For
example, network obstacles like firewalls and proxy servers, geographic locations of
sites, and security divisions within your organization.
The server:
Delivers security policies.
Controls product and
DAT
Processes events and serves tasks for all managed systems.
Provides the mechanism for agent communication.
Controls data access to and from the ePolicy Orchestrator database.
The ePolicy Orchestrator server should be hosted on a dedicated server. Typically, the
ePolicy Orchestrator server is accessed via remote ePolicy Orchestrator consoles
(installed on other systems), although it can be accessed from a local console as well.
For information on server sizing, see the ePolicy Orchestrator 3.6 Hardware Sizing and
Bandwidth Usage White Paper.
Database server
ePolicy Orchestrator uses a back-end database to store data, which is represented in
the console tree of the user interface. The database contains information from each
managed system.
The reporting and query features of ePolicy Orchestrator (accessed through the
consoles) allow you to view this data in ways you can customize.
file updates.
7
Introduction
Components of ePolicy Orchestrator
1