MDT Driver
The Driver Automation Tool is a GUI developed in PowerShell which provides full automation of BIOS and driver downloads, extraction, packaging and distribution with Dell, HP, Lenovo & Microsoft client hardware.
The intuitive GUI provides you with a full list of models from the supported manufacturer, allowing you to select one or many models, it also will detect Dell and Lenovo models matched against the WMI models known to ConfigMgr.
How does it work
The MDT method of driver detection and injection When we boot a target machine via our LiteTouch media, one of the initial task sequence steps will enumerate (via PnPEnum.exe ) all of the PnP IDs for every device in the machine. Things I've tried so far is updating my deployment share, restarting the MDT server, and re-downloading the driver pack. My server seems to be working properly in that I'm able to connect and apply images to our older hardware that already has the driver packs imported. You can search for a driving record if you have a current Montana Driver License MDT Mobile Provides traveler information focused on Montana; Includes road conditions and construction.
When the tool is opened, you have the option to select your manufacturer and OS of choice. When you click on the Find Models button, the tool initiates a download of XML content from the selected manufacturer, reads in the XML and displays a full list of models for selection. Clicking on the Add to Import List adds each of these models for processing and once you click on the Start Download and Import Process button the tool starts the full process to automatically download and package the content.
Custom and fallback packages
Mdt Driver
For those manufacturers who do not provide direct model XML feeds, you can also use the tool to create custom driver packages based on the same naming schema. This is important when it comes to combining the use of this tool with our Modern Driver & BIOS Management solutions (see our solutions section).
If you also wish to cater for those unknown models in your environment and provide a basic list of generic drivers to attempt a match on, there is also the ability to create a Driver Fallback Package. When used with the UseDriverFallback switch with our MDM solution, if a suitable model match is not found then a fall-back package which matches the OS being deployed is downloaded. Driver matching is then attempted within the contents of this package.
MDT Support
Although primarily designed for use with ConfigMgr, the tool also supports MDT. Here you will find the ability to select your deployment shares as well as dynamic creation of folder hierarchies based on total control naming methods
The Driver Automation Tool provides full model listings from the following manufacturers: Dell, HP, Lenovo & Microsoft.
Note: Model listings with the exception of Microsoft are provided by the manufactures in their XML feeds, so models will vary depending on the current support level for each model.
Mdt Golf Driver
CONFIGMGR
Mdt Driver Store
- Site server selection
- Automatic site code discovery
- Distribution point and distribution point group selection
- Binary differential replication
- Distribution priority
- Clean up of unused drivers
- Removal of superseded driver packages
- Removal of source download packages
- Driver & BIOS piloting
- Driver & BIOS deployment state management (production, pilot, retired)
MDT
- Auto or manual selection of the MDT PS module
- Deployment share listing
- Folder structure naming
Comprehensive documentation is contained within a PDF included in the download.
(0)
Just a quick post before February ends:
Allot has been said and written about injecting drivers with MDT into you operating system. However I thought that it should be useful to point out that any of the drivers you want to inject into your operating system, at the preïnstallation phase, occur before the actual drivers for your system are applied.
I cannot substantiate this process which (part of the) script does the trick, but I recently noticed that injecting hardware drivers for a particular machine prior to injecting printer drivers, is not going to do anything with the printer drivers. They are skipped and later on in the process not found on the Operating System “C:WindowsSystem32DriverStore”. But when I switch the tasks with each other, and printer drivers are injected before hardware specific drivers, the printers drivers are nicely injected.
The only conclusion I can draw from this, is that the mechanism which triggers “Microsoft.BDD.PnPEnum.exe” to query for the vendor and device ID’s of the hardware, does not have a complete match of hardware devices found in relationship to the pool of drivers which is offered. Until then it will accept all drivers to be injected prior to the actual hardware driver injection.
Hope this can be of any assistance
Cheers! Rens
By the way I’m receiving the key of our new house in the next couple of days and I’ll be spending my time getting our house ready for moving in. So I’m not expecting to write an article before the beginning of April.