Automate Device Driver Integration for disk images and RIS
It may have been covered before but I just found a rather usefull looking article about integrating device drivers into Windows images. It gives a fairly usefull looking rundown on how the whole driver searching and installation thing works and also includes some truely usefull looking scripts.
Win32_PnpEntity_Plus.vbs can be used to retrieve device information from the Win32_PnpEntity WMI class and from the registry for devices installed on a system. This script produces output formatted either as an .ini or a .csv file. The output can be filtered to include or exclude devices by device class or driver provider. You can also use the script for discovering which devices require third-party drivers. For example, suppose support for a new computer model needs to be added to the image. Start the computer with the vendorís installation of Windows.
The folder structure of Plug and Play drivers used in an operating system image can be quite large and complex. Documenting what drivers are included in these folders, along with the driver vendor, the driver version, and the devices each driver supports can be a tedious and error-prone process. I developed DriverInfInfo.vbs to retrieve provider and version info, Plug and Play IDs, and device descriptions for all device driver .inf files in a folder structure.
PNPDriverMatch.vbs enumerates the device IDs on the computer, examines the folder of Plug and Play drivers to find .inf files that have matching IDs found on the computer, and optionally copies the matching driver folders to a specified destination folder.
You can use this script to document matching drivers for a computer model, as well as to copy only matching drivers to the Plug and Play drivers folder.
This script examines a folder structure of Plug and Play drivers. It can be used to create the OemPnPDriversPath entry needed for an answer file or to directly populate the DevicePath entry in the registry.