Organizing The Directory And Repositories; Epolicy Orchestrator Directory: Concepts And Roles - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

3
Organizing the Directory and
Repositories
The ePolicy Orchestrator software requires you to configure and set up several
components. Although extensive, the configurations allow you to customize the
product specifically for your environment. Carefully planning the implementation of
your ePolicy Orchestrator solution is essential before installing the software.
You should consider how your:
Directory should be organized.
The client systems should receive their updates.
This chapter contains the following sections:
ePolicy Orchestrator Directory: concepts and
Repositories.

ePolicy Orchestrator Directory: concepts and roles

The Directory allows you to combine systems into sites and groups. Combining
systems with similar properties or requirements allows you to manage policies for
these groupings in one place, rather than having to set policies for individual systems.
It can also make visually browsing your Directory much easier.
Before discussing Directory organization further, it is important to define some terms:
Directory
The Directory contains all your managed network systems that you are managing with
ePolicy Orchestrator. It is possible to add all the systems to be managed by ePolicy
Orchestrator into one site in the Directory. However, this flat unorganized list makes
setting specific policies for different systems very difficult. Therefore, organizing the
systems in smaller units within the Directory is essential.
Sites
A site is a first-level group immediately under the Directory root of the console tree.
Systems contained within a site can be organized into groups. Sites can contain groups
and individual systems.
Groups
A group is a secondary grouping beneath a site. It can contain more groups
(sub-groups) and individual systems, but a group cannot contain a site.
roles.
18