User`s guide

Table Of Contents
Getting Started with VCM for Active Direc-
tory
15
Getting Started with VCM for Active
Directory
VCM for Active Directory (AD) collects AD objects across Domains and Forests, and displays them
through a single console. This data is consolidated and displayed under the Active Directory slider,
providing a logical grouping of AD object and configuration information, allowing you to view your AD
structure, troubleshoot issues, and detect change.
Data can be filtered, sorted, and grouped to allow you to pinpoint the specific area in which you are
interested. You can also view a subset of your AD (a Forest, Domain, or specific OU branch) by setting the
AD Location in the global zone at the top of the VCM Portal. Dashboards display high-level roll up
information in graphical form, Alerts can be configured to notify you when there is a problem or
misconfiguration, and Change Management tracks changes to the AD objects or configuration by data
class.
Before you begin collecting Active Directory data with VCM for Active Directory, you must complete the
following required steps. These steps are explained in this chapter.
1. Making VCM aware of your Domain Controllers
2. Configuring VCM for Active Directory as an additional product
3. Performing an Active Directory data collection
4. Exploring Active Directory collection results
Making VCM Aware of Domain Controllers
The first step in using VCM for Active Directory (AD) is to make VCM aware of the Domain Controllers
(DCs), and license them as Windows servers. Once they are licensed, you can then perform an initial
machines collection to make them available to VCM for Active Directory (AD).
Follow the steps listed below to make VCM aware of your DCs and to perform an initial collection:
1. Confirming the Presence of Domains
2. Adding and Assigning Network Authority Accounts
3. Discovering Domain Controllers
4. Verifying Domain Controller Machines in Available Machines
5. Licensing and Deploy the Agent
6. Performing a Machine Data Type Collection
VMware, Inc. 213