locked
Surface Pro Driver injection no longer working under MDT 2013 RRS feed

  • Question

  • Since upgrading to MDT 2013 we are experiencing an issue with deploying Windows 8.1 to our Surface Pros. The deployment seems to be ignoring driver group settings in CS.ini and it basically injects no drivers. We are following the guide Microsoft posed here:

    http://www.microsoft.com/en-us/download/details.aspx?id=38826

    So I'm confused as to where we are going wrong. Here is the section in question from CS.ini:

    [ByModel]
    Subsection=Model-%Model%
    
    [Model-Surface with Windows 8 Pro]
    OSDComputerName=TAB%SerialNumber%
    DriverGroup001="Windows 8.1 x64\Microsoft\Surface Pro"
    DriverSelectionProfile=Nothing
    XResolution=1920
    YResolution=1080

    Incidentally the computer name is getting set so i know this block is working. Any idea why the drivers would get skipped over?

    Tuesday, November 12, 2013 7:02 PM

All replies

  • Zeus,

    IMO, your better off controlling the Driver Injection using the Task Sequence.  Unless your dealing with dozens of models, it makes for a cleaner admin experience using the Workbench GUI.  It also easily carries over to Media Deployment Shares and Linked Deployment Shares.


    -BrianG (http://supportishere.com)

    • Proposed as answer by Keith GarnerMVP Thursday, November 14, 2013 5:04 AM
    Wednesday, November 13, 2013 8:36 AM
  • Zeus,

    IMO, your better off controlling the Driver Injection using the Task Sequence.  Unless your dealing with dozens of models, it makes for a cleaner admin experience using the Workbench GUI.  It also easily carries over to Media Deployment Shares and Linked Deployment Shares.


    -BrianG (http://supportishere.com)

    Well what makes this so frustrating is the fact that it is the method outlined by Microsoft in their deployment guide. Highly irritating that it seems to have just abruptly stopped working. Can you elaborate on your process?
    Wednesday, November 13, 2013 3:57 PM
  • We are also experiencing the same issue. Very frustrating since I have large deployment to do.

    Injecting the driver with the Task Sequence, because the whole point of this deployment is to inject all drivers (not only detected) from only a certain driver package. You don't want to inject all drivers from all packges (folders).


    Boudewijn Plomp, BPMi Infrastructure & Security | Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer".

    Monday, July 14, 2014 1:54 PM
  • I've been deploying to Surface tablets just fine and deployed to a Surface 3 just a couple days ago without any issues, but I do follow Johan's "Total control" way of managing drivers. http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx

    I'd recommend you go that way as well as you'll most likely have fewer issues. Depending on your situation you may also want to make use of the "ModelAliasExit" script and use Make variables or you can just follow the method above exactly as is.


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

    Friday, August 15, 2014 5:18 PM
  • If you are having problems with the Total Control method, it would be better have a concrete example of what is going on here.

    Can you copy the following files to a public site like OneDrive and copy the link here: bdd.log, drivers.xml, drivergroups.xml, and SelectionProfiles.xml. That should be enough to trace back your problem.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, August 15, 2014 6:49 PM