HostName is different in discovery and Actual

[Kamal Sharma]

Hi Team,

I am doing a windows server discovery in which getting the hostname different in discovery (CMDB) but in Actual  (on Host) is different.

Hostname In discovery (Under Device tab) or CMDB is ---  ip-172-xx-xx-xxx

Hostname in Actual  (On server) -- SYsxxxxAWS

What is the root cause for this, please help me to correct it.

[Ashutosh Munot1]

Hi,

On your machine check this:

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Hostname

What this returns. Also check Windows Classify probe output which you get.

Thanks,
Ashutosh

[Kamal Sharma]

Hi Ashutosh

I have checked the registry path and found host name is correct as per given

But unable to find the correct hostname in below XML (Windows classify probe output)

<parameters>

<parameter name="port_probe" value="9802b18f0a0a0703009d322d5b5540e5"/>

<parameter name="mid_selector_details" value="{"mode":"specific_mid"}"/>

<parameter name="discover" value="CIs"/>

<parameter name="glide.xmlhelper.trim.enable" value="true"/>

<parameter name="output_format" value="json"/>

<parameter name="use_class" value="discovery_classy_windows"/>

<parameter name="port" value="135"/>

<parameter name="cidata" value="<CIData><data><fld name="ip_address">172.xx.xx.212</fld><fld name="dns_name">ip-172-xx-xx-212.ec2.internal</fld><fld name="name">ip-172.xx.xx.212</fld><fld name="dns_domain">ec2.internal</fld></data></CIData>"/>

<parameter name="used_by_discovery" value="true"/>

<parameter name="probe_name" value="Windows - Classify"/>

<parameter name="probe" value="b11360600a0a0ba500c41bcbae55c5c4"/>

<parameter name="WMI_FetchData" value="root\virtualization\v2\Msvm_ComputerSystem.Name,HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Domain,HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Hostname,root\MSCluster\MSCluster_Resource.PrivateProperties,root\MSCluster\MSCluster_Resource.Name,root\MSCluster\MSCluster_Node.Name,root\MSCluster\MSCluster_Cluster.Name,root\MSCluster\MSCluster_ClusterToResource.GroupComponent,root\MSCluster\MSCluster_ClusterToResource.PartComponent,root\MSCluster\MSCluster_ClusterToNode.Antecedent,root\MSCluster\MSCluster_ClusterToNode.Dependent,root\virtualization\Msvm_ComputerSystem.Name,root\MSCluster\MSCluster_Resource.Type,Win32_ComputerSystem.Domain,Win32_ComputerSystem.Name,Win32_OperatingSystem.Caption,Win32_OperatingSystem.Version"/>

<parameter name="credential_id" value="7d3a7a0cdb0e44504df4ab92ca9619b3"/>

</parameters>

[Ashutosh Munot1]

HI,

This is output queue show me input queue and also check the property martin mentioned.

Thanks,
Ashutosh

[Kamal Sharma]

Hi Ashutosh

I can see the correct data in input as well.

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<results probe_time="3141" result_code="0">
<result>
<output>
{"wmi": {"Win32_ComputerSystem": {"Domain": "WORKGROUP","Name": "SYSxxxxxAWS"},"Win32_OperatingSystem": {"Caption": "Microsoft Windows Server 2016 Datacenter","Version": "10.0.14393"}},"registry": [{ "Path": "HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters","Domain": "","Hostname": "SYSxxxxxAWS"}]}
</output>
</result>
<parameters>
<parameter name="mid_selector_details" value="{"mode":"specific_mid"}"/>
<parameter name="agent" value="mid.server.AWS"/>
<parameter name="glide.xmlhelper.trim.enable" value="true"/>
<parameter name="use_class" value="discovery_classy_windows"/>
<parameter name="source" value="172.xx.xx.212"/>
<parameter name="WMI_FetchData" value="root\virtualization\v2\Msvm_ComputerSystem.Name,HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Domain,HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/Hostname,root\MSCluster\MSCluster_Resource.PrivateProperties,root\MSCluster\MSCluster_Resource.Name,root\MSCluster\MSCluster_Node.Name,root\MSCluster\MSCluster_Cluster.Name,root\MSCluster\MSCluster_ClusterToResource.GroupComponent,root\MSCluster\MSCluster_ClusterToResource.PartComponent,root\MSCluster\MSCluster_ClusterToNode.Antecedent,root\MSCluster\MSCluster_ClusterToNode.Dependent,root\virtualization\Msvm_ComputerSystem.Name,root\MSCluster\MSCluster_Resource.Type,Win32_ComputerSystem.Domain,Win32_ComputerSystem.Name,Win32_OperatingSystem.Caption,Win32_OperatingSystem.Version"/>
<parameter name="port_probe" value="9802b18f0a0a0703009d322d5b5540e5"/>
<parameter name="sys_id" value="d2eb2ee3db0058104df4ab92ca961996"/>
<parameter name="from_host" value=""/>
<parameter name="output_format" value="json"/>
<parameter name="sys_created_on" value="2020-04-14 16:39:26"/>
<parameter name="sys_domain" value="global"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="state" value="ready"/>
<parameter name="probe_name" value="Windows - Classify"/>
<parameter name="discover" value="CIs"/>
<parameter name="response_to" value="1aeb2ee3db0058104df4ab92ca961982"/>
<parameter name="from_sys_id" value=""/>
<parameter name="priority" value="0"/>
<parameter name="agent_correlator" value="7babaea3db0058104df4ab92ca9619d0"/>
<parameter name="probe" value="b11360600a0a0ba500c41bcbae55c5c4"/>
<parameter name="processed" value=""/>
<parameter name="error_string" value=""/>
<parameter name="sequence" value="171798f4b040000001"/>
<parameter name="port" value="135"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">172.xx.xx.212</fld><fld name="dns_name">ip-172-xx-xx-212.ec2.internal</fld><fld name="name">ip-172-xx-xx-212</fld><fld name="dns_domain">ec2.internal</fld></data></CIData>"/>
<parameter name="name" value="WMI: Classify"/>
<parameter name="topic" value="WMIRunner"/>
<parameter name="queue" value="output"/>
<parameter name="ecc_queue" value="d2eb2ee3db0058104df4ab92ca961996"/>
<parameter name="credential_id" value="7d3a7a0cdb0e44504df4ab92ca9619b3"/>
</parameters>
</results>

Regarding Martin's suggestion, I have already made it "True" and rediscovered but no changes.