MDT 2010 New Feature #13: New task sequence templates

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

BigDon86 — Wed, 08 Jul 2009 02:24:33 GMT

Hi;

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

Thanks

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

mniehaus — Wed, 08 Jul 2009 02:40:02 GMT

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

-Michael

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

Zouleous — Wed, 08 Jul 2009 21:59:29 GMT

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

mniehaus — Wed, 08 Jul 2009 22:08:34 GMT

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

Zouleous — Thu, 09 Jul 2009 18:14:25 GMT

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

mniehaus — Thu, 09 Jul 2009 18:21:03 GMT

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

m9600174 — Tue, 28 Jul 2009 10:44:44 GMT

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

mniehaus — Tue, 28 Jul 2009 10:53:12 GMT

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

Zouleous — Tue, 04 Aug 2009 17:03:15 GMT

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

m9600174 — Wed, 05 Aug 2009 10:36:11 GMT

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

davidph — Wed, 05 Aug 2009 13:29:55 GMT

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

davidph — Wed, 05 Aug 2009 13:34:21 GMT

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

massivesystem — Tue, 25 Aug 2009 18:46:29 GMT

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

mniehaus — Tue, 25 Aug 2009 18:52:37 GMT

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

Thanks,

-Michael

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

vvcomsys — Sat, 28 Nov 2009 23:47:18 GMT

Hi All,

I think I found solution for this error.

All credits are for Johan Arwidmark for his "Capture only Task Sequence for MDT 2008 (Lite Touch)"

I have added two new Task sequences after Set Phase

1.Set Image Folder >Task sequence Variable-"ComputerBackupLocation" ->Value \\server\Distribution$\Captures

2.Set Image Name >Task sequence variable - "BackupFile" -> Value ImageName.wim

Looks like there is bug in CaptureOnly.xml

Cheers

Vinnie

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

mniehaus — Sun, 29 Nov 2009 00:03:47 GMT

Normally the wizard would ask you for those two values. If you aren't seeing that wizard pane, it's because your computer is domain-joined. It's not recommended to sysprep and capture a domain-joined machine.

-Michael