Litetouch Deployment Fails after updating to MDT 2013 update 1 RRS feed

  • Question

  • I  hope someone can help me out.

    I had updated our MDT Server from 2012 to 2013 update 1 to enable for the deployment of Windows 10 in our organisation.

    Everything was working fine before the update but now every deployment fails.  If I use the task sequence I created before the update, the deployments fails, using a new task sequence the deployment fails as well.

    I get the error below:

    Using the configuration manger trace tool, i checked the SMSTS.LOG but seems to have no information on why the deployment fails.

    See logs below..

    Used smsts.ini to set logging settings. TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Command line: "C:\MININT\Tools\X64\TsmBootstrap.exe"  /env:SAContinue TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Current OS version is 6.1.7601.1 TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Running Task Sequence in standalone. TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Updating the local data path in the Task Sequencing Environment. TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Reading  logging settings from TS environment to set TS logging TSMBootstrap 31/03/2016 16:09:11 3288 (0x0CD8)
    Process completed with exit code 2147500037 TSMBootstrap 31/03/2016 16:24:58 3288 (0x0CD8)
    Exiting with return code 0x80004005 TSMBootstrap 31/03/2016 16:24:58 3288 (0x0CD8)
    Used smsts.ini to set logging settings. TsProgressUI 31/03/2016 16:24:58 3944 (0x0F68)
    ==========[ TsProgressUI started in process 3412 ]========== TsProgressUI 31/03/2016 16:24:58 3944 (0x0F68)
    Unregistering COM classes TsProgressUI 31/03/2016 16:24:58 3944 (0x0F68)
    Shutdown complete. TsProgressUI 31/03/2016 16:24:58 3944 (0x0F68)

    • Edited by MilSak Friday, April 1, 2016 6:29 AM
    Friday, April 1, 2016 6:28 AM

All replies

  • Why not jump to update 2 which fixes bugs in update 1? Also when moving to update 1 or 2 you MUST create new task sequences. See if you can get and post a link to your BDD.log

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

    Friday, April 1, 2016 4:30 PM
  • Thanks Dan for the info.

    I had done exactly what you said. Update to MDT Update 2 but my deployment seems not to working as it should.

    The OS and application gets installed with the exception of my command lines( this used to work before the updates)

    I have a script that copies some files to the local drive during deployment(xcopy.exe "%deployroot%\Files\*.*"  "c:\sysadmin" /Q /H /E /I /Y) , then down along the line in the task sequence I have a command line.

    Command Line:Install.cmd Start in: C:\sysadmin\C2R  :  This deploys office 365 on the machine ( This part

    is not working, used to work before update)

    In the logs, i get to see this. Do you have any idea what the problem might be..

    • Edited by MilSak Tuesday, April 5, 2016 11:23 AM
    Tuesday, April 5, 2016 11:17 AM
  • Since you mention O365, I'll add this link in case you need it.

    How are you installing Office? Did you import the files as an application into MDT or did you just add a command line task to the task sequence?

    Also I've found it much easier to use WSF (vbscript) because then you can make use of better logging and MDT variables. I suppose powershell is the new way to go but I'm still using vbscript.

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

    Tuesday, April 5, 2016 2:12 PM