Uploading a New Image
The Basic Process:
- If your MDT does not have one already, create an upload/download task sequence. You only need one for both tasks, (Sysprep and Capture)
- Upload the current image to a computer and set it up how you want.
- Select the task sequence, “Upload an Image”.
- Name your new image, and make it happen.
- Create a new task sequence for downloading the new image.
- Update the Deployment Share.
Creating a new Task Sequence for Upload
A NOTE BEFORE BEGINNING: FAMILIARIZE yourself with MDT, and its functionality, especially the area concerning task sequences. MDT has a built-in reference library which is broken down into index format, additionally, the library has built into it step by step instructions for most MDT related tasks. The library is also interconnected with different MDT tools for technical functionality and easy reference.
1. When starting the task sequence, you will be launching the MDT 2010 workbench on the MDT VM. When launched, you will click the task sequence option, once selected look to the right side of the screen and click ‘New Task Sequence’ a variety of other options exist, but ignore those for now.
2. Once clicked, MDT will initiate a wizard. Simply select a name, ID, and add any required notes for your Task, then click the drop down for preexisting templates, select the Sysprep and Capture Template. Make sure to select the correct Operating System, that is, the one which matches the Operating System you intend to capture.
3. The actual task sequence is run from the computer you are intending to capture.
4. **A common mistake at this point is to boot the reference computer from your LiteTouch image and start this task sequence. (Kevin Ledman Core team blog.) ** –Don’t do it.
5. To run the task sequence, you connect to the deployment share and launch the LITETOUCH.WSF through manual interaction with the command prompt.
6. RUN CMD – enter:
net use \\mdt\DeploymentShare$ /user:domain\username
7. Once the connection is established, execute LiteTouch.WSF
9. Select the task sequence you created earlier in step 3.
10. Use your Sysprep and Capture option, and supply the location for storage and name of the image you are capturing.
11. Supply your login credentials. – Follow the Wizard Steps.
12. MDT will assume control, and the task sequence will run through its course here, assuming it can run uninterrupted. MDT will copy the reference computer, launch the sysprep and apply the LiteTouch Image. The computer will reboot during this phase.
13. The computer will reboot, and in this portion the size of the image, and speed of the computer govern the time required for the installation. Expect this step to take a substantial amount of time.
14. After the capture is completed, you can go back to MDT – and import the image, as a customized image file in MDT itself, for use in future task sequences.
15. To do this, click Operating Systems, in the index on the left side. Look to the right, and click ‘Import Operating System,’ this will initialize another wizard.
16. Select Custom image file and hit next – find your file. Most likely under
17. Include the setup files for the OS which you are importing and complete the wizards. This is important, if you select the wrong OS – the system will not install on subsequent attempts.
18. Should be done! The file will be available for use with any new task sequence you need.
**All these techniques were taken from technet, or similar blogs and the content is property of their respective authors – thanks for the information!
The most common error:
The task sequence has been suspended. LiteTouch has encountered and Environment Error (Boot into WinPE!) OK to Reboot
There are two primary scenarios where this can happen (although not limited to these). When booting into a LiteTouch WinPE image, we can encounter this error.
- With “The task sequence has been suspended” dialog up don’t click OK, press F8 right then, and run diskpart right out of the PE instance. – so boot from standard Windows PE and open diskpart, select disk 0 and type “clean”. Following this, you will be able to boot the LiteTouch.wim install and start over again.
- In the middle of a LiteTouch OS installation, and the user booted back into WinPE, when the new OS should be running. User should remove the WinPE Boot media or adjust the boot order.
- We start a LiteTouch installation from scratch, *however* there was a previous LiteTouch Task Sequence running, and was not properly cleaned up. In that case remove the c:\minint\ and/or c:\_SMSTaskSequence directory and reboot back into WinPE.
Good references:How to run a Sysprep and Capture Task Sequence From MDT 2010 (For a generalized breakdown of the process.) LiteTouch has encountered and Environment Error
(For error correction, several are covered.)