none
Inject Drivers failing MDT 2013 Media Deployment RRS feed

  • Question

  • Hello Deployment folks,

    im currently running into problems which i seemingly cannot resolve on my own anymore. Im recreating our media deployment from MDT 2010 in MDT 2013 from scratch. I've not designed the old (and messy) deployment and started learning about 2,5 months ago.

    We are running a complete rework of the wizard written from me which is working just fine. Basically at the end of the wizard (after some required inputs) the computer querys the SQL server for his configuration again and the installation starts. So far so good, but after injecting the drivers to the machine (no matter what i change or which solutions from the internet i try) the deployment fails with the following lines in smsts.log:

    Executing command line: cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"	TSManager	12.11.2015 18:09:48	1568 (0x0620)
    Process completed with exit code 13	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    !--------------------------------------------------------------------------------------------!	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Failed to run the action: Inject Drivers. 
    The data is invalid. (Error: 0000000D; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Sending status message . . .	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Set a global environment variable _SMSTSLastActionRetCode=13	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Clear local default environment	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Let the parent group (Preinstall) decides whether to continue execution	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    The execution of the group (Preinstall) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Failed to run the last action: Inject Drivers. Execution of task sequence failed.
    The data is invalid. (Error: 0000000D; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Sending status message . . .	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Task Sequence Engine failed! Code: enExecutionFail	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    ****************************************************************************	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Task sequence execution failed with error code 80004005	TSManager	12.11.2015 18:10:18	1568 (0x0620)
    Cleaning Up. Removing Authenticator	TSManager	12.11.2015 18:10:18	1568 (0x0620)

    Information:

    Even if i tell the Deployment to not inject ANY drivers at all, the deployment will still fail.

    I am using the same drivers which worked fine in MDT 2010 with the old media. I am currently not able to change them out.

    I am deploying Windows 7 Professional 64 Bit (~4500 PCs)

    What i have tried:

    Re-adding all drivers to the Deployment Share; regenerate Media.

    Comparing OS.xml with the TS.xml GUID.

    Installing OS without any driver injections.

    Swapped hardware to another test machine.

    Some more stuff i can't remember right now.

    Im very thankful for any further tips!

    Thank you

    Thursday, November 12, 2015 4:47 PM

Answers

  • Thanks to your video i started reviewing those logs again and found the error. Apparently the Environment Variable "ImageBuild" was not set in my Deployment. I found it by checking the code ZTIDrivers.wsf after

    Updating downlevel OS configuration.	ZTIDrivers	13.11.2015 08:52:46	0 (0x0000)
    

    logentry. Using a simple MsgBox in my Wizard to tell me the Environment Variable just before exiting to proccess with the installation i noticed it beeing empty. Since we are not going to change the OS for any machine i just hardcoded it in.

    Thank you, maybe this is of some help for others aswell.

    • Marked as answer by philipp.soad Friday, November 13, 2015 10:28 AM
    Friday, November 13, 2015 8:29 AM

All replies

  • Can you post the SMSTS.log and BDD.log to something like OneDrive and share the link here?

    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.

    Thursday, November 12, 2015 6:54 PM
    Moderator
  • Thanks to your video i started reviewing those logs again and found the error. Apparently the Environment Variable "ImageBuild" was not set in my Deployment. I found it by checking the code ZTIDrivers.wsf after

    Updating downlevel OS configuration.	ZTIDrivers	13.11.2015 08:52:46	0 (0x0000)
    

    logentry. Using a simple MsgBox in my Wizard to tell me the Environment Variable just before exiting to proccess with the installation i noticed it beeing empty. Since we are not going to change the OS for any machine i just hardcoded it in.

    Thank you, maybe this is of some help for others aswell.

    • Marked as answer by philipp.soad Friday, November 13, 2015 10:28 AM
    Friday, November 13, 2015 8:29 AM
  • That is so awesome.  Finally someone read my signature.  Today is a good day :)

    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.

    Friday, November 13, 2015 7:57 PM
    Moderator