How does Discovery know which Hardware Model to attach to? Does it / Should it / Can it use Model Number (Manufacturer Part Number)?

[bjmcdonald]

In the Discovery data it seems it just has Manufacturer and Model Name - not part number; and to be honest, most of our hardware models do not have a Model Number.   If we do populate our Hardware Models with a Model Number - do you create one with a "Generic" model number for those that are Discovered and/or loaded without a Model Number (Part Number)?   Wow, I hope that made sense.

[bjmcdonald]

thank you!  

so it's a part of the transform maps - is there a transform map for Discovery - or is that "built in" - Hope this isn't a stupid question.

Do you have any idea why Discovery would change the Model ID from a good model to "Unknown"?

[jake_mckenna]

Discovery does not use transform maps like other CMDB integrations. This is all done in a sensor script. For example, Windows discovery utilizes the return result of wmi providing the manufacturer and model name. Those values are passed into MakeAndModelJS script include and a GlideRecord Query is returning the first result found.

In your example of using the model number you would need to customize the script include to add in this benefit. This can become a big issue when you are working with a manufacturer like Lenovo who changes how they use model name vs model number.

One thing i have tried to help normalize this is update the sensor for Windows Discovery to add in the Win32_ComputerSystemProduct query to enhance the data that change out what is passed to that script include i mentioned earlier.

Sensor script = Windows - OS Information

               var man = result.Win32_ComputerSystem.Manufacturer;
               var mod = result.Win32_ComputerSystem.Model;
   //Code to add
   if(man.match(/lenovo/i) != null){
   mod = result.Win32_ComputerSystemProduct.Version; //where Lenovo keeps their model names
   }
   //end of code to add
               var mm = MakeAndModelJS.fromNames(man, mod, "hardware");

[cyked]

Hi BJ.   Is there a requirement around Asset Management that the Asset be created first?   Our purchase receipt process mandates that receipt must take place in Asset Management, that way we have an existing model and associated category in the tool.   When discovery then runs, the existing CI should be updated (matched on class and serial number).

The issue we have is how model and/or manufacturer info are reported from devices.   HP vs. hewlett packard vs. hewlett-packard vs hewlett packard inc. etc.   Field normalization will help with this, but we lack some much needed discipline around the company table.

[bjmcdonald]

We have normalization on Company as well as Model Name.   That helps us.

[cyked]

Our plan as well is to implement normalization on Company and Model. Both are inconsistent unfortunately.

Drew Paul

Configuration Management

IT Shared Services

p: 916.350.3445

Need to report a gap in CMDB?<https://www.atshieldca.com/docs/DOC-97434>