SG-SCCM - De-duplication Tasks Created based on Correlation ID

[Will O]

After updating SG-SCCM to latest version (3.4.2), it does import Computers records having "generic" or invalid serial numbers (for example, To Be Filled by O.E.M., or System Serial Number) but De-duplication tasks began to be generated based on "matching Correlation IDs" even though the computers all had unique SCCM Resource IDs (we populate Correlation ID based on SCCM Resource ID).

ServiceNow Support guidance was to remove "Correlation ID" from the CI Class Manager Identification Rule for Hardware (which applies to Computer) as that was a customization we made within our organization.  After making this change in a sub-prod instance, the De-Deduplication Tasks have stopped based on "matching" Correlation IDs. However, I am concerned about any potential impact removing Correlation ID from the Computer CI Identification Rule might have on the SG-SCCM Import.

My understanding is that Sys_Object_Source table requires the SCCM Resource ID for initial matching during the SG-SCCM import.  If Correlation ID (SCCM Resource ID) is removed from the Computer CI Identification Rule, does it have any impact to the Sys_Object_Source process related to SG-SCCM?  

The Computer CI Identification Rule was matching on Correlation ID (SCCM Resource ID) first, and then Serial Number, etc.  Now, the rule ignores Correlation ID and matches first on Serial Number.  Does SG-SCCM really work outside of IRE and runs first to find a match on Sys_Object_Source?  Then, if it can't find a match on Connection ID, it goes to IRE?

Thanks for reading this and for any input you might provide!

[Will O · Accepted solution]

Does removing Correlation ID from the CI Identification Rule impact SG-SCCM import?

No, it does not impact the initial matching done by SG-SCCM via sys_object_source.

That process is independent of the CI Identification Rule.

However, it does impact fallback matching via IRE, which may now be less precise if serial numbers are generic or duplicated.