vmWare Virtual Machine Instance upon discovery does not show serial number of VM instance and as a result does not merge Windows Server CI with VM instance CI

[Misana]

We have enabled Horizontal discovery in our client environment and are discovering both Windows Server (OS) CIs along with vCenter discovery (and it's children). We are now showing duplication with vmWare Virtual Machine Instance CIs and corresponding Windows Server CIs. According to my brief reading, a business rule is supposed to run to match the 2 based on serial number, however, the vm instance is not capturing the serial number yet the Windows OS CI is showing the related VM serial number? What could be the cause for this?

[David104]

Hi Misana,

When you say duplicates between Virtual Machine Instance CI's and Server CI's, do you mean that they are not being related to each other, or are you expecting them to be merged? What you should see is that the two CI's both exist and a realtionship is created between them. The serial number gathered from horizontal discovery on the Server CI will (hopefully) be the vm guest serial number. I don't recall if the serial is also captured from vcenter on the Virtual Machine Instance, but I'm pretty sure it is.

Do you see a relationship between the VMI and Server CI's?

They often cause confusion to users as when they search for a server name, they will get two CI's returned, so you may like to filter them out of CI searchs on incident/change forms etc

Regards,

David

[Abdul Parveez]

@Misana - did get this fixed? what was the issue?