SCCM job for removed software is deleting ALL software from SCCM in cmdb_sam_sw_install

[David77]

We've been running SG-SCCM for some time successfully.  We were only interested in servers and computer CI hardware data, but not software. 

However, we recently implemented SAM-Pro and that's when we noticed that while the "SG-SCCM Software" job will populate table cmdb_sam_sw_install, when later the "SG-SCCM Removed Software" job runs it then deletes ALL the titles just put there.  We have not customized anything in the SG-SCCM setup.

if we don't run the Removed Software job, then all the titles from SCCM stay in cmdb_sam_sw_install.
We can watch the titles being deleted as the remove job runs. 

While we have a case open w NOW Support, so far they don't have an explanation.

Has anyone else run into this problem, and if yes, please share the remediation.

Thanks!

[JohnC1]

Thanks for the reply.  We're definitely only running just SG-SCCM Software for now.  We've not used Asset Intelligence, so have never used the AI sources.

We wanted to see what the impact would be if we were to run removed software, but the results were not what we were expecting, which was the removal of everything.  I was able to replicate that issue in two of our lower environments right after we migrated to Zurich and had those lower environments recently cloned from our production environment.

Feel free to share that with ServiceNow.  Would love to know how this turns out for you.

[David77]

Here's what we were instructed to do and it seems to be working

Next Steps:
1) Remove all records from cmdb_software_instance that were created from a Service Graph, this impact would be seen on any SG not just SG-SCCM.
2) Customer to remove all sys_object_source records where name=SG-SCCM and target table is cmdb_software_instance.
3) Clear out last run datetime on the datasources for SG-SCCM.
4) Allow the scheduled job to run and in turn a full import.
5) Software should work after that point, please verify this now.

They are claiming that during SAM-Pro setup, the step to migrate records did not work correctly. 

[JohnC1]

Thanks for that update.  We'll try that recommendation in a few days.  We don't use SAM-Pro, so I'm curious on what our results will be.