none
MDT not injecting all drivers RRS feed

  • Question

  • MDT2013.. litetouch deployment.. been using the exact procedure for years with no issues..  uploaded new Windows 10 Image and all drivers for Surface Book..  the system will image (not using WDS for surfaces) and 3 drivers wont install.  The BDD log states no 3rd party drivers found for those devices (I matched the Hardware ID from device mgr to confirm its the actually device(s) having the issue).  I triple checked and made sure the driver(s) are there and enabled.  After imaging, I go into device manager and manually point to the driver and it installs properly.  It is skipping 2 HD sound drivers and 1 unknown.  We dont use Windows Update or WSUS during deployment yet.. however, when I manually point to the driver or do a full windows update, everything installs.  I removed all drivers, and readded and updated ISO.. still wont install them.. any ideas as to whats going on? 
    Wednesday, March 16, 2016 7:52 PM

Answers

All replies

  • So this is a chicken and the egg issue.  MDT doesn't have any way of knowing what child devices something might have when it does its PNP detection.  There are a couple of different ways you can handle this.  I will list them in order of preference.  You can use the Total Control (method 3 in Johan's blog) , choose to install the drivers as applications based on make model, or you can try adding the parent driver to WinPE.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Wednesday, March 16, 2016 9:44 PM
    Moderator
  • I had a similar issue with the Surface Pro 4. What I ended up doing was downing the Firmware update MSI and I ran this as an application in MDT. This took care of any missing drivers and updated the Firmware on the device. Here is the link for the Firmware: https://www.microsoft.com/en-us/download/details.aspx?id=49497. Hope this helps. 

    • Marked as answer by rodgerkrau Thursday, March 17, 2016 6:14 PM
    Thursday, March 17, 2016 1:45 AM
  • Microsoft has some guidance on managing surface drivers and firmware - https://technet.microsoft.com/en-us/library/mt210838.aspx

    Also I wholeheartedly agree on following the Total control method for drivers.


    If this post is helpful please vote it as Helpful or click Mark for answer.


    • Edited by Dan_Vega Thursday, March 17, 2016 3:19 PM
    Thursday, March 17, 2016 3:18 PM
  • I went this route and it worked.  thanks!
    Thursday, March 17, 2016 6:14 PM