none
Having trouble deploying image via USB drive using MDT 2013 and Windows 7 RRS feed

  • Question

  • Hello.

    I am having difficulty deploying a custom Windows 7 x64 Enterprise image for a client. The process fails at the "Install Operating System" step. Here is there error page I get during the process:

    Here is the process I went through to create this image:

    1. Installed Windows 7 64bit Enterprise on a physical reference PC (Dell OptiPlex Desktop). Installed some company-specific apps. Installed IE9. Set some local policies. Did not run Windows Update. Captured. Later, I realized I needed to install Windows KMDF 1.11 so I started the reference machine back up, installed KMDF 1.11, and then sysprepped and re-captured.

    2. Created a Deployment Share on a non-domain-joined workstation at path of C:\DeploymentShare$. Left most things default except set it to ask for admin password.

    3. Added Windows Intune to applications list with command line "quiet" switch.

    4. Created new Operating Systems entry. Chose custom image file, important custom WIM, chose setup files are not needed, chose destination directory name "Win7Ent".

    5. Added drivers. I created two driver folders, one for "WinPE 5.0" and one for "Windows 7 x64 Ent". Imported Windows PE 5.0 driver cab from Dell into PE folder (it completed with 6 warnings, all similar to "Warning: Driver.... does not appear to support platform x86 as indicated. Overriding the indicated platform.") Imported Windows 7 Dell driver cabs for E5440, E7240, M4800 (completed with 75 warnings, same as with PE drivers). Created selected profile for WinPE5.0 and selected the PE folder, including all x86 and x64 drivers - then, went into Deployment Share properties, in Windows PE, under Drivers, set the driver selection profile to this (also set scratch space for PE to 256mb).

    6. Created task sequence: standard task sequence, chose "Do not specify product key" and "Do not specify local admin password".

    8. Updated deployment share. Completely regenerated boot images.

    9. Created and updated media.

    10. Moved contents of "Content" folder in media folder onto a flash drive. Put the drive into a Dell E5440 and attempted to run the Deploy task sequence. It seemed to start working. It passed the format and driver injection steps and then not long after I get the errors.

    I have done and redone this over and over again and scoured the web for any ideas and I can find nothing that might be breaking this process. Any ideas you all might have would be VERY appreciated. Thank you.


    • Edited by Jeremy_SRITS Wednesday, February 26, 2014 8:11 PM
    Wednesday, February 26, 2014 7:44 PM

Answers

  • Success! My problem must have somehow been rooted either MDT 2013 or the ADK. After rebuilding everything with MDT 2012 and WAIK, the deployment process worked.

    Thank you everyone for your help on this.

    • Marked as answer by Jeremy_SRITS Thursday, March 6, 2014 7:48 PM
    Thursday, March 6, 2014 7:48 PM

All replies

  • Hello.

    I am having difficulty deploying a custom Windows 7 x64 Enterprise image for a client. The process fails at the "Install Operating System" step. Here is there error page I get during the process:

    Here is the process I went through to create this image:

    1. Installed Windows 7 64bit Enterprise on a physical reference PC (Dell OptiPlex Desktop). Installed some company-specific apps. Installed IE9. Set some local policies. Did not run Windows Update. Captured. Later, I realized I needed to install Windows KMDF 1.11 so I started the reference machine back up, installed KMDF 1.11, and then sysprepped and re-captured.

    2. Created a Deployment Share on a non-domain-joined workstation at path of C:\DeploymentShare$. Left most things default except set it to ask for admin password.

    3. Added Windows Intune to applications list with command line "quiet" switch.

    4. Created new Operating Systems entry. Chose custom image file, important custom WIM, chose setup files are not needed, chose destination directory name "Win7Ent".

    5. Added drivers. I created two driver folders, one for "WinPE 5.0" and one for "Windows 7 x64 Ent". Imported Windows PE 5.0 driver cab from Dell into PE folder (it completed with 6 warnings, all similar to "Warning: Driver.... does not appear to support platform x86 as indicated. Overriding the indicated platform.") Imported Windows 7 Dell driver cabs for E5440, E7240, M4800 (completed with 75 warnings, same as with PE drivers). Created selected profile for WinPE5.0 and selected the PE folder, including all x86 and x64 drivers - then, went into Deployment Share properties, in Windows PE, under Drivers, set the driver selection profile to this (also set scratch space for PE to 256mb).

    6. Created task sequence: standard task sequence, chose "Do not specify product key" and "Do not specify local admin password".

    8. Updated deployment share. Completely regenerated boot images.

    9. Created and updated media.

    10. Moved contents of "Content" folder in media folder onto a flash drive. Put the drive into a Dell E5440 and attempted to run the Deploy task sequence. It seemed to start working. It passed the format and driver injection steps and then not long after I get the errors.

    I have done and redone this over and over again and scoured the web for any ideas and I can find nothing that might be breaking this process. Any ideas you all might have would be VERY appreciated. Thank you.


    First off you should be building you RI on a VM, not on a phyiscal computer

    5624 FAILURE: Run ImageX: <command>

    While applying the operating system image to the disk using ImageX, a non-zero return code was returned. To troubleshoot, look at the BDD.LOG to see what specific errors were returned by ImageX.

    Could be a corrupt wim file...

    If you boot into WinPE and run ImageX manually, can you apply the image? A manual imagex apply command example would look like:
    d:\tools\imagex.exe /apply C:\myimage.wim 1 c:
    D: is drive and directory where imagex is installed on your boot CD
    C:\ is the drive where your sysprepped image is located.

    If the process works, then there is a problem with your MDT configurations (paths, drivers, task sequence etc
    If the process fails, then your problem can be with your image wim file.

    Wednesday, February 26, 2014 9:48 PM
  • Massivesystem, thanks for your response. I appreciate your help on this.

    In the past, I have always built my images for MDT using a physical PC. I'm sure this is not best practice, but it hasn't given me trouble in the past. Do you suspect this may be my issue?

    Hmm, a corrupt WIM file. After I get the error message, within the deployment environment I tried pulling up a command prompt and running "imagex.exe /apply "d:\[path to WIM file]" 1 c:\" but the command gives no response. It just brings me right back to the prompt.


    • Edited by Jeremy_SRITS Wednesday, February 26, 2014 10:02 PM
    Wednesday, February 26, 2014 9:55 PM
  • Massivesystem, thanks for your response. I appreciate your help on this.

    In the past, I have always built my images for MDT using a physical PC. I'm sure this is not best practice, but it hasn't given me trouble in the past. Do you suspect this may be my issue?

    Hmm, a corrupt WIM file. After I get the error message, within the deployment environment I tried pulling up a command prompt and running "imagex.exe /apply "d:\[path to WIM file]" 1 c:\" but the command gives no response. It just brings me right back to the prompt.



    post your BDD.log
    Wednesday, February 26, 2014 10:06 PM
  • Although I don't recommend posting the *entire* bdd.log file as text in a post. Instead copy the LTIAPply.log file or post the bdd.log file to a public site like SkyDrive/OneDrive and post the link here.

    Keith Garner - keithga.wordpress.com

    Wednesday, February 26, 2014 10:36 PM
    Moderator
  • Hello again and thank you both for your help.

    Here is my LTIApply.log:

    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[OSDTargetDriveCache was determined earlier : C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[	Open Control File: OperatingSystems]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[------  Applying Windows image using ImageX.exe ------]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI applying image D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim using ImageX]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property SourcePath is now = D:\Deploy\Operating Systems\Win7Ent]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Cleaning off old operating system]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\Drivers]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\MININT]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\_SMSTaskSequence]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\MININT-4PISH0R\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\MININT-4PISH0R\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Enabling 8dot3 name support on volume C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: "D:\Deploy\Tools\X64\imagex.exe"  /apply "D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim" 1 C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 1724)]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = -1073741819]LOG]!><time="08:31:33.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5624 ): -1073741819  0xC0000005: Run ImageX:  /apply "D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim" 1 C:]LOG]!><time="08:31:33.000+000" date="02-27-2014" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    

    Thursday, February 27, 2014 2:39 PM
  • Hello again and thank you both for your help.

    Here is my LTIApply.log:

    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[OSDTargetDriveCache was determined earlier : C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[	Open Control File: OperatingSystems]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[------  Applying Windows image using ImageX.exe ------]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI applying image D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim using ImageX]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property SourcePath is now = D:\Deploy\Operating Systems\Win7Ent]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Cleaning off old operating system]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\Drivers]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\MININT]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Skipping C:\_SMSTaskSequence]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\MININT-4PISH0R\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\MININT-4PISH0R\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Enabling 8dot3 name support on volume C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: "D:\Deploy\Tools\X64\imagex.exe"  /apply "D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim" 1 C:]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 1724)]LOG]!><time="08:31:32.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = -1073741819]LOG]!><time="08:31:33.000+000" date="02-27-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5624 ): -1073741819  0xC0000005: Run ImageX:  /apply "D:\Deploy\Operating Systems\Win7Ent\Win7Ent.wim" 1 C:]LOG]!><time="08:31:33.000+000" date="02-27-2014" component="LTIApply" context="" type="3" thread="" file="LTIApply">


    I need you to upload and post a link to your BDD.log..
    Thursday, February 27, 2014 4:08 PM
  • Sorry about that - here it is:

    https://onedrive.live.com/redir?resid=6F8A9F388485333A!1766&authkey=!AIIVKdgVSXe6Rtk&ithint=file%2c.log

    Can you also throw up the smsts.log

    thanks

    Thursday, February 27, 2014 5:01 PM
  • For sure:https://onedrive.live.com/redir?resid=6F8A9F388485333A!1767&authkey=!AMS6zbOXtFYdE_0&ithint=file%2c.log

    I would say it is either  a problem with your MDT configurations (paths, drivers, task sequence etc
    or a  problem with your image wim file.

    Can you manualy apply the .wim from imagex? Have you tried it on a VM or another supported client?

    Thursday, February 27, 2014 5:59 PM
  • After I get the error message, within the deployment environment I tried pulling up a command prompt and running "imagex.exe /apply "d:\[path to WIM file]" 1 c:\" but the command gives no response. It just brings me right back to the prompt.

    I have attempted this deployment on two different models: a laptop and a desktop.

    Unless anyone has a different suggestion, I will try building my reference image on a VM.

    Thursday, February 27, 2014 6:02 PM
  • After I get the error message, within the deployment environment I tried pulling up a command prompt and running "imagex.exe /apply "d:\[path to WIM file]" 1 c:\" but the command gives no response. It just brings me right back to the prompt.

    I have attempted this deployment on two different models: a laptop and a desktop.

    Unless anyone has a different suggestion, I will try building my reference image on a VM.


    try and deploy your current image to a VM. It is obvious its a  FAILURE to Run ImageX: <command>
    Thursday, February 27, 2014 6:07 PM
  • I don't understand what you mean by "it gives no response. It just brings me right back to the prompt." Are you saying that there was not response whatsoever? that sounds weird to me. What happens when you type in "imagex.exe /?" do you get the usage window, or do you get "... not recognized as an internal or external command" error?

    You may need to specify the full command: "D:\Deploy\Tools\X64\imagex.exe" to get it to work.

    THe problem is most definitely within imagex.exe. somehow it was unable to write the contents of the *.wim file to the disk, however we can't tell from the bdd.log file, we need the output from the imagex.exe command to know for sure.


    Keith Garner - keithga.wordpress.com

    Thursday, February 27, 2014 6:17 PM
    Moderator
  • A fair question, Keith. Here is the output from my attempts:

    As you can see, I first confirm that I've got the directory right (that is, the imagex.exe utility is definitely in that folder). Then, I attempt to apply the WIM with no luck. Lastly, I try the /? switch and still get no response.

    Thursday, February 27, 2014 6:40 PM
  • A fair question, Keith. Here is the output from my attempts:

    As you can see, I first confirm that I've got the directory right (that is, the imagex.exe utility is definitely in that folder). Then, I attempt to apply the WIM with no luck. Lastly, I try the /? switch and still get no response.

    Very Strange......Bad USB Drive, files corupt on USB?


    What happens when you run imagex.exe from the computer hosting MDT? Or even run it directly from the source contents folder you copied to the USB drive. Whats it's behavior? You could also try mounting the offline media iso on a VM and see if it succesfuly deploys the image.
    Thursday, February 27, 2014 7:51 PM
  • Bingo! We now have a root cause determined. ImageX.exe shouldn't do that. :^)

    Most likely corrupt, do a CRC check against the values, or better yet uninstall the ADK, reinstall, and rebuild.


    Keith Garner - keithga.wordpress.com

    Friday, February 28, 2014 4:44 AM
    Moderator
  • I have an update:

    - I rebuilt the reference WIM. I stuck with a physical machine for the sake of convenience.

    - I started from scratch with MDT 2013 and ADK on a totally different workstation. Despite this, imagex.exe still failed to respond with any output.

    - I am back on the original workstation (the one on which I was originally building the deployment share) and I have uninstalled MDT 2013 and ADK. I have installed MDT 2012 and WAIK to see if I get any different results. I will post the results when I get them.

    Monday, March 3, 2014 8:06 PM
  • Success! My problem must have somehow been rooted either MDT 2013 or the ADK. After rebuilding everything with MDT 2012 and WAIK, the deployment process worked.

    Thank you everyone for your help on this.

    • Marked as answer by Jeremy_SRITS Thursday, March 6, 2014 7:48 PM
    Thursday, March 6, 2014 7:48 PM
  • Success! My problem must have somehow been rooted either MDT 2013 or the ADK. After rebuilding everything with MDT 2012 and WAIK, the deployment process worked.

    Thank you everyone for your help on this.


    Its great to hear that you resolved the issue by install MDT 2012 and Waik, but you should have no issue using MDT 2013 and WAIK unless there was a problem with your initial install.

    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Friday, March 7, 2014 3:53 AM
  • That's what I would think too! The reason I don't think it was something to do with my install is I tried building this image in two separate deployment shares in two separate MDT 2013 installs on two totally different machines. I experienced the exact same problem in both setups.

    I actually did not try the combination of MDT 2013 and WAIK. I only tried MDT 2013 with ADK and MDT 2012 with WAIK. Perhaps my problem lies with the ADK? It does work with Windows 7, correct?
    Friday, March 7, 2014 6:16 PM
  • That's what I would think too! The reason I don't think it was something to do with my install is I tried building this image in two separate deployment shares in two separate MDT 2013 installs on two totally different machines. I experienced the exact same problem in both setups.

    I actually did not try the combination of MDT 2013 and WAIK. I only tried MDT 2013 with ADK and MDT 2012 with WAIK. Perhaps my problem lies with the ADK? It does work with Windows 7, correct?

    ADK supports Windows 7

    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Friday, March 7, 2014 6:34 PM