Last Scanned not updating with CMDB-SCCM integration for SAM SW table

[Somnath Shilimk]

Hi Experts,

We are using SG-SCCM to pull data for our computers as well as softwares, we have SAM plugins installed, what we have observed that last_scanned attribute not getting populated for SAM softwares in cmdb_sam_sw_install.

One more observation is that only entry for Windows 10 Enterprise gets updated for last_scanned attribute.

Below steps we have taken to troubleshoot, but I come to halt further than this : 

1) Checked from Service Graph Data Visualizer, last_scanned is actually taken from attribute called u_lasthwscan, which is actually attribute in SCCM called lastHWscan

2) this SCCM lastHWscan attribute is never queried in Data Source SG-SCCM Software, but actually it is queried from Data Source SG-SCCM Computer Identity.

3) When checked from Service Graph Data Visualizer, In SG-SCCM Computer Identity, attribute u_lasthwscan is found to be transforming and putting values in 1) last_discovered AKA most recent discovery attribute on computer 2) last_scanned AKA Last Scanned on SAM sw Install table.

4) Now while transforming from u_lasthwscan to last_scanned, there is conditional script which checks if SAM plugins are install and if u_caption exists. if true then update the last_scanned on SAM sw install table.

5) now this u_caption is again found in SG-SCCM Computer Identity which actually brings Operating System value. since conditional script only checks if value exists,  it will update all softwares with last_scanned date (u_lasthwscan)

But in our case only software record it is updating with last scanned date is Windows 10k Enterprise.

I checked from IntergrationHub ETL as well, there in ISET as well, for softwares, it is taking empty values in import tables for u_lasthwscan. But when checked in computer identity, there are values available for u_lasthwscan

Best Regards,

Somnath Shilimkar.

[Patrick Quinlan]

@Somnath Shilimk We are seeing the same behavior in our environment. Have you found a solution?

[KRManning]

Has anyone found a solution? It was a known issue that was due to be fixed with Geneva Patch 8 and Helsinki Patch 2 releases (PRB667447) per another thread I saw.

[Brian Dolinar]

Glad to know it isn't just me.  We're on Utah and I updated the SCCM plugin to 3.4.0 and the only thing getting a "Last Scan" date are versions of Microsoft Windows.

[Brian Dolinar]

Determined that somehow there were SCCM Scheduled Data Import Jobs which were set to Active = FALSE and not all of them were set to Run = 'After Parent Runs' where 'Parent' = 'SG-SCCM Computer Identity' job.

Once all of the jobs were set to ACTIVE with the same Parent, the next time the Computer Identity job ran, all the Last Scanned dates starting appearing, not just for the Windows operating system records.