Resolve De-Duplicate Tasks made from the CMDB Health jobs running

[galaxypwm]

Hi,

My boss wants me to find out how to resolve the De-Duplicate Tasks that are created whenever the CMDB Health job runs and detects duplicate CIs. I need to know how to resolve the tasks without deleting any of the CIs even if they are duplicates. Is there a way to do this without deleting anything?

Paul

[Michael160]

Thank you Manish.   In my review of the other community post you reference.   I see an entry by Richard Brounstein.   "The thing is, as of Jakarta, even if a server's operational_status is marked as "non-operational", it will still consider this server on Discovery and if the attributes match the CI Identifier rule, it will overwrite it or mark it as a duplicate if there are more than one with matching attributes."   This indicates to me the issue is not resolved by updating the operationa_status?   (have you tested)

[Phil32]

I can't find anywhere in the documentation that says if relationships to INC or CHG is update to the Master CI, or remains with the duplicate CIs

[emir]

This is documented on the Default related items list section of: https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/configuration-management...

In the Remediation Screen, on the Merge Relationships and Related Items step, you can choose if you want to Merge all relationships from the duplicate CIs to the master CI or Do not merge relationships from the duplicate CIs to the master CI.

Change and Incident are available for out of the box unless you modify Duplicate CI Remediator Default Related Items