Service Graph Connector for SCCM, all tables not being captured to update set?

[Juha-Matti]

My goal is to configure Service Graph Connector for SCCM in our dev environment and take the configuration from there to test and prod. While doing the configuration I noticed that Graph Connector for SCCM configurations are captured only partially to update set. For example, the tables sn_sccm_integrate_instance_member and sn_sccm_integrate_instance are not captured.

The table sn_sccm_integrate_instance has a record of the configured SCCM instance and the sys_id of the instance is being referenced to in multiple places, for example SCCM Computer Identity transform map (u_connectionid) and several script functions of the script include SCCMMultiDataSourceUtil.

If you have done the same, how have you taken the configuration from dev to prod? Did you include the missing tables or go with the configuration that was captured?

It seems that the data sources, schedules and transform maps do transfer, and it looks like everything is working. However, I'm puzzled if this is the way.

[CMDB Whisperer]

I can confirm that this is extremely difficult and unreliable.  I have tried multiple times and have failed 100% of the time.  There seems to be some incongruity in the Application scopes applied to the Update records and Update sets, as well as some instance-specific information that was captured in the updates if I recall correctly.  As a result my changes would fail to promote every time.  My hunch is that something in the IntegrationHub-ETL application isn't working correctly in its capturing of updates, and perhaps making the RTE changes directly is a solution.  I'm not convinced it isn't user error on my part, and at one time I was determined to find the cause and solution but I never did and eventually moved on.

[Juha-Matti]

Thanks for your reply! 

In addition to asking here I created a ticket to ServiceNow and they replied, that the recommended way to set up the integration is to configure it in each instance separately (and not use update sets to transfer the configuration). So probably I'll just move on and configure it as they recommended.