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.
- XDT100-200: Driver And Traffic Safety Education Suffolk County Community College offers high school students a non-credit, state-certified Driver and Traffic Safety Education program. This program consists of 25.5 hours of classroom instruction and 25.5 hours of behind the wheel training and observation. Those who successfully complete the program will receive the MV-285 Student Certificate of.
- Driver Education Instructor Training This is a DMV approved course for the certification of instructors to teach driver education in a noncredit format. Focus is on fundamental driver education, curriculum development, and presentation skills.
- Microsoft System Center Configuration Manager (SCCM) and Microsoft Deployment Toolkit (MDT) Package Index.
How does it work
This article features our “3 Post Commercial Style Hookup” kit (SCC part number DS-0100) shown below. This driver station is designed for controllers with alligator clips. The step-by-step instructions, and accompanying photos, are designed to make assembling the driver station kit as straightforward and painless as possible.
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
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.
CONFIGMGR
- 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
Scc Drivers Education
- 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)
I recently ran into a challenge at a client that I had not dealt with before. We were working on cleanup items post-deployment of their new Windows 7 desktop when Kraft & Kennedy was asked to put together a number of updates for deployment to the new desktop. One of the requests was to update drivers on the machines with new drivers from both Dell and Toshiba. Microsoft had done a review of the desktop and concluded some updated driver versions would help with performance.
We already had a task sequence with the new version of drivers built-in using SCCM 2012 driver packages so I though this request shouldn’t not be a problem. Then I started running into challenges! First off, you’ll notice that there is no way to “deploy” a driver package in SCCM 2012 — red flag #1. To work around this, I figured I would run a task sequence and install the driver package during the course of installing other application updates we were planning to deploy. We kicked off the task sequence and it failed on the driver installation step because the machine was not running in WinPE — red flag #2! Having the task sequence reboot into WinPE to install the driver package sounded like a big mess so I turned to the internet for help.
It turns out there is not much out there on this topic but I was eventually able to find an answer that was very easy to implement. Microsoft has a kit called Windows Driver Kit 8.1 (“WDK 8.1”) designed to help plan and test installing drivers on Windows operating systems. Inside the kit is a command line utility called DPinst.exe, short for Driver Package Installer. Turns out this is a perfect utility for installing or updating drivers on the command line.
Here is what I did to create driver packages that can be deployed or installed during a task sequence:
1. Download dpinst.exe as part of the Windows Driver Kit HERE.
2. Create a source file directory with your drivers in all of their subfolders. Dell provided driver packages come in a perfect pre-existing package. (Note: drivers must be in extract INF based format, Setup.exe drivers installation programs will not work)
3. Copy dpinst.exe to the root of the folder
4. Create a DPInst.xml file with UTF-8 encoding and the text below in the root of the source folder. (UTF-8 encoding is an option in the Save As screen in Notepad)
5. Create a Package in SCCM and point to your source folder containing the drivers. (Note: this is a Package, not a Driver Package)
6. Enter the following command into SCCM as a Program: dpinst.exe /S /SA /SE /SW /F
7. Use the Program as part of a task sequence.
8. Enable Continue on Error
9. DPInst returns DWORD return codes so you won’t get 0x0 as a success. If you want you can write a VB wrapper to modify the return code.
10. Details on return codes can be found HERE.
11. Reboot the computer after the installation
Scc Drivers Education Lincoln Ne
%windir%dpinst.log is the detailed log file for the installation.
Scc Driver Education
DPInst.xml text:
Scc Drivers Ed
<?xml version=”1.0″ ?> <dpinst> <!– The following search and subDirectory elements direct DPInst to search all subdirectories (under the DPInst working directory) to locate driver packages. –> <search> <subDirectory>*</subDirectory> </search> </dpinst>