SCCM for SAM Pro: issues with imports of software installs and software last used data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 01:35 AM - edited 12-22-2022 02:37 AM
Hi SAM Pro Superstars,
We're implementing SAM Pro for a client who has SCCM 2016 integration up and running (migration to SCCM Service Graph Connector is out of scope). We ran sanity checks on data we see in ServiceNow in cmdb_sam_sw_install and cmdb_sam_sw_usage (and the staging table for Software Last Used data source imp_sccm2016_software_last_used) - we see large differences between SCCM and ServiceNow. What would you do to:
1. Ensure all software installation records from SCCM are brought into ServiceNow? (We have identified records on SCCM side installed on specific computers or installations of specific software products that are for some reason not imported)
2. Ensure all software last used records for software products defined in the reclamation rules (e.g. SnagIt) are imported into ServiceNow. We see the SQL query in the scheduled import being correctly built but only a small fraction of available records are being imported into the staging table (imp_sccm2016_software_last_used)
Any ideas? Any hints? Anything we might be missing? Any resources you know that can help troubleshoot on ServiceNow side?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-23-2022 05:35 AM
Hi Michal,
This sounds like a data last-used condition that could impact your result set. Pulling that back to an earlier date and rerunning the import helps with the missing data analysis. This is all managed on the data sources for the SCCM JDBC connections. If you do this, could you make sure you run checks on the counts and validate if imports against retired machines also happened to clean those records up. Sometimes rolling it back 1 year, for example, helps pull in missing records.
