Hyper-V Discovery and Duplicate Windows Server

[bharath10]

Hello All,

just want to know is anyone facing same issue.

Hyper-V Discovery and Duplicate Windows Server gets created.

having 3 ci's with same name.
i can understand that Hyper-v Server discover it created one ci in hyper-v class and one ci in windows server class.

but here hyper-v 1(virtual is true) 
Windows Server class 2(one is virtual other is not virtual), both windows server having same serial number.
both windows servers created on same time and created by same mid.

Why duplicate ci created.
how windows server with virtual is false, determine as duplicate (in discovery source)
how can avoid these kind of case OR duplicate ci creation in cmdb.

does any new identification rule require or can be customized existing one. (cmdb_identifier)

London release.

Thanks for any help or suggestion.

[DaveHertel]

Hi-  If duplicates are coming into your CMDB, then look at the identifier rules that are set for the CI type(s) you are troubleshooting, ie.. Windows, Virtual machines, etc.   Its possible the out of the box CI identifier Rules may need to be adjusted for your unique needs -- see the Discovery Identification engine docs for more details on Disco identifiers.   These rules/criteria are responsible for uniquely identifying CI's in the CMDB, so when dups are getting into the CMBD, the ID rules for each class/type is a good place to start troubleshooting.

Hope this helps?

[Damhoej]

could it be that a hyper-v server is linked to a windows server (and both have an asset linked pr. default)

A hyper-v virtualization server ESX has an attribute called "windows host" thst referres to the Windows server class.

Can that be the reason for your experience?

You can find the relation under suggested relationships.