AD Domain Controller classed as a Windows Server

[adamtrent]

The domain controller we have AD running on has been classed as a Windows Server in the cmdb, we were expecting this to be an AD Domain Controller.   We've applied a behaviour to the discvovery schedule to use WMI and WINRM probes only.

Any idea why the AD Domain Controller has been discovered a Windows Server and not and AD Domain Controller?

[Deepak Ingale1]

Hi Adam,

As you can see, Directory Server is extended from class "Application", I am not sure whether discovery creates an entry for corresponding application class as well while creating entry in server class. Probably you might have to create new entry itself in Directory Server keeping Windows server entry as it is and then build a relationship between these two classes.

bsweetser, any thoughts on it?

[Community Alums]

Adam,

If you look at the table name for AD Domain Controller, does the table name begin with a u_ or some other prefix? It sounds to me like a custom table. From where does it extend in the structure? That can help sort out this mystery. I still stand by the suggestions deepak.ingale and I have made that the AD server should be an item related to the physical Windows Server.

Ben

[adamtrent]

This is odd.   I found a table for Active Directory Domain to Domain Controller - cmdb_ci_endpoint_ad_domain - it extends Endpoint.   I can't find a table for Active Directory Domain Controller and it's not a custom entry because I see the same class in different instances in the CI relationship mapping filter.

[Hellfried]

This topic is a bit puzzling - but I found out how it works:

As we all have noticed, the windows server running the AD Domain Controller services is classified as Windows Server [cmdb_ci_win_server]. 
If the server has been promoted to a domain controller,  a separate CI is created in table
Active Directory Domain Controller [cmdb_ci_ad_controller], which represents this AD instance.

Both CIs are related with Relation type: Runs on::Run

A (maybe short) description is to be found in 
https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/refe...
- but it assumes that is natural for you to see the AD replica as a separate CI.