- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2022 03:59 AM
Hi
We deployed the Service Graph Connector for Microsoft SCCM. After completing the setup we executed the Computer Identity scheduled job. However we noticed Correlation id, in the Computer table, was not populating although the resourceid field in the import set had legit values.
Using IntegrationHub ETL we discovered there was nothing mapped to the Correlation Id field, so we mapped in u_resourceid then executed the Computer Identity scheduled job again.
Only a third of the records, in the computer table, successfully populated with a correlation id the others remained blank. We had a look at the sys_object_source table and found that, in most cases, the ID column contained the resourceid/correlationid plus a pipe symbol and connectionid concatenated to it.
Any ideas why this may be happening?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2022 09:13 AM
Hi Folks - I discovered this approach is now used, in the sys_object_source table ID field, to differentiate data from different SCCM instances as Service Graph Connector for SCCM now supports connections to more than one SCCM instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2022 09:13 AM
Hi Folks - I discovered this approach is now used, in the sys_object_source table ID field, to differentiate data from different SCCM instances as Service Graph Connector for SCCM now supports connections to more than one SCCM instance.