Welcome to TechNet Blogs Sign in | Join | Help

MDT 2010 New Feature #13: New task sequence templates

There are two new Lite Touch task sequence templates provided in MDT 2010:

  • Capture only (CaptureOnly.xml).  This task sequence includes only the steps to sysprep the OS, reboot into Windows PE, and capture a WIM file (with the right /FLAGS value).  We would prefer that you use a full task sequence to do the complete build/sysprep/capture process, but if for some reason you can’t do that then you can consider this template to reliably perform those last few steps.
  • Post OS Installation Task Sequence (StateRestore.xml).  This task sequence includes all the “State Restore” phase activities: installing applications, enabling BitLocker, restoring the user state, and even the “capture only” steps described above.  This is useful in cases where you have already built the OS (maybe you deployed an already-built VHD to Hyper-V), but now you want to customize it.
Published Wednesday, July 01, 2009 9:53 PM by mniehaus

Comments

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, July 07, 2009 7:24 PM by BigDon86

Hi;

Neither of the features above seem to work with Windows 2003.  True?

Thanks

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, July 07, 2009 7:40 PM by mniehaus

These new templates should work fine with Windows XP and Windows Server 2003.

-Michael

# re: MDT 2010 New Feature #13: New task sequence templates

Wednesday, July 08, 2009 2:59 PM by Zouleous

How come the task sequence wizard asks me to specify an OS to deploy if I'm using the capture only template?

# re: MDT 2010 New Feature #13: New task sequence templates

Wednesday, July 08, 2009 3:08 PM by mniehaus

We include a disabled step in the task sequence to install an OS.  This causes a sysprep.inf or unattend.xml to be associated with the task sequence.  If we didn't do that, there wouldn't be a sysprep.inf/unattend.xml available for the capture process to use.

-Michael

# re: MDT 2010 New Feature #13: New task sequence templates

Thursday, July 09, 2009 11:14 AM by Zouleous

So should I just pick the OS that will be captured and disable the step?  Then edit the sysprep.inf in the task sequence OS info tab to reflect what I want in the sysprep.inf?  I assume this task needs to be run from within the OS so it can sysprep the image using those settings and then reboot for a capture.

# re: MDT 2010 New Feature #13: New task sequence templates

Thursday, July 09, 2009 11:21 AM by mniehaus

The step in the task sequence is disabled by default for this template.

Yes, you can edit the sysprep.inf associated with the task sequence and that will be copied to C:\Sysprep before running sysprep.

-Michael

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, July 28, 2009 3:44 AM by m9600174

Hello Michael

I tried the capture only task. I booted in PE and could select the task, choose capture and specify the name of the wim file. The task sequence starts but when sysprep starts, the task aborts with an error 'Unhandled error returned by LTIsysprep: the system cannot find the file specified (-2147024894 0x80070002)'.

Thanks for your advice.

Pieter-Jan

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, July 28, 2009 3:53 AM by mniehaus

That's because this isn't just a "Capture" task sequence.  It's a "Sysprep and Capture" task sequence.  You need to start it in the full operating system.  It will take care of running sysprep, rebooting into Windows PE, and capturing a WIM.

We modified the name after MDT 2010 Beta 2 was released because this seemed to confuse lots of people.

-Michael

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, August 04, 2009 10:03 AM by Zouleous

Where does the task sequence get the deploy.cab files to run sysprep against an XP image?

Also, how do I initiate the task?  I tried

cscript \\server\deploymentshare$\scripts\litetouch.vbs

I thought that would do it, but it returns a Wizard Error that says "A connection to the deployment share (\\server\deploymentshare$) could not be made.   The Deployment will not proceed."  I can ping the server and even open the window manually from the run line although it does require credentials.  Do I have a permissions issue?  Mind you I have no problem launching the Wizard from PE deployment media.

# re: MDT 2010 New Feature #13: New task sequence templates

Wednesday, August 05, 2009 3:36 AM by m9600174

the cscript part is too much. Just run

\\server\deploymentshare$\scripts\litetouch.vbs

Then a dialog appears where you fill in your credentials, next a dialog with all the defined task sequences (the same dialog you get when you boot from PE).

Cheers

Pieter-Jan

# re: MDT 2010 New Feature #13: New task sequence templates

Wednesday, August 05, 2009 6:29 AM by davidph

I'm also having problems with the capture only task in MDT 2010

I've executed litetouch.vbs from the running reference system, it allows me to select the Capture only task I've created from the template, runs sysprep and reboots.

Once it reboots, it launches the PE image and starts to create the WIM file. However, it fails with 5 errors, stating that it cannot access the deployment share. I don't get the option to enter any credentials either.

From the command prompt I have a IP address and can manually map a drive to the deployment share. I'm guessing it's a credentials issue, but I can't see an option within the task sequence to add them in.

What needs to be present on the donor computer for this to work properly?  

Cheers,

David

# re: MDT 2010 New Feature #13: New task sequence templates

Wednesday, August 05, 2009 6:34 AM by davidph

I forgot to mention - if I capture an image as part of a standard deployment task to a reference computer it works fine - so it appears it's missing something that these tasks put on the image.

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, August 25, 2009 11:46 AM by massivesystem

I have a issue that I can't figure out. I am using MDT 2010 to deploy windows 7 Ent, I have been using MDT 2008 for sometime now. Let me run through what I have done so far. I have installed MDT 2010 and all needed componets, I have of course added the OS, drivers, created a deploment share, and a task sequence to use to build my Win 7 image. A new task sequnce that came with MDt 2010 is a capture Only task. I have created it, and updated the deployment share. From my Win 7 desktop (windows not PE) I have ran \\servername\deploymentshare$\scripts\litetouch.vbs, and select the capture TS from the options. The Win 7 build runs sys prep and reboots the pc and kicks it into Win PE to prepare it for capture. Nothing is captured of course and it gives me 2 errors and 1 warning which are:

Warning- Unable to validation connectiuon because a black UNC was specified. Error creating an imagge of drive d: rc=2

ZTI error- NON -zero return code by ZTIbackup, rc=2.

When i created the capture TS with-in MDT I was never ask to create or provide a UNC. I am totaly lost.

Also why was the capture only TS created when above you state " We would prefer that you use a full task sequence to do the complete build/sysprep/capture process, but if for some reason you can’t do that then you can consider this template to reliably perform those last few steps"

# re: MDT 2010 New Feature #13: New task sequence templates

Tuesday, August 25, 2009 11:52 AM by mniehaus

Can you e-mail me (mniehaus@microsoft.com) your BDD.LOG?  

Thanks,

-Michael

Anonymous comments are disabled
 
Page view tracker