MDT + WDS Deployment " Operating System deployment did not complete successfully"
- Hi,
We are deploying Windows Longhorn server in LAB environment using MDT 2010 & WDS. Deployment server "WIN-W3VM9" is a Windows server 2008. Server having single partition as C contain Deployment Workbench share \\WIN-W3VM9\Deployment$ as well WDS share \\WIN-W3VM9\REMINST .
-We have manually configured reference computer with Server 2008 & captured it using WDS
-Above image imported into MDT using add OS image wizard….
- Configured task sequence.
- As we had already configured LiteTouchPE_x86.iso , booted another system using LiteTouchPE_x86 DVD…
- Selected respective task sequence and completed further steps in wizard…
- OS installation process began …and sometime later it shows ERROR…
Operating System deployment did not complete successfully..
Error- Unable to find SETUP , needed to install the image \\ WIN-W3VM9.contoso.com\REMINST\Images\Windows_Server_2008\Longhorn.WIM
ZTI ERROR – Non Zero return code by LTI Apply , rc=1
What I missed / anything has wrong…. ??
Any help would much appreciated …
Answers
Yes, someone do :)
First, you need to add the setup files because MDT 2010 Lite Touch is always running setup.exe when deploying an image, even if it's stored in WDS.So you need to import the Operating System Files to the Deployment Workbench anyway.
If you are adding Windows Server 2008 R2, you need to update the LTIApply.wsf script, becasue when it tries to verify the Install Path it actually breaks it, adding a "\\" where it should only be a "\". So the Path will be like \\Server\REMINST\\Images..., instead of \\Server\REMINST\Images.. This is not necessary for Windows Server 2008, only the R2 version.
Commenting out line 438 - 445 in LTIApply.wsf will fix it for Windows Server 2008 R2.
Shorthand story...Adding your images to an Image Group on the WDS server is a bad idea (IMNSHO), it just adds additional (and un-needed) complexity. I recommend to store them directly in the MDT Deployment Share.
/ Johan
- Marked As Answer byTim Quan - MSFTMSFT, ModeratorFriday, November 06, 2009 2:14 AM
- Unmarked As Answer bysamtiger Friday, November 06, 2009 11:15 AM
- Proposed As Answer byJonathan440 Wednesday, November 04, 2009 2:28 PM
- Marked As Answer bysamtiger Saturday, November 07, 2009 11:03 AM
- Edited byJohan ArwidmarkMVPWednesday, November 04, 2009 10:42 PM
- Edited byJohan ArwidmarkMVPWednesday, November 04, 2009 10:43 PM
- Unproposed As Answer bysamtiger Friday, November 06, 2009 11:34 AM
I will do my best :)
In the MDT Quickstart Guide they first import a full source os (The entire DVD), creates a task sequence, deploy it and capture the setup to a new image (custom image)
Later they add that custom image (as a custom image) into the workbench, creates a new task sequence, and then deploy the captured image (the custom image).
The reason the deployment of the custom image works is because you already imported the setup files when importing the full source os, and MDT is smart enough to look at all imported operating systems in the deployment share, searching for the setup files.
In the case where you create a deployment share, don't import a full source os, and only add a custom image (either a wim-file directly, or from the WDS), the deployment will fail because MDT cannot locate the setup files in the deployment share. And MDT always run setup.exe, even when deploying a custom image.
If you want to know how to get your MDT 2010 deployment solution done, sign up for my free CD (online download) with step-by-step guides & videos that I have published to the management and deployment community. They are more detailed than the default MDT quickstart guide, and I have recorded every single step you need to do in order to build a MDT 2010 Lite Touch solution.
The CD, which is free to download contains the following guides and videos.
MDT 2010 Lite Touch Deployments (deployment without ConfigMgr 2007 SP2 R2, just the free tools)
- LTI01 - Installing the server for MDT 2010 Lite Touch
- LTI02 - Creating a Windows 7 reference image using Lite Touch
- LTI03 - Deploying a Windows 7 image using Lite Touch
- LTI04 - Dynamic Settings, creating and using the deployment databaseMDT 2010 Zero Touch Deployments (deployment with ConfigMgr 2007 SP2 R2)
- ZTI01 - Installing the server for MDT 2010 Zero Touch and ConfigMgr 2007 SP2
- ZTI02 - Creating a Windows 7 reference image using ConfigMgr 2007 SP2
- ZTI03 - Deploying a Windows 7 image using ConfigMgr 2007 SP2
- ZTI04 - Dynamic Settings, creating and using the deployment databaseAdditional Presentations
- E01 - New features in MDT 2010
- E02 - Upgrading MDT 2008 to MDT 2010
- E03 - Migrating Windows XP to Windows 7
Sign up at www.deploymentcd.com
/ Johan- Marked As Answer bysamtiger Saturday, November 07, 2009 10:43 AM
All Replies
Some tips for you...
Even though you techincally can, do not store the operating system images in WDS, store them in the MDT Deployment Share instead. If it were up to me Microsoft should have removed the Operating System image option all together fronm WDS and just use it for PXE and Multicast...
Then only use WDS for PXE-booting the LiteTouch_x86.wim file (which after booting, will connect to the MDT Deployment share)
As for your question, when adding a custom image, you must specify a folder where you have the setup files (Lite Touch always runs setup.exe). If you already imported a full DVD it will find the setup.exe from that operating system, but as a general rule, always select to add the setup files when importing a custom image, then you know Lite Touch will find them.- Hi Johan,
Thanks for the reply...!! One thing I don't understood..Why there is option to import Operating Wizard as " Windows Deployment Services Image" or is this bugs in MDT....?? since it shows images successfully imported from WDS in last page of wizard..
Thanks.
Nobody has a answer….?Yes, someone do :)
First, you need to add the setup files because MDT 2010 Lite Touch is always running setup.exe when deploying an image, even if it's stored in WDS.So you need to import the Operating System Files to the Deployment Workbench anyway.
If you are adding Windows Server 2008 R2, you need to update the LTIApply.wsf script, becasue when it tries to verify the Install Path it actually breaks it, adding a "\\" where it should only be a "\". So the Path will be like \\Server\REMINST\\Images..., instead of \\Server\REMINST\Images.. This is not necessary for Windows Server 2008, only the R2 version.
Commenting out line 438 - 445 in LTIApply.wsf will fix it for Windows Server 2008 R2.
Shorthand story...Adding your images to an Image Group on the WDS server is a bad idea (IMNSHO), it just adds additional (and un-needed) complexity. I recommend to store them directly in the MDT Deployment Share.
/ Johan
- Marked As Answer byTim Quan - MSFTMSFT, ModeratorFriday, November 06, 2009 2:14 AM
- Unmarked As Answer bysamtiger Friday, November 06, 2009 11:15 AM
- Proposed As Answer byJonathan440 Wednesday, November 04, 2009 2:28 PM
- Marked As Answer bysamtiger Saturday, November 07, 2009 11:03 AM
- Edited byJohan ArwidmarkMVPWednesday, November 04, 2009 10:42 PM
- Edited byJohan ArwidmarkMVPWednesday, November 04, 2009 10:43 PM
- Unproposed As Answer bysamtiger Friday, November 06, 2009 11:34 AM
- I had the same problem, and what is tough to figure out is how WDS and MDT 2010 work together. The bottom line is found out by myself other than PXE booting lite touch, the WDS server doesn't really do anything else besides multicast your deployments if enabled.
I completely second Johan's response.- Marked As Answer byTim Quan - MSFTMSFT, ModeratorFriday, November 06, 2009 2:14 AM
- Unmarked As Answer bysamtiger Friday, November 06, 2009 11:23 AM
Yes, someone do :)
First, you need to add the setup files because MDT 2010 Lite Touch is always running setup.exe when deploying an image, even if it's stored in WDS.So you need to import the Operating System Files to the Deployment Workbench anyway.
If you are adding Windows Server 2008 R2, you need to update the LTIApply.wsf script, becasue when it tries to verify the Install Path it actually breaks it, adding a "\\" where it should only be a "\". So the Path will be like \\Server\REMINST\\Images..., instead of \\Server\REMINST\Images.. This is not necessary for Windows Server 2008, only the R2 version.
Commenting out line 438 - 445 in LTIApply.wsf will fix it for Windows Server 2008 R2.
Shorthand story...Adding your images to an Image Group on the WDS server is a bad idea (IMNSHO), it just adds additional (and un-needed) complexity. I recommend to store them directly in the MDT Deployment Share.
/ Johan
Hi Johan,
Thanks.
Sorry but I don't agree with you fully ... since as per documentation of MDT as Quick Start Guide for Lite Touch Installation found I at http://download.microsoft.com/download/b/3/a/b3a89fae-f7bf-4e7c-b208-223b991e9c30/Optional%20-%20MDT%202010%20Print-Ready%20Documentation.zip ,
In this guide , initially they created custom image (WIM) from reference computer & later it deployed to another target computer...
Still I am not able to deploy custom image to target computer which is captured from WDS as well build & captured from MDT itself....
Where is mistake.....? Please explain......!!!I will do my best :)
In the MDT Quickstart Guide they first import a full source os (The entire DVD), creates a task sequence, deploy it and capture the setup to a new image (custom image)
Later they add that custom image (as a custom image) into the workbench, creates a new task sequence, and then deploy the captured image (the custom image).
The reason the deployment of the custom image works is because you already imported the setup files when importing the full source os, and MDT is smart enough to look at all imported operating systems in the deployment share, searching for the setup files.
In the case where you create a deployment share, don't import a full source os, and only add a custom image (either a wim-file directly, or from the WDS), the deployment will fail because MDT cannot locate the setup files in the deployment share. And MDT always run setup.exe, even when deploying a custom image.
If you want to know how to get your MDT 2010 deployment solution done, sign up for my free CD (online download) with step-by-step guides & videos that I have published to the management and deployment community. They are more detailed than the default MDT quickstart guide, and I have recorded every single step you need to do in order to build a MDT 2010 Lite Touch solution.
The CD, which is free to download contains the following guides and videos.
MDT 2010 Lite Touch Deployments (deployment without ConfigMgr 2007 SP2 R2, just the free tools)
- LTI01 - Installing the server for MDT 2010 Lite Touch
- LTI02 - Creating a Windows 7 reference image using Lite Touch
- LTI03 - Deploying a Windows 7 image using Lite Touch
- LTI04 - Dynamic Settings, creating and using the deployment databaseMDT 2010 Zero Touch Deployments (deployment with ConfigMgr 2007 SP2 R2)
- ZTI01 - Installing the server for MDT 2010 Zero Touch and ConfigMgr 2007 SP2
- ZTI02 - Creating a Windows 7 reference image using ConfigMgr 2007 SP2
- ZTI03 - Deploying a Windows 7 image using ConfigMgr 2007 SP2
- ZTI04 - Dynamic Settings, creating and using the deployment databaseAdditional Presentations
- E01 - New features in MDT 2010
- E02 - Upgrading MDT 2008 to MDT 2010
- E03 - Migrating Windows XP to Windows 7
Sign up at www.deploymentcd.com
/ Johan- Marked As Answer bysamtiger Saturday, November 07, 2009 10:43 AM
Hi Johan,
Thanks for statements that you made .....might be I'm not understood MDT completely that’s why I'm unable to "drive" it properly ...
One more thing I have registered for deployment CD & waiting for it *eagerly *...... :)
Thanks again...I'm glad I could help...
I couldn't quite figure out what email address you registered with, but I have approved all confirmed registrations as of now :)
