Discovery for Vcenter and ESX Hosts - Wrong Serial no overwritten!!

[anubhavkapoor76]

Hey Folks,

I have a question regarding the discovery of Vmware Vcenter Server which I am trying to discover in my organization network.

Step 1. When I trigger the Quick Discovery with IP and Mid Server it finds the Vcenter, clusters and ESX Servers as seen in Discovery Log.

Step 2 As seen in Log when it finds the Vcenter through "windows Identity" probe then the serial no updated is correct one i.e field "serial_number" under Windows Server Class.

Step 3. During the last phase of Discovery the proble "VMWare - vcenter" replaces the serial no of Vcenter by serial nos of one of the ESX's serial no.

So we are ending up with wring serial no of the Vcenter host ( Windows Server).

I raised the incident with Service Now however looking for assistance in the community for various leaders to reply back.

Please let me know that is it a known issue or need some fix. Any help will be much appreciated.

[anubhavkapoor76 · Accepted solution]

Hi...Does anyone has answer to this query which I raised?

Update: As read from standard docs from ServiceNow: "ESX server discovery is done through vCenter. Do not specify the IP address of the ESX server in a Discovery Schedule. Instead, discover the vCenter through the Discovery Schedule".

Now As per ServiceNow Support Team when the VmWare probe runs then actually "ServiceTag" (which is serial no for ESX Server) replaces the Serial No for Windows Server (vCenter - for which the actual serial no was discovered by Windows Identity Probe).

Any help would be much appreciated.