none
Using MDT Version: 6.3.8443.1000 Drivers not injecting RRS feed

  • Question

  • I have been having an issue with MDT deploying drivers to the Dell Latitude E5450.  I have all of the most recent cab files loaded with the total control method.  It seems as if it does the "Set DriverGroup001" task and does nothing, it also jumps over the "Injecting Drivers" phase.  I have been plugging away at this over and over but it just fails to install all of the drivers.  


    Jason Santoro A+ Network+

    Wednesday, November 1, 2017 8:22 PM

Answers

  • Ok, so i was set to Inject all drivers and Selection profile = nothing.  Just on a whim, I tried setting the profile to my DriverGroup001 and install only matching drivers and it deployed correctly with not missing drivers.  It worked forever with the original setup (Inject all drivers selection profiles = nothing) and now it has changed not sure why.  I guess for the mean time issue is resolved.  

    Jason Santoro A+ Network+

    • Marked as answer by Jason S_Mass Thursday, November 2, 2017 1:03 PM
    Thursday, November 2, 2017 1:03 PM

All replies

  • I wish. It is not that though I think it’s the way the screen capture was or how mdt handles the font compared to notepad when I took it. There is a space between it in Win 10x64. Thanks for the response though I appreciate it.

    Jason Santoro A+ Network+

    Thursday, November 2, 2017 9:04 AM
  • Hmm... normally I would set the variable just before the Inject Driver step. Could you try that? Also, please verify that your Inject Drivers step is configured as follows: Inject all drivers, Selection Profile = Nothing. If that does not help, please post your BDD.log.

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


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, November 2, 2017 10:28 AM
  • Ok, so i was set to Inject all drivers and Selection profile = nothing.  Just on a whim, I tried setting the profile to my DriverGroup001 and install only matching drivers and it deployed correctly with not missing drivers.  It worked forever with the original setup (Inject all drivers selection profiles = nothing) and now it has changed not sure why.  I guess for the mean time issue is resolved.  

    Jason Santoro A+ Network+

    • Marked as answer by Jason S_Mass Thursday, November 2, 2017 1:03 PM
    Thursday, November 2, 2017 1:03 PM
  • I haven't tested by setting the variables in CustomSettings.ini in MDT 8456, but it works great by setting the DriverGroup001 variable in the task sequence in MDT 8456. In my Windows 10 v1903 task sequence, the Inject Drivers step has the selection profile set to Nothing, and to "Install all drivers from the selection profile".

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Sunday, October 20, 2019 9:22 PM
    Moderator
  • Not sure what I am doing wrong, but I used the ModelAlias.vbs, set my customsettings.ini as:

    [Settings]
    Priority=HardwareInfo
    Properties=MakeAlias, ModelAlias

    [HardwareInfo]
    UserExit=ModelAliasExit.vbs
    MakeAlias=#SetMakeAlias()#
    ModelAlias=#SetModelAlias()#

    [Default]
    OSInstall=Y
    _SMSTSORGNAME=%TaskSequenceID%
    SLShare=\\US19APVP130\DeploymentShare$\Logs\#month(date) & "-" & day(date) & "-" & year(date) & "__" & hour(now) & "-" & minute(now)#
    SLShareDynamicLogging=\\US19APVP130\DeploymentShare$\DynamicLogs\#month(date) & "-" & day(date) & "-" & year(date) & "__" & hour(now) & "-" & minute(now)#
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES
    SkipApplications=YES

    Then in my task sequence I set the inject drivers to nothing, and my drivergroup to DriverGroup001 Windows 10x64\%ModelAlias%. I can see logs showing the modelalias set as my friendly name, but when I run a task, no drivers are applied.

    Tuesday, March 3, 2020 7:15 PM
  • The way I got this resolved was to set the task sequence variable.  Not using [Hardware Info]  or vbs script like below.  If you are using SQL then I understand the reason to use this

    UserExit=ModelAliasExit.vbs
    MakeAlias=#SetMakeAlias()#
    ModelAlias=#SetModelAlias()#

    Background,

    I have created the folder structure in the Out-Of-Box Drivers group as seen below.  I used the wmic command to gather the same information that MDT will gather during the Gather phase.

    The wmic command is 

    wmic bios get manufacturer

    and

    wmic computersystem get model

    The folder structure must line up exactly. In my case see below

    I have created a new selection profile named DriverGroup001

    After that I created a new "Set Task Sequence Variable" and set it to DriverGroup001.

    MDT has built in variables that are gathered during the Gather task sequence and they are accessed by using %Make% and %Model% so all you need to do is point to the DriverGroup001 to OutOfBox Driver Group (in my case Win10x64)

    So the full Value is set to Win10x64\%Make%\%Model%

    Below is a screenshot of what I set.

    Once that is done you set the Inject Drivers TS to the selection profile DriverGroup001 and install only matching drivers from the selection profile.  

    After that during driver injection it will pick and choose the correct drivers based on model. 


    Jason Santoro A+ Network+


    • Edited by Jason S_Mass Tuesday, March 3, 2020 7:40 PM mistyped I put task sequence variable instead of selection profile
    Tuesday, March 3, 2020 7:38 PM