Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Following the release of Driver Manager 1.0 we had lots of feedback from customers and partners asking if we could provide the functionality we have for SCCM 2007 for MDT2010. So for Driver Manager 2.0 (scheduled for release in July) we have added the ability to integrate with MDT 2010 and provision drivers into the MDT deployment system.


The process to import hardware, find and download drivers is the same whether you’re using SCCM or MDT. Once you have the drivers you need and they have been analysed by Driver Manager you can then integrate the drivers into the MDT environment. Driver Manager will determine whether drivers are INF type drivers (good drivers) or application packages (bad drivers) and add them to MDT as either Out-of-box Drivers or Application packages.


Driver Manager will complete the following steps during the integration process:

  1. Create a folder structure beneath Out-of-box Drivers based on the Windows OS/platform, machine make and model e.g. Windows 7 (x86)\Dell Inc.\Optiplex 790
  2. Import INF type drivers into the folder created in #1
  3. Create a folder structure beneath Applications based on the Windows OS/platform, machine make and model e.g. Windows 7 (x86)\Dell Inc.\Optiplex 790
  4. Create an Application package and place it into the folder created in #3
  5. Update the MDT database with a Make and Model entry for the machine and assign the application package to the entry (optional)


MDT Task Sequence Configuration:

INF drivers are delivered using the Inject Drivers task sequence step, by default this will scan all drivers in the store and attempt to select the best option. In order to filter the drivers so that only the drivers for a specific make and model are available set a Task Sequence Variable named DriverGroup001 to the folder created by Driver Manager, e.g Windows 7 (x86)\%Make%\%Model% Then edit the Inject Drivers task sequence step and ensure that Choose selection profile is set to nothing

Drivers that are wrapped up in application packages will be created under a single MDT Application package that can be installed during your task sequence. The application includes DriverInstaller (a component of Driver Manager) which is used to determine whether a given application package is actually applicable for the machine being deployed. DriverInstaller will process each application package and silently install the required packages. The Application that Driver Manager creates can automatically be assigned to the Make and Model entry in the MDT database and therefore by dynamically installed by MDT using the Install Applications task sequence step.

Using this method will you can dynamically deliver only the INF drivers and application packages required for a specific machine type during your MDT deployment task sequence.