Hyper-V Server pattern steps do not differentiate identification fields from Windows Server, causing conflicts with duplicate remediatorDescriptionYou notice a high volume of deduplication tasks between Windows Servers and Hyper-V ServersSteps to Reproduce Discover Windows Servers running Hyper-Role, and then run CMDB Health jobs.WorkaroundThis problem has been fixed, in the September 2022 version of the "Visibility Content" app v6.1.0, and later. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. After upgrading, the "Windows OS - Servers" Pattern step "Insert data to cmdb_ci_hyper_v_server" now uses the true name/serial number in the Windows Server CI, and adds a "@Hyper-V Server" suffix to the name, and "_hyper_v_server" suffix to the Serial Number of the Hyper-V Server CI. The "Hyper-V Server" Pattern, when creating just a single Hyper-V Server CI for Hyper-V only editions, does still use the true Name/Serial. More details on the general design of this pattern is in: KB0719772 Discovery creates 2 Server CIs for Hyper-V (Windows Server + Hyper-V Server) - Known issues with this designRelated Problem: PRB1564552