VEN and DEV IDs stand for Vendor ID and Device ID – these are the unique codes identifying a hardware device including the device model, type, and the hardware device manufacturer. These IDs are available for most hardware devices and components.

Hi, I know we're using Software Inventory to do this. Basically you collect the info on all *.sys files (typically under C: WINDOWS system32 drivers). To my knowledge this is reliable, although you'll have an accidental weird version. To be on the safe side, I did a comparison for a Hp Server and the information for e.g. The array controller was consistent between Device Manager, Hp Version Control Agent and SCCM.

It all matched the header of the actual driver file HpCISSs2.sys. Cheers, Serge. Hardware inventory would work if this infornation is written to the Registry or WMI. We can query those fairly easily (see our default Configuration.mof and sms_def.mof files for examples on what we gather by default). If you were to add a rule to software inventory for the driver file (or extension) then we'd inventory the file infornation for the driver file. However, that may not give you the exact version you are after, we software inventory reports what is in the resource header for the file, which may be a more detailed, or even different version, than is published in the.inf file or displayed to the user. Those would be the two thoughts I'd have.

Thanks Wally, After posting I did actually find the information in the registry - however it's not in the same key everytime. I can't confirm, but I do think they are all under: HKLM SYSTEM CurrentControlSet Control Class {4D36E97B-11CE-BFC1-08002BE10318 Under that I found what I wanted under 0001 on one server and 0003 on another. So I guess I would need a way to either query all the keys under the main key or figure out a way to just query the key I care about which could be any of a number of keys. Hi, I know we're using Software Inventory to do this. Basically you collect the info on all *.sys files (typically under C: WINDOWS system32 drivers). To my knowledge this is reliable, although you'll have an accidental weird version. To be on the safe side, I did a comparison for a Hp Server and the information for e.g.

Lagu islami kau lah ibuku cinta kasihku. Nonton atau download video film pendek mengharukan perjuangan ibu kaulah ibuku cinta kasihku cover malik irama durasi panjang/pendek penuh, format MP4 atau 3GP. Lagu247.com Download Lagu Gratis.

The array controller was consistent between Device Manager, Hp Version Control Agent and SCCM. It all matched the header of the actual driver file HpCISSs2.sys. Cheers, Serge.

Dell resource DCs usually cover many different laptops or PCs. Not just one CD per device. Dell really has their drivers and resource CDs down to a science. It does not surprise me that this one CD works on differing hardware. When you install a driver for a particular peice of hardware it usually rips out or disables the old driver. Free workshop manual for peugeot 106 tuning. So, after a reboot you are running the new driver.

No worries about the long text. Your reply was not that long and sometimes it takes a lot of details to get things settled. Lots of little details in this profession and the devils in them all. Issue is resolved.After searching the web finally came across the fix. - I had to 1st delete the Keyboard and Mouse 'UpperFilters' multistring values for both devices in the registry under HKEY LOCAL MACHINE>SYSTEM>CurrentControlSet>Control>Class. And rebooted.

-Then I copied the Classguid value from the Details tab for each device in Device Manager -Completed a Find for both reg entries with the Classguid string and created a new Multi String value entry for both devices matching the description below. -Keyboard: Name: Upperfilters:: Type: kbdclass -Mouse: Name: Upperfilters: Type: mouclass -rebooted again and Device Manager was clean and both keyboard and touchpad are working correctly now. Thanks for the responses. Robby Hotsauce wrote: Download the CAB file from here: Extract it then update/install drivers for the hardware you listed. When prompted, point it to the folder where you extracted the CAB.

It will find the correct driver for you and once install, let you now what it is.Maybe I'm missing something, but I don't see a CAB there. I usually get mine from here: en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deployment (just linking in case someone else needs it in the future). I can't believe I didn't think to just point device manager there. That worked great.