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

[kalyani8]

Hi 

Thanks so much for the quick response.

Are you saying to add SG-SCCM as a data source in Reconciliation rules?

Its not working for us.

Thanks

[Ian Mildon]

As part of the initial setup of Service Graph it has you do a test load; which populates the Last Run Datetime field on the Computer Identity data source.

I just recently completed our first full run of Service Graph on our production instance (after clearing the timestamp) and it certainly stamped all the records with SG-SCCM as the discovery source

[Anton15]

Hi Ian - thanks for that. We had the 'Use last run datetime' unchecked before the first full SG run. Did you migrate from the SCCM 2016 Integration plugin?

[Ian Mildon]

Our previous setup was using SCCM 2012 v2.

We have just completed the switch over to Service Graph Connector Microsoft SCCM on our instances and completed the initial "full" import/transform of all records from the SCCM database.