none
Add drivers to existing image for nonexistant hardware? RRS feed

  • Question

  • What is the best way to force drivers into an image for a device that will not be attached to the computer during the MDT deployment process?

    There will be a device the users will plug in after the workstation after the workstation is delivered.  Since the device will not be connected during the deployment task sequence, the Inject Drivers task will not include these drivers.

    We need the drivers to be automatically installed from the computer's local driver store when the user later connects the device.



    • Edited by MyGposts Wednesday, September 2, 2015 9:14 PM
    Wednesday, September 2, 2015 8:40 PM

Answers

  • Johan's total control method handles this.  You would just import the driver into the your make model structure:

    http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    • Marked as answer by MyGposts Wednesday, September 2, 2015 9:11 PM
    Wednesday, September 2, 2015 8:44 PM
    Moderator
  • Doesn't that rely on plug and play hardware detection?  Even if we add the driver to the Out of Box Drivers folder, wouldn't it be seen as an unneeded driver and skipped?

    No, it doesn't rely on PnP detection, if you follow the advice to enable "Install all drivers...."

    Otherwise, you could use pnputil -a, or, dpinst. Both of these methods "add drivers to the store", without depending on PnP detection. This is the method we use to pre-stage printer drivers into our machines.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    • Marked as answer by MyGposts Wednesday, September 2, 2015 9:12 PM
    Wednesday, September 2, 2015 9:11 PM

All replies

  • Johan's total control method handles this.  You would just import the driver into the your make model structure:

    http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    • Marked as answer by MyGposts Wednesday, September 2, 2015 9:11 PM
    Wednesday, September 2, 2015 8:44 PM
    Moderator
  • Doesn't that rely on plug and play hardware detection?  Even if we add the driver to the Out of Box Drivers folder, wouldn't it be seen as an unneeded driver and skipped?
    Wednesday, September 2, 2015 8:47 PM
  • Doesn't that rely on plug and play hardware detection?  Even if we add the driver to the Out of Box Drivers folder, wouldn't it be seen as an unneeded driver and skipped?

    Read through the Total Control section.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Wednesday, September 2, 2015 9:09 PM
    Moderator
  • Doesn't that rely on plug and play hardware detection?  Even if we add the driver to the Out of Box Drivers folder, wouldn't it be seen as an unneeded driver and skipped?

    No, it doesn't rely on PnP detection, if you follow the advice to enable "Install all drivers...."

    Otherwise, you could use pnputil -a, or, dpinst. Both of these methods "add drivers to the store", without depending on PnP detection. This is the method we use to pre-stage printer drivers into our machines.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    • Marked as answer by MyGposts Wednesday, September 2, 2015 9:12 PM
    Wednesday, September 2, 2015 9:11 PM