Which Specific Windows Command(s) Retrieve FQDN?

tim_sewell · ‎09-07-2016

We have found that the Fully qualified domain name (fqdn) on several of our Windows servers is not set correctly after nightly discovery is ran. Our Windows admin is asking which specific command our discovery is using to pull that information so he can identify if there is an inconsistency in the server configuration. I was able to find several script includes that deal with fqdn, but I was not able to see which commands are sent to the server, i.e. in a probe.

Ryan Zulli · ‎09-13-2016

Hi Tim,

When that property is checked we essentially ask windows what it thinks the hostname is of that device. (Same as typing 'hostname' from a cmd windows) If you look at the Windows - Classify probe, you'll see we query for both Win32_ComputerSystem.name and Win32_ComputerSystem.domain. If you look at the sensor for that probe, you'll see that we join both name + domain to create fqdn.

Let me know if this helps.

Thanks,-Ryan

View solution in original post

Chuck Tomasi · ‎09-07-2016

Hi Tim,

This may help...

How to check fqdn in windows | Teckadmin

tim_sewell · ‎09-07-2016

That's great, but it doesn't really address my question... Do you know specifically which command(s) ServiceNow discovery uses and in which probe they are contained?

Chuck Tomasi · ‎09-07-2016

Sorry for the confusion, Tim. I don't know if it's a command or (more likely) a WMI query. It is most likely in the "Windows - Network" probe somewhere although I haven't looked closely in a while.

jake_mckenna · ‎09-08-2016

Normally in these situations we suggest setting the properties for discovery to trust WMI or SSH over what is found from the Shazzam probe aka DNS. Give that a try to validate if the your result set align better.

Properties to check:

glide.discovery.hostname.wmi_trusted

glide.discovery.hostname.snmp_trusted

glide.discovery.hostname.ssh_trusted

Setting Up Discovery - ServiceNow Wiki