Handling Duplicate Hardware Models

[Sam Kinney]

I am running Discovery and SCCM integration.  I have found that after implementing field normalization on the Lenovo models I am now getting duplicate "Non-normalized" models being created after SCCM imports.  What is the best method A)Merge the models and assets into one, B)Stop this from happening in the future.

Thank you

[Patrick DeCarl1]

The logic to see if model record exist is based on model name and manufacturer, NOT model number. 

To merge the records you will need to either create a background script and run to update all related records(CIs, assets, POs and other records that reference model record) to the keep model record, once that is done, you can delete the dup record. 

Did you already have field normalization installed in your instance? If not, I would had used "Normalization Data Services". 

[Sam Kinney]

Ok.  So if you have two models that are actually different model numbers, but same model name, would then enforce CI verification be the way to go to ensure the ci creates or merges with the correct asset?

[Patrick DeCarl1]

Yes that way will help. 

[Sam Kinney]

I will be doing some testing on this over the next week and will try the background script to move the assets that end up in the wrong hardware model.