How does ServiceNow Discovery handle duplicate CIs when the same device is discovered from multiple

[ravivsnow]

I’m looking to understand how ServiceNow Discovery handles a scenario where the same infrastructure device is discovered from multiple sources or discovery methods.

For example, suppose a server is discovered through multiple Discovery schedules or has overlapping discovery data from different sources.

How does ServiceNow determine whether the discovered device is an existing CI or a new CI?

Specifically:

• Which role do Identification Rules and the Identification and Reconciliation Engine (IRE) play?
• How are duplicate CIs prevented?
• What happens when different sources provide conflicting attribute values?
• How do Reconciliation Rules determine which source should update the CI?

I’m interested in understanding the end-to-end flow from Discovery → IRE → Identification Rules → Reconciliation Rules → CMDB.

[Mark Manders]

Looking at the questions you are asking, I'd advise you to go to NowLearning and take the CMDB course where everything is explained. That would give a way better understanding than just answering these questions. You can even just skip to IRE if you don't want to understand everything.

[Harish Bainsla]

Hi @ravivsnow  check below link

https://www.servicenow.com/community/itom-articles/servicenow-duplicate-cis-solution-script-report/t...

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

https://youtu.be/v16ruSaV1Rk?si=ghWdXNX40RNcL8M4

If my answer helps you mark helpful and accept solution