
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
In a recent blog post, I explained how to change the target class for a JAMF integration. Since then, someone asked how to do the same for an SCCM integration. Let’s walk through how to modify the target class for SCCM.
SG-SCCM Computer Identity Integration Hub ETL:
Step 2. Prepare Source Data for Mapping, you will find a custom transform called sys_class_name_2. This custom transform takes two input fields: u_system_role & cleansed_os_software. If you click on the 3 lines, and select View Transform, you will see the inputs, and scripting.
To view the logic more easily, click the Pop Out Script Editor at the bottom of the side window. In the script, you’ll notice that based on the values of (u_system_role input) and/or os_name (cleaned_os_software input) the script returns one of several target classes.
a) If no system role is provided → returns cmdb_ci_computer
b) If system role is SERVER and OS is Linux → returns cmdb_ci_linux_server
c) If system role is SERVER and OS is Windows → returns cmdb_ci_win_server
d) If system role is SERVER and OS is not specified → returns cmdb_ci_server
e) If system role is not SERVER → returns cmdb_ci_computer
As you can see, by changing A and E above to cmdb_ci_pc_hardware, the target class will be updated.
Step 3: No mapping change is needed under SCCM Computer Identity – Computer. The sys_class_name_2 is already mapped so changing the script is all that is needed.
Step 4: Run the integration and confirm the target class is correct.
Thanks for reading!
- 266 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.