Controlling and consolidating the Normalization Services
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Dear HAM or HAMpro admins and gurus -
I want to ask if anyone else out there is having issues recently with Normalization Services for Hardware Models? Especially for Lenovo workstation models and Xerox and HP printer models.
AND do you use all the Service Graph Connectors like we do? SG-Intune, SG-Jamf, SG-SCCM, SG-AWS
We pull all of them daily, thus, the stressor of keeping Hardware Models clean and fresh is burdensome.
Put in a Support ticket and this is the explanation, which I understand but feels like some 'that is the way it is' and wanted to know if anyone else has had recent success keeping their Hardware Models lists clean?
KB2649239 - Hardware models created by Service Graph Connectors do not match existing hardware models
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2649239
The struggle I have, I have tried doing the matchy-matchy name but new models seem to move my CIs and either partially orphan some Hardware Models while spreading out the same model number into several records.
*AND* new models are often auto-created **without the Model Number field populated**, causing the widget on the HAM Workspace to yell that we have models with no model number in them (that were created by the imports)....
I felt like I had a handle on the Hardware Models in mid 2025, Normalization Services and wrangling the Hardware Models list into a fairly consistent state but since *about* Yokohama Patch4, it has been chaotic. We are currently on Yokohama Patch10HF1, using HAMPro and will be going to Australia in May 2026.
Mostly work to keep the models clean and consolidated for Apple, Lenovo, Xerox, HP and Zebra.
Any stories, advice, focus items, help is appreciated...
- Mark
