Discovery storage device classification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2017 08:17 AM
Istanbul
I'm new to the discovery world....
Discovery defaults most of the found hard disks to (Standard disk drives) and doesn't set the device interface .
It create new product models because it is not matching the serial number or device id of the hard disk to what is in system.
I've corrected the data, set up field normalization and the next day it wipes it out.
From the Windows - Storage 2008 Multi probe input payload
<Win32_DiskDrive>
<Manufacturer>(Standard disk drives)</Manufacturer>
<Status>OK</Status>
<InterfaceType>IDE</InterfaceType>
<SCSITargetId>2</SCSITargetId>
<Index>1</Index>
<SCSILogicalUnit>0</SCSILogicalUnit>
<SCSIBus>0</SCSIBus>
<SCSIPort>0</SCSIPort>
<Size>159998146560</Size>
<SerialNumber>W -DCWTA32826578</SerialNumber>
<DeviceID>\\.\PHYSICALDRIVE1</DeviceID>
<Caption>WDC WD1600AAJS-75B4A0</Caption>
field normalization to set WDC WD1600AAJS-75B4A0 to WDC WD1600AAJS and coalesce it to Western Digital WDC WD1600AAJS
Question:
Where is it getting this manufacturer from (Standard disk drives) even after I have removed it from the system.
Is there a way discovery "look up" the product model of the hard drive and set the correct manufacturer so it doesn't creates all the records.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2017 01:19 PM
Hi Marc,
This is actually what WMI is reporting for the device. If you go onto the computer itself and look in device manager, you will probably see something similar to the following...
So both the manufacturer and the model tend to be in both the model and caption WMI fields but I don't think even these are consistently populated so you can't easily split these up to get manufacturer etc. Most other devices are the same and in the example above, I could only find Manufacturer correctly populated on the Network adapters and Processors. I don't know the reason why Windows does this.
Regards,
Dave