The Zurich release has arrived! Interested in new features and functionalities? Click here for more

AD Domain Controller classed as a Windows Server

adamtrent
Tera Contributor

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?

8 REPLIES 8

adamtrent
Tera Contributor

OK so I've since learnt that Discovery classes AD Domain Controllers as Windows Servers.   Does anyone know why this is the case?   AD Domain Controller is an available class so what is the reason behind classing them as Windows Servers?   Is it so you can manually change the class of a domain controller if it best fits your relationship mapping?



Thoughts please any of you ServiceNow Jedi's out there?


Community Alums
Not applicable

I do not have Domain Controller in my Configuration list, but my first thought is this: a Domain Controller is simply a Windows Server that is running special software to interact with/run Active Directory. The server is a Windows Server, and then you would have AD Domain Controller related to that Windows Server in the CMDB. This same Windows Server could also be running other software, such as SQL Server and other items that could be broken out as related items in the CMDB. In this way, the physical server as a Windows Server with related items makes sense to me.



Ben


Hi Adam,



I agree with what Ben has pointed out.


Active Directory is a special role installed on Microsoft Windows Servers just like installing any other applications. Same server can also be used as DNS, DHCP server. So I am not wondering if AD server is getting classified as windows.


adamtrent
Tera Contributor

Hi Ben/Deepak,



Thank you for your responses and to an extent I agree, but there is a class available called AD Domain Controller, a server with AD installed is a domain controller but as you said if the OS is Windows then it is also a Windows Server.   My question relates to the logic of including AD Domain Controller as a class if it won't be assigned automatically, is the intention therefore to include as AD Domain Controller as an option to manually re-class a device if that better suits your relationship mapping?