Forcing a device driver to install in the driver store

by Mitch Tulloch [Published on 23 Oct. 2012 / Last Updated on 23 Oct. 2012]

A tip on how you can force a driver for a particular device to be installed by MDT during the deployment process even if the device is not connected to the system during the installation.

Let's say your using MDT to deploy Windows to a system that users will use smartcards with.  You've downloaded the driver for your smartcard reader from the Windows Catalog website, and you've imported the driver into your deployment share. You want to force the smartcard driver to be installed during the deployment process, but the smartcard reader won't actually be connected when that happens.  How can you force the smartcard driver to install into the driver store of the system during the deployment process?

To make this happen, configure the Inject Drivers step of your task sequence so that all drivers will be injected and not just matching ones.

Mitch Tulloch is a eight-time recipient of the Microsoft Most Valuable Professional (MVP) award and widely recognized expert on Windows administration, deployment and virtualization. For more tips by Mitch you can follow him on Twitter or friend him on Facebook.

The Author — Mitch Tulloch

Mitch Tulloch is a widely recognized expert on Windows administration, networking, and security. He has been repeatedly awarded Most Valuable Professional (MVP) status by Microsoft for his outstanding contributions in supporting users who deploy and use Microsoft platforms, products and solutions. Mitch has published over two hundred articles on different IT websites and magazines, and he has written or contributed to almost two dozen books and is lead author for the Windows 7 Resource Kit from Microsoft Press. For more information, see .

Latest Contributions

Featured Links