none
All task sequence failing. RRS feed

  • Question

  • I had a working MDT server in windows 2008R2 with WDS installed for deployment. It was working fine. Later i had to install windows 2012r2 and copy the deployment share from the old server and install the necessary tools to get the MDT 2013 and wds working. Upgraded the deployment share and already created task Sequence were working fine(server name had changed)

    Now my problem is any new task sequence i create to deploy windows 7 its fails at step 44 (install operating system) , but if i replace the wim file from the old task sequence with the one i want and do a deployment it works. bascially any new deployment is failing at step 44.

    Error it get in the Deployment summary,

    Failure (5627):- 2146498514 0x800f082e: Run DISM.exe

    https://social.technet.microsoft.com/Forums/getfile/724847 

    Kindly advice.


    With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3


    • Edited by mike 1983 Wednesday, September 23, 2015 9:50 AM
    Wednesday, September 23, 2015 9:45 AM

Answers

  • That's better...

      Console > Deployment Image Servicing and Management tool
      Console > Version: 6.3.9600.16384
      Console > Image Version: 6.1.7601.18489
      Console > Error: 0x800f082e
      Console > DISM failed. No operation was performed. 
      Console > For more information, review the log file.
      Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log
    Return code from command = -2146498514
    FAILURE ( 5627 ): -2146498514  0x800F082E: Run DISM.exe
    Event 41002 sent: FAILURE ( 5627 ): -2146498514  0x800F082E: Run DISM.exe
    

    MDT calls DISM at several points, for various tasks, what you have here is the dism.exe /Apply-Unattend.xml step. Windows will copy the Unattend.xml file to the new disk so we can process the xml file during WIndows Setup. Additionally, we will run the "offlineServicing" phase of the Unattend.xml file.

    It's possible that your Unattend.xml file is corrupt, or perhaps your OS image isn't sysprepped properly.

    Now we need the x:\windows\logs\dism\dism.log file to find out what happened. :)


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by mike 1983 Monday, September 28, 2015 7:51 AM
    Monday, September 28, 2015 4:13 AM
    Moderator

All replies

  • Are you using MDT 2013 Update 1 build 8298?

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Friday, September 25, 2015 11:08 PM
    Moderator
  • I am not sure what you mean by MDT 2013 Update 1 build 8298

    I can see from the help of MDT that mine is  6.2.5019.0

    Please find the BDD.log ,


    With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3


    • Edited by mike 1983 Saturday, September 26, 2015 8:13 AM
    Saturday, September 26, 2015 7:34 AM
  • I can't make out the screen shot of the bdd.log above.

    IF you still need help, please copy your bdd.log file to a public site like onedrive, and share the link.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Sunday, September 27, 2015 10:53 PM
    Moderator
  • Dear Keith, 

    I have uploaded the BBd.log to onedrive

    https://onedrive.live.com/redir?resid=ECE5493EE0850766!114&authkey=!AAmAkqIioam03KQ&ithint=file%2clog

    Sorry for the trouble and thanks for helping.


    With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3

    Monday, September 28, 2015 4:03 AM
  • That's better...

      Console > Deployment Image Servicing and Management tool
      Console > Version: 6.3.9600.16384
      Console > Image Version: 6.1.7601.18489
      Console > Error: 0x800f082e
      Console > DISM failed. No operation was performed. 
      Console > For more information, review the log file.
      Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log
    Return code from command = -2146498514
    FAILURE ( 5627 ): -2146498514  0x800F082E: Run DISM.exe
    Event 41002 sent: FAILURE ( 5627 ): -2146498514  0x800F082E: Run DISM.exe
    

    MDT calls DISM at several points, for various tasks, what you have here is the dism.exe /Apply-Unattend.xml step. Windows will copy the Unattend.xml file to the new disk so we can process the xml file during WIndows Setup. Additionally, we will run the "offlineServicing" phase of the Unattend.xml file.

    It's possible that your Unattend.xml file is corrupt, or perhaps your OS image isn't sysprepped properly.

    Now we need the x:\windows\logs\dism\dism.log file to find out what happened. :)


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by mike 1983 Monday, September 28, 2015 7:51 AM
    Monday, September 28, 2015 4:13 AM
    Moderator
  • Keith how will i get the dism.log from the machine when its failed. is there a way to connect a USB and somehow transfer it from F8?

    Also i have a doubt, since this is a new server i didn't create any boot images directly from wds, instead i just copied the x64bit boot image from MDT folder to WDS.  is that a problem as all the old task sequence that was was created on the old server is working here, its just i can make any new task sequence to complete. 


    With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3

    Monday, September 28, 2015 5:13 AM
  • Hey Keith,

     i solved the issue. You pointed me in the right direction. I went through the Dism.log and found that one update was only an online update and its poped error as task sequence was doing a offline update.

    2015-09-28 21:25:39, Error                 CBS    Cannot perform offline servicing with an online-only package: Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1 [HRESULT = 0x800f082e - CBS_E_NOT_ALLOWED_OFFLINE]

    So i removed that and now its works fine.


    With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3

    Monday, September 28, 2015 7:50 AM