Service Graph SCCM Connector Discovery Source not Updating

[Anton15]

Hi Folks

Recently we migrated from the SCCM 2016 Integration plugin to the Service Graph SCCM Connector. After executing the connector, we noticed that only 7,000 out of 25,000 computers had a Discovery Source of ‘SG-SCCM’ the remaining 18,000 computers retained the Discovery Source ‘SCCM’

So we opened each of the IH ETL Service Graph SCCM Robust Transforms and found that the Discovery Source field was not mapped in any transform.

Two questions…

1) Why did 7000 computers have the correct discovery source value?

2) Why did 18,000 retain the old discovery source value?

Thanks

[#2]

First, the discovery source field does not have to be mapped for CMDB tables.  It is populated via the IRE payload which will have the discovery source from the RTE definition.

As to possible reasons why I suspect 1 of the following:

1) You are running an incremental data pull by leveraging the "Use last run datetime" field on the SG-SCCM Computer Identity data source.  This would only bring in recent records from SCCM.

2) The last scan date is not the most recent scan date for the CIs that are not being updated.  IE: there is another source that has a more recent or equal scan time.  For instance your old SCCM integration may have the same scan time as the SG SCCM integration.  This would not update the discovery source value.

I would suggest you look into the sys_object_source table to get a better understanding of which records are being updated by each data source and their scan dates.  You can pick one record that is not being updated and filter the sys_object_source table by that sys_id.

[Anton15]

Thanks for replying, this is a real head scratcher!

Regarding…

1)  The " Use last run datetime" field on the SG-SCCM Computer Identity data source was not checked – so that’s ruled out.

2) Every computer imported during the first run of SG, created a new record in the sys_object_source table with ‘Name’ = SG-SCCM. I checked half a dozen records, that hadn’t been updated to ‘SG-SCCM’, and in every case the SG-SCCM scan date was more recent than any other source (which is only the old deactivated SCCM integration)

I also tried modifying the out the box SG-SCCM Computer Identity RTE definition to include a mapping to Discovery Source from discovery_source – which is set to a fixed column value of ‘SG-SCCM’. But that didn’t help.

In short, existing computer records are being updated as attribute value changes (as they should) but Discovery Source isn’t always.

I’ll investigate the computer records that have updated to SG-SCCM  - hopefully I’ll see a pattern that might shed some light

[kalyani8]

Hi,

We are facing the same issue. Able to find the data in import sets but the discovery source is not set to SG-SCCM. Did you find a solution for this?

Thanks

[Anton15]

Hi

Yes we did - it was a bit of an oversight, however the solution was to add SG-SCCM as a new attribute within the Reconciliation Rules (think CI Class Manager)  🙂