CIs not creating/updating after deleting sys_object_source and rerunning SCCM Integration

[chintuchairmen]

Hi community,

I am troubleshooting an SCCM CI attribute-flipping issue (has changed ownership, name, serial number, manufacturer, RAM, and location several times). To test, I am trying to re-import a specific set of records, but the target CIs are not being created or updated.

Steps taken:

1. Identified records by Resource ID.
2. Deleted the corresponding records from sys_object_source to break the correlation.
3. Reran the SCCM Import Schedule

Even after running the schedule the ci are not getting updated and generated..  The current integration uses MECM/SCCM ResourceID as the unique identifier for CIs.  

Any solution apart from this?

[abbasshaik4]

Hi @chintuchairmen,

Please refer to the link below:
Solved: SCCM Resource ID Creates sys_object_source Entry A... - ServiceNow Community

If it is helpful, please mark it as helpful and accept the correct solution by referring to the solution in the future it will be helpful to them.

Thanks & Regards,

Abbas Shaik