---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Active Directory Domain Controller

# Active Directory Domain Controller discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 27, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The Discovery and Service Mapping Patterns application uses the Active Directory Domain Controller On Windows pattern to find Active Directory domain controllers running on a Windows server. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
When discovery runs on a domain controller, the pattern also creates LDAP endpoint connections to child domains in the same forest, triggering discovery of those domain controllers as well.  
Note:  
For information on Probe to Pattern migration see the knowledge article [KB0694477](https://support.servicenow.com/kb_view.do?sysparm_article=KB0694477).

## Prerequisites {#r-ActiveDirectory__section_prerequisites_ad}

Verify that the applications are up to date
:
    * Discovery and Service Mapping Patterns
    * Visibility Content
    {#r-ActiveDirectory__ul_apps_ad}

Verify an LDAP or TCP entry point is configured
:   Verify that the relevant port is open and listening on the domain controller.

Create Windows credentials with WMI access
:   Verify that the credentials have permission to run WMI queries on the `\\root\CIMV2` namespace. For more information, see [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).

Schedule a horizontal discovery
:   For more information, see [Schedule a horizontal discovery](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.").

## Data collected by Discovery during horizontal discovery {#r-ActiveDirectory__section_jzw_1lf_g2c}

Discovery populates the data in the CMDB when running the Active Directory Domain Controller On Windows pattern.  
{#r-ActiveDirectory__table_qlw_vlf_g2c__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the domain controller, which is the domain name. |
| Domain name \[domain_name\] | Name of the Active Directory domain. |
| Domain Controller name \[domain_controller_name\] | Name of the domain controller server. |
| Forest name \[forest_name\] | DNS name of the Active Directory forest. |
[Table 1. Active Directory Domain Controller \[cmdb_ci_ad_controller\]]

{#r-ActiveDirectory__table_qlw_vlf_g2c}

## CI relationships {#r-ActiveDirectory__section_relationships_ad}

The Active Directory Domain Controller On Windows pattern creates the following relationships to support Active Directory Domain Controller discovery.  
{#r-ActiveDirectory__table_relationships_ad__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Active Directory Domain Controller \[cmdb_ci_ad_controller\] | Runs on::Runs | Windows Server \[cmdb_ci_win_server\] |
[Table 2. CI relationships]

{#r-ActiveDirectory__table_relationships_ad}