Prevent SG-SCCM from Overwriting Normalized Manufacturer Name

Peter525
Tera Expert

Hello -

I've recently turned on Normalization Data Services to normalize the Company/Manufacturer names in our CIs, but the daily SG-SCCM import is reverting those changes. What's the best way to approach this issue? We're largely a HP shop, so we have a good number of those HP vs. Hewlett-Packard entries in our Computer CIs.

Thanks,
Peter

1 ACCEPTED SOLUTION

Hi @Alec Hanson,

 

This ended up being user error on my end. Apparently if you don't enable the Normalization API, the import via SCCM-SG will cause the previously normalized data to revert.

 

Peter525_0-1670864834604.png

-Peter

View solution in original post

6 REPLIES 6

Yousaf
Giga Sage

Hi Peter,

Check if this could relate to your problem.

Resolution

The suggested way to use a new SCCM environment is to clear out those lookups a.k.a sys_object_source records so these mismatches do not occur. IRE uses the sys_object_source to short cut the IRE identification process and uses the target sys_id to make updates to the target computer directly.

Please refer to the below steps to have a clean run

- Clear out the sys_object_source records with name = SG-SCCM
- Clear out the cmdb_serial_number table where created by 'svcSCCMIntegration'
- Run a full Intune Integration
- Run a full (not incremental - remove last run datetime for all data sources and update/save) SG-SCCM integration
- Validate in test/dev/uat to see if the issue persists.

 

Reference: KB1115658 - CI updated by SCCM Integration it's reverted to the record's correct settings by the Int...


Mark Correct or Helpful if it helps.


***Mark Correct or Helpful if it helps.***

Hi Yousaf,

That KB doesn't look applicable to us since our CIs aren't being duplicated. Our problem is with the manufacturer field reverting back to the un-normalized name.

find_real_file.png

Thanks,

Peter

Hi @Peter525 did you ever get to the bottom of this?

I assume you are using the SCCM Service graph connector?

We are just trying to figure this out ourselves, or at least check whether the integration uses the Normalization Mappings to get the Normalised name at all, looks from your issues that it does not?

Cheers

Hi @Alec Hanson,

 

This ended up being user error on my end. Apparently if you don't enable the Normalization API, the import via SCCM-SG will cause the previously normalized data to revert.

 

Peter525_0-1670864834604.png

-Peter