WMI is trusted host name source:

mikeb5
Kilo Contributor

‎10-07-2015 06:35 AM

We're seeing a number of problems where ServiceNow discovers a Windows server and gets the host name wrong. We have a number of servers with DNS aliases, which we are using to make switching processing to our DR site easier. The alias points at the server at either the main or DR site, so any processes or people that need the resource use the alias and don't need ot know which site the server is running at.
ServiceNow is picking up the alias instead of the server name. I think it's doing reverse DNS lookup on the ip address to get the name and, for some reason, picks up the alias name.

It occurred to me that setting "


  • I assume this setting would apply to every discovery schedule?
  • What other effects would we see? Eg any side effects we wouldn't want.
  • Would this have an impact on discovering MS failover clusters? Hitting a cluster virtual name ip address with a WMI query could bring back the name of the physical server hosting the resource where a DNS query would bring back the cluster virtual name.


The only thing I can think that might happen is that for servers where WMI is unavailable, we don't even get the server name from DNS.

Labels:
0 Helpfuls
  • 1,684 Views
1 REPLY 1

doug_schulze
ServiceNow Employee
ServiceNow Employee

‎10-07-2015 07:47 AM

Mike,



That is a perfect use for that property and there are really no side effects that I have ever come across in using it these many years in my deployments. But to answer directly



1. Yes, it applies to all windows hosts discovered regardless of schedule


2. None, unless you really wanted to include your domain name in hostname, then you'd have to go back


3. absolutely NO impact, for clusters we're getting that info from the cluster itself and do not rely on DNS to offer any assistance in building those CIs



While you're in the neighborhood, may as well set SSH and SNMP! I always do..