Service Graph Connector for Microsoft SCCM - IRE Local Language Relationship Translation Issue

For example, to run the script for SCCM scoped application: var util = new CMDBIntegrationMetaDataFixUtil();

util.addRelTypeMapping("SG-SCCM");

12. The above script run will create the necessary meta data to fix this translation issue and send some debug output messages to the screen. It typically runs very quick under a minute.13. Capture that info messages in to a text file for any reference later in case of an issue14. Go to your scoped application import schedule and kick off the parent job. For example, the computer identity will be the parent job for SCCM which will run all the children as well.15. Validate the output like you normally will for your application run, especially checking if the relationship were correctly created in cmdb_rel_ci table

16. Perform any other validations as necessary.

Q&As from case tasks:

1. Will it resolve the issue once we apply the script?

Yes, it needs to be run as a background script within your application scope

2. Can we recognize that we can apply the script on our Rome and Japanese environment?

Yes, it can be applied to Rome and the language of the running user does not matter

3. Could you please let me know the way how to apply the scripts? The steps are documented under 'Steps below on how to run the script include:' section documented

above in this post.

4. If we apply the scripts then does it have official support? The script is provided as a work around for a single issue. Yes, the SG connector will still be supported. All we request is that you test the script in a dev/uat/test with your production like data to make sure it resolves the translation issue first before applying this directly in a production instance as a safeguard for

any unforeseen issues.

5. Could you please let us know the notification points. For example, when we make upgrade from Rome to San Diego then we need to delete the scripts in advance? If you prefer, you may delete the script but it is not necessary. The script is only run by a user and on demand. On upgrade, the changes made by the script will still exist. There won't be any impact with respect to this change and the integration will run as normal.

Labels: