Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
After MDT 2012 update 1 upgrade..

Unanswered After MDT 2012 update 1 upgrade..

  • Thursday, September 06, 2012 9:40 PM
     
     
    Sign In to Vote
    0

    ...from mdt 2012.  

    Highlights from the SMSTS log:

    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 9/6/2012 12:59:13 PM 1304 (0x0518)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015F0; Source: Unknown) TSManager 9/6/2012 12:59:13 PM 1304 (0x0518)

    Task Sequence Engine failed! Code: enExecutionFail TSManager 9/6/2012 12:59:13 PM 1304 (0x0518)

    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    Also.. FAILURE 5616 : Verify BCDBootEx


    • Edited by RickS2 Friday, September 07, 2012 12:08 AM
    •  
     

All Replies

  • Friday, September 07, 2012 6:07 AM
     
     
    Sign In to Vote
    0

    Recreate the Task Sequence and try running it again.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Friday, September 07, 2012 1:30 PM
     
     
    Sign In to Vote
    0
    Thanks for the reply but the result is the same. BDD log shows no errors.
     
  • Monday, September 10, 2012 7:17 AM
     
     
    Sign In to Vote
    0

    After installing Sp1, if you right click on the Deployment Share - there is an option to upgrade it. Did you do that?

    Are all task sequences failing? In this specific one, are you trying to install Windows 7 to a bare metal machine?

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Friday, October 12, 2012 3:42 AM
     
     
    Sign In to Vote
    0

    Hello Sirs,

         I meet the same problem after SP1 installed.  Before installed, it works properly.

    • Proposed As Answer by BattMatt Monday, November 05, 2012 6:20 PM
    • Unproposed As Answer by BattMatt Monday, November 05, 2012 6:20 PM
    •  
     
  • Monday, November 05, 2012 6:26 PM
     
     
    Sign In to Vote
    0
    Are there spaces in the path for the deployment share(s)?  I recently upgraded and found that I had to recreate deployment shares to exclude spaces in their folder names (e.g., delete "Deployment Share" and create "DeploymentShare" in its place) to solve this problem.
    • Edited by BattMatt Monday, November 05, 2012 6:53 PM
    •  
     
  • Tuesday, November 06, 2012 12:02 AM
     
     
    Sign In to Vote
    0
    BattMatt is correct... this is a bug with the RunWithConsoleLoggingAndHidden function in ZTIUtility.vbs. In this situation where MDT is failing, it is passing the path of BCDBoot.exe (in the Tools folder of your Deployment Share) to ztiRunCommandHidden.wsf however if you have spaces in the path of your deployment share the arguments aren't passed correctly (you can confirm this by modifying ztiRunCommandHidden.wsf to display a msgbox containing wscript.arguments.UnNamed(0) and you will find that it only contains a portion of the string). You could quite easily modify ztiRunCommandHidden.wsf to piece all of the arguments passed back into a single string.