Which Specific Windows Command(s) Retrieve FQDN?

[tim_sewell]

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.  

[tim_sewell]

Thanks for the info Jake.   I looked into our discovery properties and verified that we do have glide.discovery.hostname.wmi_trusted set to true.   I went ahead and cleared out the fqdn value on one of the CIs and reran a discovery, just to make sure, but it filled in the incorrect value again.

Any leads on the actual command that is used to pull the fqdn?  

[Ryan Zulli · Accepted solution]

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

[tim_sewell]

Perfect, this is exactly what I was looking for.   Thanks for all of your help.