none
Upgraded to new MDT now all deployments failing. RRS feed

  • Question

  • Upgraded existing deployment server with new 2013 release 2 and current windows 10 MDK.  Now when trying to deploy any image on any hardware, 2008 or 2012, Dell or HP servers.  I get the following problem.  The deployment partitions the drive, injects drivers, then fails on OS image apply.  

    From the SMSTS.log

    Could not find CCM install folder. Don't use ccmerrors.dll TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Failed to run the action: Install Operating System. 
    Unknown error (Error: 000015EF; Source: Unknown) TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Set a global environment variable _SMSTSLastActionRetCode=5615 TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Clear local default environment TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Let the parent group (Install) decides whether to continue execution TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Could not find CCM install folder. Don't use ccmerrors.dll TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015EF; Source: Unknown) TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    **************************************************************************** TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Task sequence execution failed with error code 80004005 TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Cleaning Up. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Removing Authenticator TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Cleaning up task sequence folder TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Failed to delete directory 'C:\_SMSTaskSequence' TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    SetNamedSecurityInfo() failed. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    SetObjectOwner() failed. 0x80070005. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Deleting volume ID file V:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister TSManager 12/31/2015 5:41:40 AM 1084 (0x043C)
    ==========[ TsProgressUI started in process 1976 ]========== TsProgressUI 12/31/2015 5:41:41 AM 2032 (0x07F0)
    Unregistering COM classes TsProgressUI 12/31/2015 5:41:41 AM 2032 (0x07F0)
    Shutdown complete. TsProgressUI 12/31/2015 5:41:41 AM 2032 (0x07F0)
    Process completed with exit code 0 TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Successfully unregistered TS Progress UI. TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    End program: TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Sending error status message TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Finalizing logs to root of first available drive TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Used smsts.ini to set logging settings. TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)
    Successfully finalized logs to C:\SMSTSLog TSManager 12/31/2015 5:41:41 AM 1084 (0x043C)

    I have completely rebuilt the boot image.  Any suggestions?

    Rick Drake

    Thursday, December 31, 2015 3:30 PM

Answers

  • Had not seen that blog post.  Checked and updated deployment share and that didn't fix it. Finally did find it however. I created a new empty task list and noticed that in the format and partition drive section of this new task set there was a UEFI and a BIOS format/partition task with different settings. In the old task list there was just one format and partition and this worked for either UEFI or BIOS build in our system. Not sure why this behavior didn't carry over to the new MDT, but when I copied the UEFI and BIOS partition tasks to the old deployment tasks everything started working again.

    Rick Drake

    • Marked as answer by AinarM Monday, January 4, 2016 4:46 PM
    Monday, January 4, 2016 4:46 PM

All replies

  • Rick,

    Have you checked permissions? https://keithga.wordpress.com/2015/10/02/mdt-uberbug11-security-vs-usability/


    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, December 31, 2015 9:11 PM
    Moderator
  • Had not seen that blog post.  Checked and updated deployment share and that didn't fix it. Finally did find it however. I created a new empty task list and noticed that in the format and partition drive section of this new task set there was a UEFI and a BIOS format/partition task with different settings. In the old task list there was just one format and partition and this worked for either UEFI or BIOS build in our system. Not sure why this behavior didn't carry over to the new MDT, but when I copied the UEFI and BIOS partition tasks to the old deployment tasks everything started working again.

    Rick Drake

    • Marked as answer by AinarM Monday, January 4, 2016 4:46 PM
    Monday, January 4, 2016 4:46 PM
  • There might be other problems which you haven't noticed yet.
    The suggested approach is to recreate the Task Sequences from scratch once you updated the deployment share (in case the task sequence templates were modified) and put your changes into this new one.
    Keep that in mind if you run into anything else.
    Monday, January 4, 2016 10:48 PM