With SG-SCCM version 2.5, Organization Unit (OU) information from SCCM is pulled in and populated in a related table. We are seeing cases where there are multiple OUs for a resource id (computer) which results in multiple computer records in the computer import set table. This will not result in duplicates in CMDB but could potentially increase the processing time for computer data source.
We have a defect (DEF0244656) opened for this issue -
https://buildtools1.service-now.com/nav_to.do?uri=%2Fx_snc_defect_defect.do%3Fsys_id%3Dfca[…]84288%26sysparm_record_list%3DORDERBYDESCsys_updated_on
Work around to avoid duplicates in import set and not bring in OU information until the defect is fixed:
1. Open up SG-SCCM Computer Identity data source and go the SQL statement section
2. Replace this SQL line:
v_RA_System_SystemOUName.System_OU_Name0 as OUName,
With:
null as OUName,
3. Remove the following JOIN and save it
LEFT JOIN v_RA_System_SystemOUName ON v_GS_COMPUTER_SYSTEM.ResourceID =
v_RA_System_SystemOUName.ResourceID
4. Test run the SG-SCCM Computer Identity data source to make sure that the above change did not
bring in duplicate computer records in the import set table and records processed successfully
