Duplicate Hyper-V Virtual Machine Instances Created

[theroz]

I am setting up discovery to run in a data center that uses Microsoft Hyper-V virtualization. Our MID server is using Hyper-V probe discovery. Discovery is creating a server CI and a Hyper-V VM instance CI during the first discovery. However, during subsequent discoveries the discovery service updated the server class CI, but created a new duplicate instance of a Hyper-V VM instance CI. I did some investigating on some other threads similar to this in ServiceNow and they mentioned to check ObjectID of the VM instance. I confirmed that the ObjectID of the duplicate instances were the same, but discovery dates different. I confirmed that ObjectID is the only identifier for this class. Any ideas why discovery would create duplicate Hyper-V VM instances even though ObjectID is identical between instances?

[adilrathore]

Do the existing Hyper V records have windows_host field populated. As per below KB, you need to check if the existing original CI has a valid windows CI in "windows_host" field.

Duplicate Hyper V server CI records in CMDB

[theroz]

Thanks for replying adilrathore -

Specifically, this applies to Hyper-V VM instances CIs, not Hyper-V server CIs (I'm not seeing Hyper-V server CIs being created in my instance for some reason - but that's another thing I need to examine). The Hyper-V VM instances that have duplicates include ones that have a valid Windows server CI associated with it. So everything including the Object ID seems to meet the criteria for identification match, but it is still creating duplicates for Hyper-V VM instances.

I am planning on implementing Hyper-V discovery patterns in my test instance - maybe this will fix the issue?

[adilrathore]

Ok, so you would like to test if Hyper-V probe to pattern migration would resolve the issue.

[pratiksha5]

Did you find a solution for this?