Windows server and Hyper V servers are 2 different CIs with same name and same serial number ,Any idea why these CI records are in de-duplication task

[Basavaraj Java1]

Hi ,We have a server with Hyper V role enabled on it ,so the discovery is  creating 2 CIs with same name and same Serial number in 2 different class ,one in windows and another one in Hyper V server class..

and these records are showing in de-duplication task, not sure why these CIs are considered as duplicate as both are different class. 

Any idea why it is thinking these CIs are  duplicate even though both are different class of CIs?

 Thanks

[Rahul Priyadars]

Seems a known i behavior .

After Discovering your Hyper-V Windows Server, you may find you have Two CIs for the same server hardware. In the case of a full Windows Server installation that has the Hyper-V role installed, this is normal, and this will explain why.

Refer kb

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0719772

Regards

RP

[Basavaraj Java1]

Thanks Rahul for the response, ok its known behavior, it creates 2 CIs one in windows and one with Hyper V Class ,actually these CIs are not duplicate.

but question is ,why these CIs are in de-duplication task ?

[Suraj6]

I am also facing same issue. why those are on duplicate dashboard and how we can stop it from getting on dashboard ?