- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2023 04:44 PM - edited 10-24-2023 07:25 AM
Hello experts,
We are having a recurring issue with relationships health reporting windows and Hyper-V servers as duplicates, (see attached). The machines themselves were discovered a while back and exist in their own class table, have the same name, and have had tasks created since the platform was installed . We have updated all the plugins and are still having this issue. We would like to resolve this issue. Has anyone else experienced this as well? If so, how did you resolve it. Any guidance will be greatly appreciated.
Thanks in advance.
-Juan
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2023 06:41 AM
This seems to be an issue that had been corrected by ServiceNow already. Have you checked this KB? Hyper-V Server pattern steps do not differentiate identification fields from Windows Server, causing...
Maybe it is a Pattern that needs to be updated? Have you also checked that the relationships between the Hyper-V and Windows Servers are properly set? Worth checking.
Other than that, was the Identification Rule for these classes updated? This is also another important point to be confirmed as it is the base rule for the IRE to create de-duplication tasks. I hope this helps you.
Please, mark my response as helpful 👍 in case it helped you. Also, please mark the question as answered in case your issue was solved. This really helps future readers.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2023 06:41 AM
This seems to be an issue that had been corrected by ServiceNow already. Have you checked this KB? Hyper-V Server pattern steps do not differentiate identification fields from Windows Server, causing...
Maybe it is a Pattern that needs to be updated? Have you also checked that the relationships between the Hyper-V and Windows Servers are properly set? Worth checking.
Other than that, was the Identification Rule for these classes updated? This is also another important point to be confirmed as it is the base rule for the IRE to create de-duplication tasks. I hope this helps you.
Please, mark my response as helpful 👍 in case it helped you. Also, please mark the question as answered in case your issue was solved. This really helps future readers.