locked
Deploy Drivers via task sequence RRS feed

  • Question

  • Currently on on V1906. Had about 50 laptops imaged, but the drivers where not included in the task sequence. 

    I am trying to deploy the drivers to a collection that includes all the new laptops via a Task sequence, but they keep failing. I have used both options: Auto Apply Drivers, and Driver Package with no success.

    Log from Driver Package Install

    Task sequence schema version is 3.10	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Current supported schema version is 3.10 and 3.00	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Starting Task Sequence Engine . . . 	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    ****************************************************************************	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable _SMSTSInstructionTableSize=1	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable SMSTSRebootRequested=	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable SMSTSRebootMessage=	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable SMSTSRebootReason=	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Set a global environment variable SMSTSRetryRequested=	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    The task execution engine started execution	TSManager	27 Jul 2020 12:04:13	3264 (0x0CC0)
    Not in SSL.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Has more instructions.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Start executing an instruction. Instruction name: Apply Driver Package. Instruction pointer: 0	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSCurrentActionName=Apply Driver Package	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a local default variable OSDRecurse	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a local default variable OSDAllowUnsignedDriver	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSLogPath=C:\Windows\CCM\Logs\SMSTSLog	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Evaluating an AND expression	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Evaluating a WMI condition expression	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Expand a string: root\cimv2	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "Latitude 3500"	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    The condition for the action (Apply Driver Package) is evaluated to be true	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Expand a string: osddriverclient.exe /install:MDD00143  /unsigned:%OSDAllowUnsignedDriver% /recurse:%OSDRecurse%	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Expand a string: 	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Start executing the command line: osddriverclient.exe /install:MDD00143  /unsigned:%OSDAllowUnsignedDriver% /recurse:%OSDRecurse%	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    !--------------------------------------------------------------------------------------------!	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Expand a string: WinPE	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    The step (Apply Driver Package) must be running in WinPE	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    !--------------------------------------------------------------------------------------------!	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Failed to run the action: Apply Driver Package. Error 0x80070032	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Not in SSL.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSLastActionRetCode=50	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSLastActionName=Apply Driver Package	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Clear local default environment	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Failed to run the action: Apply Driver Package. Execution has been aborted	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Not in SSL.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Failed to run the last action: Apply Driver Package. Result 50. Execution of task sequence failed.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Not in SSL.	TSManager	27 Jul 2020 12:04:14	3264 (0x0CC0)
    Task Sequence Engine failed! Code: enExecutionFail	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    ****************************************************************************	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Task sequence execution failed with error code 80004005	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Cleaning Up.	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Removing Authenticator	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Cleaning up task sequence folder	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    File "C:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002)	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Successfully unregistered Task Sequencing Environment COM Interface.	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister with options (0, 0)	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    ==========[ TsProgressUI started in process 11964 ]==========	TsProgressUI	27 Jul 2020 12:05:12	9060 (0x2364)
    Unregistering COM classes	TsProgressUI	27 Jul 2020 12:05:12	9060 (0x2364)
    Shutdown complete.	TsProgressUI	27 Jul 2020 12:05:12	9060 (0x2364)
    Process completed with exit code 0	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Successfully unregistered Task Sequence Progress UI.	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Start to cleanup Task Sequence policy	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    End Task Sequence policy cleanup	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    GetTsRegValue() is unsuccessful. 0x80070002.	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    End program: 	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Error executing Task Sequence Manager service. Code 0x80004005	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Sending error status message	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Not in SSL.	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    Successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs	TSManager	27 Jul 2020 12:05:12	3264 (0x0CC0)
    

    Log from Auto Apply Drivers

    ==========[ TsProgressUI started in process 3580 ]==========	TsProgressUI	27 Jul 2020 13:01:49	2716 (0x0A9C)
    Registering COM classes	TsProgressUI	27 Jul 2020 13:01:49	2716 (0x0A9C)
    sbModulePath = C:\Windows\CCM\TsProgressUI.exe	TsProgressUI	27 Jul 2020 13:01:49	2716 (0x0A9C)
    Shutdown complete.	TsProgressUI	27 Jul 2020 13:01:49	2716 (0x0A9C)
    Successfully initialized Logging for Task Sequence Manager.	TSManager	27 Jul 2020 13:01:50	9292 (0x244C)
    Commandline: C:\Windows\CCM\TSManager.exe /service	TSManager	27 Jul 2020 13:01:50	9292 (0x244C)
    Successfully registered Task Sequencing COM Interface.	TSManager	27 Jul 2020 13:01:50	9292 (0x244C)
    Running service module (tsmanager.exe) version 5.0.8853.1006 from location 'C:\Windows\CCM\TSManager.exe'	TSManager	27 Jul 2020 13:01:50	9292 (0x244C)
    Started ServiceMain	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Task Sequence Manager executing as service main thread	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    UEFI: true	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Reading logging settings from Task Sequence environment to set Task Sequence logging.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Parsing task sequence . . .	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Task sequence schema version is 3.10	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Current supported schema version is 3.10 and 3.00	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Starting Task Sequence Engine . . . 	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    ****************************************************************************	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSInstructionTableSize=1	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable SMSTSRebootRequested=	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable SMSTSRebootMessage=	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable SMSTSRebootReason=	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable SMSTSRetryRequested=	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    The task execution engine started execution	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Not in SSL.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Has more instructions.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Start executing an instruction. Instruction name: Auto Apply Drivers. Instruction pointer: 0	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSCurrentActionName=Auto Apply Drivers	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSNextInstructionPointer=0	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a local default variable OSDAutoApplyDriverBestMatch	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a local default variable OSDAutoApplyDriverCategoryList	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a local default variable OSDAllowUnsignedDriver	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSLogPath=C:\Windows\CCM\Logs\SMSTSLog	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Expand a string: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver%	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Expand a string: 	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Start executing the command line: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver%	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    !--------------------------------------------------------------------------------------------!	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Expand a string: WinPE	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    The step (Auto Apply Drivers) must be running in WinPE	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    !--------------------------------------------------------------------------------------------!	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Failed to run the action: Auto Apply Drivers. Error 0x80070032	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Not in SSL.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSLastActionRetCode=50	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSLastActionName=Auto Apply Drivers	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Clear local default environment	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Failed to run the action: Auto Apply Drivers. Execution has been aborted	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Not in SSL.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Failed to run the last action: Auto Apply Drivers. Result 50. Execution of task sequence failed.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Not in SSL.	TSManager	27 Jul 2020 13:01:50	10064 (0x2750)
    Task Sequence Engine failed! Code: enExecutionFail	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    ****************************************************************************	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Task sequence execution failed with error code 80004005	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Cleaning Up.	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Removing Authenticator	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Cleaning up task sequence folder	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    File "C:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002)	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Successfully unregistered Task Sequencing Environment COM Interface.	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister with options (0, 0)	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    ==========[ TsProgressUI started in process 11804 ]==========	TsProgressUI	27 Jul 2020 13:01:52	11444 (0x2CB4)
    Unregistering COM classes	TsProgressUI	27 Jul 2020 13:01:52	11444 (0x2CB4)
    Shutdown complete.	TsProgressUI	27 Jul 2020 13:01:52	11444 (0x2CB4)
    Process completed with exit code 0	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Successfully unregistered Task Sequence Progress UI.	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Start to cleanup Task Sequence policy	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    End Task Sequence policy cleanup	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    GetTsRegValue() is unsuccessful. 0x80070002.	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    End program: 	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Error executing Task Sequence Manager service. Code 0x80004005	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Sending error status message	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Not in SSL.	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    Successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs	TSManager	27 Jul 2020 13:01:52	10064 (0x2750)
    

    Monday, July 27, 2020 1:58 PM

Answers

  • Hi You cannot deploy drivers separately using a task sequence without OS, on other words, you cannot use those 2 steps on a OS. You can actually create a regular SCCM package and use pnputil to deploy to those 50 device The step (Apply Driver Package) must be running in WinPE TSManager 27 Jul 2020 12:04:14 3264 (0x0CC0) !--------------------------------------------------------------------------------------------! TSManager 27 Jul 2020 12:04:14 3264 (0x0CC0) Failed to run the action: Apply Driver Package. Error 0x80070032

    Aravinth Mathan

    • Marked as answer by Nav_n Wednesday, August 5, 2020 8:23 PM
    Monday, July 27, 2020 5:53 PM
  • Hi Nav_n,

    Thanks for posting in TechNet.

    1. This task sequence step apply driver package or auto apply drivers runs only in Windows PE. It doesn't run in the full OS. So it is recommended that we could use driver package to deploy to the client.
    Here is a helpful guide to create the driver package using SCCM:
    https://www.reddit.com/r/SCCM/comments/85hzmk/how_to_implement_drivers_in_sccm_the_easy_way/

    2. If we want to know the steps about apply driver package and auto apply drivers, please refer to the following article:
    https://docs.microsoft.com/en-us/mem/configmgr/osd/understand/task-sequence-steps#BKMK_ApplyDriverPackage

    I hope this could help you. Thanks for your time.

    Best regards,
    Fiona Yan


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Nav_n Wednesday, August 5, 2020 8:23 PM
    Tuesday, July 28, 2020 6:33 AM

All replies

  • Hi You cannot deploy drivers separately using a task sequence without OS, on other words, you cannot use those 2 steps on a OS. You can actually create a regular SCCM package and use pnputil to deploy to those 50 device The step (Apply Driver Package) must be running in WinPE TSManager 27 Jul 2020 12:04:14 3264 (0x0CC0) !--------------------------------------------------------------------------------------------! TSManager 27 Jul 2020 12:04:14 3264 (0x0CC0) Failed to run the action: Apply Driver Package. Error 0x80070032

    Aravinth Mathan

    • Marked as answer by Nav_n Wednesday, August 5, 2020 8:23 PM
    Monday, July 27, 2020 5:53 PM
  • Hi Nav_n,

    Thanks for posting in TechNet.

    1. This task sequence step apply driver package or auto apply drivers runs only in Windows PE. It doesn't run in the full OS. So it is recommended that we could use driver package to deploy to the client.
    Here is a helpful guide to create the driver package using SCCM:
    https://www.reddit.com/r/SCCM/comments/85hzmk/how_to_implement_drivers_in_sccm_the_easy_way/

    2. If we want to know the steps about apply driver package and auto apply drivers, please refer to the following article:
    https://docs.microsoft.com/en-us/mem/configmgr/osd/understand/task-sequence-steps#BKMK_ApplyDriverPackage

    I hope this could help you. Thanks for your time.

    Best regards,
    Fiona Yan


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Nav_n Wednesday, August 5, 2020 8:23 PM
    Tuesday, July 28, 2020 6:33 AM
  • Hi  Nav_n,

    Hope everything goes well.

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Best regards,
    Fiona Yan


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    • Edited by fionay Thursday, July 30, 2020 2:21 AM
    Thursday, July 30, 2020 2:19 AM
  • Hi,

    Just checking in to see if there is any update. We haven't heard from you for a few days and would like to know the current status of the problem. Is the problem solved? Do you need any further assistance? Look forward to hearing from you.

    Best regards,
    Fiona Yan


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 5, 2020 6:10 AM
  • Hi, I eventually just added the drivers to the Task Sequence and re-ran the TS. 
    • Proposed as answer by fionay Thursday, August 6, 2020 7:18 AM
    Wednesday, August 5, 2020 8:22 PM
  • Hi Nav_n,

    Thanks for your feedback and I'm glad the problem is solved now.
    If you have any questions in future, we warmly welcome you to post in this forum again.

    Best regards,
    Fiona Yan


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 6, 2020 1:59 AM