none
MDT 2013U2 produces corrupt boot image RRS feed

  • Question

  • Hello,

    We have a customer who is a year away from upgrading their server environment and would like a Windows 10 SOE. Their main server is an SBS 2008 virtual machine.

    We created a basic deployment share based on Windows 10 / MDT 2013 U2 but WinPE simply hangs forever on the Microsoft Deployment Toolkit background screen. There is some CPU usage at the first minute but then nothing.

    Looking at the WinPE instance's BDD.log it ends with the following lines:
    ---------------------------------------------------------------------------------------
    <![LOG[Finished determining the INI file to use.]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="ZTIGather" context="" type="1" thread="" file="ZTIGather"><![LOG[Unable to find rules INI file, rc = 1]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="ZTIGather" context="" type="3" thread="" file="ZTIGather"><![LOG[ZTI ERROR - Non-zero return code by ZTIGather, rc = 8000]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="ZTIGather" context="" type="3" thread="" file="ZTIGather"><![LOG[Command completed, return code = 8000]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[FAILURE: 8000: Running wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /nolocalonly]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="2" thread="" file="LiteTouch"><![LOG[Validating connection to \\server\DeploymentShare$]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Mapping server share: \\server\DeploymentShare$]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Found Existing UNC Path Z: = \\server\DeploymentShare$]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Found Existing UNC Path Z: = \\server\DeploymentShare$]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Successfully established connection using supplied credentials.]LOG]!><time="16:33:52.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Property WizardComplete is now = Y]LOG]!><time="16:33:53.000+000" date="03-31-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property LTIDirty is now = TRUE]LOG]!><time="16:33:53.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[About to run command: MSHTA.exe "\\server\DeploymentShare$\Scripts\Wizard.hta" /definition:DeployWiz_Definition_ENU.xml]LOG]!><time="16:33:53.000+000" date="03-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    ---------------------------------------------------------------------------------------

    I noticed under System Requirements MDT supports 2008 R2 at minimum but I was wondering if that's indeed the issues and if there's any way to get this working at all?

    Thanks in advance




    • Edited by crunchabit Wednesday, April 6, 2016 1:34 AM Issue is not with SBS 2008
    Thursday, March 31, 2016 6:55 AM

Answers

  • UPDATE 2: Issue resolved!

    The problem was access permissions to the deployment share as per this thread:
    https://community.spiceworks.com/topic/1169625-mdt-wizard-not-appearing

    I added the deployment user with Allow Modify in the Security tab of the share's folder and changed the share permissions from Full Control for local administrators to Full Control for Everyone.

    Seriously, when are the MDT releases going to receive some proper QA?? There have been so many problems since the first 2013U1 release it's just ridiculous >:-(



    • Marked as answer by crunchabit Wednesday, April 27, 2016 7:24 AM
    • Edited by crunchabit Wednesday, April 27, 2016 7:25 AM
    Wednesday, April 27, 2016 7:24 AM

All replies

  • If there wasn't any testing on 2008 SBS it 'might' be the issue. I would look at the share permissions http://deploymentresearch.com/Research/Post/518/Fixing-MDT-2013-Update-1-deployment-share-permissions-using-PowerShell. If you are able to access the share ok then I would install MDT on a Windows 7 or later box and attach to the 2008 SBS share. Update from the attached machine and use that boot media.

    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, March 31, 2016 12:14 PM
    Moderator
  • Thank you

    It would be great if I could at least know what the problem is so that I can get back to the client and advise what additional work is required

    One thing I didn't mention is that Windows 7 AIK, Windows 8.1 ADK and MDT 2012 were previously installed on this server which I uninstalled. The Windows 7 AIK said a reboot is required which I didn't do. Could that be the issue?


    Also, I tested the Windows 7 deployment share which I kept and upgraded to 2013U2. It works fine using the ADK 8.1 boot image. It just looks like something is wrong with the ADK 10 WinPE boot image? I regenerated it and with no drivers but no dice

    Thanks Ty, I just reread your edited reply - I was thinking the same thing (setting up a Win7 MDT system and test), doing that now and will report back.
    • Edited by crunchabit Thursday, March 31, 2016 11:27 PM
    Thursday, March 31, 2016 10:58 PM
  • Side-by-side ADK installs are unsupported. MDT won't know what to do if multiple versions are installed. Win 10 ADK is the only correct choice with 2013u2.

    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, April 1, 2016 5:18 AM
    Moderator
  • Sorry what I meant was that the Windows 7 deployment share with AIK10 / 2013U2 works fine.

    Moving on, I created a Windows 7 MDT machine, copied the Windows 10 deployment share and modified the share's paths to point to this new system. Then I generated a new boot image from this system and imported it to WDS. First attempt went past the wizard and started deploying the install image however BSOD'ed midway, no idea why. Second attempt completed successfully %100.

    I'll just keep the MDT system for the time being as I'm not going to mess with that SBS server.

    Will continue to add drivers and test and report back.

    EDIT: Just found the reason for the BSOD, it's a VMware issue:
    https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2060019&sliceId=1&docTypeID=DT_KB_1_1&dialogID=158133794&stateId=0%200%20158145165




    • Edited by crunchabit Friday, April 1, 2016 5:52 AM
    Friday, April 1, 2016 5:41 AM
  • UPDATE:

    I have a test system based on a single 2012 R2 Standard server. This server had ADK 8.1 and MDT 2013 installed. I uninstalled those components, installed ADK 10 and MDT2013U2 and built a brand new deployment share. I get the same problem with WinPE hanging indefinitely with the grey background and Microsoft Deployment Toolkit logo.

    I am convinced there is a problem with the current breed and previous installations of previous versions. Something just sticks and causes WinPE to not work but I don't know what it is. Therefore the problem is not with SBS 2008.


    • Edited by crunchabit Saturday, April 2, 2016 12:24 PM
    Saturday, April 2, 2016 12:22 PM
  • As we have lots of customers with deployment systems based on previous versions of ADK / MDT and will all be upgraded gradually I would really love to get to the bottom of this issue.

    Can anyone help with why these upgrades produce broken and unusable WinPE images? Thanks in advance

    Monday, April 4, 2016 3:23 AM
  • It might be interesting to see if changing your deployroot to use the IP of the server instead of the name.

    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.

    Monday, April 4, 2016 6:00 PM
    Moderator
  • Thread's subject has been changed to reflect the real issue.

    If anyone can suggest what I can do to troubleshoot this further and hopefully produce some meaningful errors that would be great.

    I have already removed the components from the old server but if anyone can throw some more ideas to try I'll set this up again and test all at once.

    Wednesday, April 6, 2016 1:38 AM
  • UPDATE:

    We have another customer with this issue, however the system we installed MDT on (2008 R2) did not have a previous installation of MDT or WIK.

    Can anyone throw some ideas into what could be causing this issue? It would be really nice to know what's clashing here. Thanks in advance


    • Edited by crunchabit Wednesday, April 27, 2016 7:12 AM
    Wednesday, April 27, 2016 7:06 AM
  • UPDATE 2: Issue resolved!

    The problem was access permissions to the deployment share as per this thread:
    https://community.spiceworks.com/topic/1169625-mdt-wizard-not-appearing

    I added the deployment user with Allow Modify in the Security tab of the share's folder and changed the share permissions from Full Control for local administrators to Full Control for Everyone.

    Seriously, when are the MDT releases going to receive some proper QA?? There have been so many problems since the first 2013U1 release it's just ridiculous >:-(



    • Marked as answer by crunchabit Wednesday, April 27, 2016 7:24 AM
    • Edited by crunchabit Wednesday, April 27, 2016 7:25 AM
    Wednesday, April 27, 2016 7:24 AM
  • Thank you! Changing MDTBuild Permissions corrected my issue as well.

    Cheers-


    Scott M. Phoenix, AZ

    Tuesday, July 11, 2017 2:31 PM