De-duplicate task

[Test97]

As per the document, if IRE finds out duplication then it updates the CI instead of creating a new.

"After an initial import, the Microsoft Intune device ID, connection name, and Discovery Source are populated in the Source [sys_object_source] table. In subsequent imports:

1. If incoming Microsoft Intune data contains a device ID, connection name and Discovery Source that matches an existing CI in the Source [sys_object_source] table, the system updates the referenced target CI in the CMDB. 
2. If no match is found on the device ID, connection name , and Discovery Source in the Source [sys_object_source] table, the system attempts to use identification rules to match on attributes such as name, serial number, etc. to determine if the CI is in the CMDB. 
3. If a match is found using identification rules, the CI is updated.
4. If no match is found using identification rules, a new CI is created."

Then as IRE will update if it catches some duplicate CI, then why and how de-duplicate task gets created?

Anyone can elaborate this?

Thank you.

[Wojtek Winnicki]

Hello @Test97 

can you please specify what is the issue?

In our question you are mixing two terms - CI Identification and De-duplicate tasks.

ServiceNow is using the IRE and specificly the Identification Rules to distinguish the unique CI and based on this rules create the new CI or update the exisitng one. For example for the Hardware CI there is rule that checks if any Hardware CI exist with the given serial number. Let's say you already have Hardware CI with the XYZ serial number (from the Discovery, manual load etc.) and CI with the same serial number comes from the SG Intune IRE will update the existing CI.

On top of that, as a part of the CMDB Health, you have a job that checks the CIs based on the Identification Rules to determine the duplicates and create the De-Duplication Tasks. However this job does not runs on the creation/update of the CI, but it runs on schedule basis (daily)