Having issues with SCCM integrations into SN after SCCM server upgrade - Resource IDs changed

[koliva]

Our operations group had to upgrade their SCCM server last month.  When they do this, the resource ids completely change for the computers.  When SCCM integration into SN runs, it messes everything up.

We ran into this 2 years ago.  I worked with HI support and I think what we had to do was delete all records from sys_object_source and cmdb_serial_numbers and then it recreated these with the new resource ids.

Here we are 2 years later and it's a problem again.  I'm in the process of deleting records from those tables and will run the import to see if it fixes it; this is in our dev instance.

I found this on community which is similar to my issue:  https://community.servicenow.com/community?id=community_question&sys_id=227503eddbd8dbc01dcaf3231f961971&view_source=searchResult

Is there a better way around this issue?  

Thank you.

[Anton15]

Hi

Thank you for the quick reply. yes, customers I've worked with have had similar problems with resource / correlation ID. Another thing that's worth checking is if CorrelationID is an IRE Identification attribute, this is a legacy setting from previous SCCM 2016 Integrations and should be removed as resourceid|connectionstring in the source table is the primary identification for SG SCCM.

[koliva]

I believe we took that out of the IRE and it still was using it in the service graph.  

If you have had several customers with the same issue, I would suggest reporting it to servicenow.  I think the more they hear that it is an issue, the more apt they will be to fix it.  What we have in place is a workaround that I really don't like having to do.  We are messing with data to get around this issue because support won't fix it.