Discovery and unexpected Lenovo computer model information

[jas101]

Hi everyone.

We have noticed that Discovery is not pulling in Lenovo computer model names/numbers as expected which is causing problems when it comes to reporting etc. Dell machines populate Model ID as follows e.g. Dell Inc. OptiPlex 760 which is logical/great. Lenovo CIs on the other hand populate model IDs as e.g. Lenovo 4291YYH

I.e. with all seemingly unique model IDs (not the serial tags) whereas here we would expect e.g. Lenovo ThinkPad X1 Carbon, Lenovo ThinkCentre M93p Tiny or Lenovo ThinkPad X220 (we have only 3 different models in use currently).

Our EUC team have identified that this happens because Lenovo stores their "ModelName" in a different WMI class than other vendors (Win32_ComputerSystemProduct as opposed to Win32_ComputerSystem).

I'm presuming plenty of other organisations must have experienced this issue and if so how have you guys remedied it? Is it possible to customise the probe to bring back Win32_ComputerSystemProduct for Lenovos only!?

We have observed that the start of model IDs are consistent with the actual model e.g.

ServiceNow Display Name	Actual Model Name
Lenovo 10AAxxxxxx	Lenovo ThinkCentre M93p Tiny
Lenovo 10ABxxxxxx	Lenovo ThinkCentre M93p Tiny
Lenovo 20BSxxxxxx	Lenovo ThinkPad X1 Carbon 3rd Gen
Lenovo 20BTxxxxxx	Lenovo ThinkPad X1 Carbon 3rd Gen
Lenovo 429xxxx	Lenovo ThinkPad X220

So I'm presuming we could create a business rule - although Discovery would overwrite this info each time it scans right? I.e. far better to fix at source presumably.

Any help much appreciated, I still await Hi's feedback on this.

Many thanks!

Daniel

[CMDB Whisperer]

Hey Ben, I know this response is old but we're still seeing this consistent behavior with Lenovo devices, and I'm wondering if ServiceNow's position on this has changed at all now that we have HAM Pro.  The content library for HAM seems to be sticking with the OOTB model numbers that would be discovered by Discovery/SCCM.  Interestingly, however, they still don't normalize the same way that other models do in HAM; I'm guessing the content curation team might still be scratching their heads about what to do about this, since the mappings aren't working correctly, but every indication seems to be that this is being set up to use the OOTB model numbers instead of the model families reported by Lenovo, and as such the Field Normalization mappings will no longer work.  This seems like a bit of a quagmire.  Wondering if you have any insights into it.

[Carlos Chaluisa]

I know this thread is a bit old but I am working the same issue so perhaps some of you could help.  I activated Field Normalization, configured the Normal values, rules etc.  When it runs it does updates the fields as expected.  Now, what I am missing is how to make it run on schedule.  When new laptops are discovered, they show up with the weird model number. 

Any help would be greatly appreciated

[Martin Bublitz1]

To resolve this using patterns, I created the following extension to the "Windows OS - Desktops" pattern:

[CMDB Whisperer]

The problem with this extension is that the resulting Model gets created without "Lenovo" as the manufacturer. You still need to have this call MakeAndModelJS so that the model can be created with the normalized manufacturer, just with a different model name.