Nick Moseley has inspired me to write today’s blog with my own efforts.
When I’m testing a new machine to add to MDT I have a time saving script that outputs the missing drivers for me.
The script creates a report like this:
Computer Details: Manufacturer: Dell Inc. Model: Latitude D610 Hardware that's not working list Service Tag: HRXXXXX Description: Texas Instruments PCI-x515 CardBus Controller Device ID: PCI\VEN_104C&DEV_8036&SUBSYS_01821028&REV_00\4&2CB2952F&0&08F0 Description: Unknown Device Device ID: PCI\VEN_104C&DEV_8038&SUBSYS_01821028&REV_00\4&2CB2952F&0&0DF0 Description: Broadcom NetXtreme 57xx Gigabit Controller Device ID: PCI\VEN_14E4&DEV_1677&SUBSYS_01821028&REV_01\4&521ADAE&0&00E0 Description: Dell Wireless 1470 Dual Band WLAN Mini-PCI Card Device ID: PCI\VEN_14E4&DEV_4319&SUBSYS_00051028&REV_02\4&2CB2952F&0&18F0
This line outputs the report in a text file to the same folder that the script is run from. You can change the .\ to \\server\share\folder\
Set objLogFile = objFSO.CreateTextFile(".\" & strComputer & " missing drivers.txt", ForWriting, True)
Some guy’s commented that it returns all devices that have a non zero error code (He a hater!) and that’s right, this will show all the devices in the device manager that are not working (even disabled) so they should be remediated in your build images.
You can download your missing drivers from the Microsoft Update Catalog by just pasting the Device ID into the search engine.