How to run a Sysprep and Capture Task Sequence From MDT 2010

How to run a Sysprep and Capture Task Sequence From MDT 2010

  • Comments 37
  • Likes

Hello, my name is Kevin Ledman. I am a Support Escalation Engineer in the Windows group and today’s blog will cover how to run the new Sysprep and Capture Task Sequence included with MDT 2010.

If you choose to deploy an operating system manually or need to make customizations outside of the MDT task sequencer, you can still use MDT to automatically sysprep and capture the image for future use.

To configure the task sequence, launch the MDT 2010 deployment workbench and create a new task sequence using the sysprep and capture template.  Answer the remaining wizard items, making sure to choose an OS source that matches the OS you are going to be capturing.

  clip_image002

Update your deployment points and switch to the reference computer to start the task sequence.  **A common mistake at this point is to boot the reference computer from your LiteTouch image and start this task sequence.  The sysprep and capture task sequence is designed to be run from the desktop of the reference machine similar to a post OS installation task sequence.  To launch this, you will need to establish connectivity to the deployment share and launch LiteTouch.WSF manually.  Because you are logged in to the reference machine as a local administrator and not joined to a workgroup, be sure to establish the session under the same security context that will be used for the task sequence:

net use * \\mdtserver\DeploymentShare$ /user:domain\username

Once the connection is established, execute LiteTouch.WSF:

cscript \\mdtserver\DeploymentShare$\Scripts\LiteTouch.WSF

 

clip_image004

The MDT Wizard Screens will launch and prompt for the information required to complete this task sequence.  **Note – we will still process customsettings.ini for this task sequence.  If you have modified customsettings.ini to skip wizard screens, those settings will be honored with this task sequence as well.

clip_image006

Choose the task sequence you have created.

clip_image008

Choose the capture option and supply the location and file name.

clip_image010

Supply the credentials that LiteTouch will use to connect to the deployment share.

clip_image012

View the summary and click ‘Begin’ to start the task sequence.  If you receive error “A connection to the distribution share could not be made” see the following blog: 

http://blogs.technet.com/msdeployment/archive/2009/09/18/fix-for-multiple-connections-to-a-server-or-shared-resource-by-the-same-user-using-more-than-one-user-name-are-not-allowed-problem-with-mdt-2010.aspx

clip_image014

MDT will copy the necessary files to the reference computer, launch sysprep, apply the LiteTouch Image and reboot the machine

.

 

clip_image016

LiteTouch boots and begins the capture of the image.  Depending on the size of the installation, this may take a significant amount of time.

 

Once the capture has completed, you can now import the captured image as a custom image file in MDT and use it for future task sequences.

clip_image018

Add new operating system and choose custom image file.

clip_image020

Point to the “Captures” path and move it to the to the deployment share.

clip_image022

Include the setup files for the OS which you are importing and complete the wizards.

clip_image024

The operating system is now ready for use with new task sequences.

Kevin Ledman
Support Escalation Engineer
Microsoft Enterprise Platforms Support

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi there. I tried this process on a Windows 7 RC build but the sysprep fails with the error:

    FAILURE (Err): -2147024894  0x80070002: Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading. LTISysprep 13/10/2009 3:33:45 p.m. 0 (0x0000)

    FAILURE ( 6191 ): Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading. LTISysprep 13/10/2009 3:33:45 p.m. 0 (0x0000)

    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 13/10/2009 3:33:46 p.m. 0 (0x0000)

    This problem does not occur in Windows 7 RTM - however the work I am doing at the moment is on the RC build 7100 and I need it to be working in the RC version.

  • Hi there. I tried this process on a Windows 7 RC build but the sysprep fails with the error:

    FAILURE (Err): -2147024894  0x80070002: Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading. LTISysprep 13/10/2009 3:33:45 p.m. 0 (0x0000)

    FAILURE ( 6191 ): Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for reading. LTISysprep 13/10/2009 3:33:45 p.m. 0 (0x0000)

    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 13/10/2009 3:33:46 p.m. 0 (0x0000)

    This problem does not occur in Windows 7 RTM - however the work I am doing at the moment is on the RC build 7100 and I need it to be working in the RC version.

  • My Sysprep and Capture TS keeps skipping the capture wizard.  Here is my customsettings.ini:

    [Settings]

    Priority=Default

    Properties=MyCustomProperty

    [Default]

    SkipBDDWelcome=YES

    OSInstall=Y

    SkipAppsOnUpgrade=YES

    SkipCapture=NO

    SkipDomainMembership=NO

    JoinDomain=company.net

    SkipUserData=YES

    SkipAdminPassword=YES

    SkipProductKey=YES

    SkipBitLocker=YES

    SkipLocaleSelection=YES

    KeyboardLocale=en-us

    UserLocale=en-us

    InputLocale=0409:00000409

    SkipTimeZone=YES

    TimeZone=010

    TimeZoneName=Mountain Standard Time

    Please advise.

    Thanks,

    Tsunami2475

  • I do not recieve the capture options screen when selecting my sysprep and capture task sequence and if I try to go ahead I recieve 2 erros and 6 warnings. How do I get my task sequence to give me the capture options? I am just using MDT 2010 and WAIK but I am new to all of this.

    Thank you,

    Cory

  • i know this is a late comment and hopefully you guys will still be able to respond to it... is there a way to set the task script to allow you to change the URL destination so that if one is running the whole deployment wizard using NewMedia/UFD to be able to capture the image right to a USB drive.... it's much faster than moving over the wire.  My current project I've been creating UFD model of installation and I'm trying to capture the sysprepped reference image and find it easier to send to UFD than to the deployment share.   any suggestions/help.  I haven't found anything in the chm files to help with this.  Thanks!!!!

  • When I try to sysprep and capture a Windows 2003 reference server, it never makes it to the capture section.  I get an error that says Failure (6102): -2: Expand Sysprep files from deploy.cab  

    What am I doing wrong.  I would like to start using MDT2010 to deply Windows 2003 servers but this is holding me up.

    Thanks, any help will be nice.

    Jason

  • We would like to do the same thing as Jasoned.  We boot to USB Media and run all of our MDT Task Sequences run perfect, BUILD, DEPLOY, SYSPREP, SYSPREP and CAPTURE accross the wire to our MDT server.  What we cannot get to work is booting to the USB media and running our Task Sequence to capture to the USB Drive,  It wants a UNC Path, which we don't have since we are off the wire when we want to do this.  We have searched everywhere and cannot find anyone able to do this.  We have resorted to booting to USB, exiting MDT, in the cmd prompt browsing to our USB drive and running a batch file we created to capture.  Please help.

  • TomF -

    Does using a unc path of \\localhost\<usbdriveletter$>\<where youwant the image> not work?

    Or maybe 127.0.0.1 instead of localhost?

  • TomF -  You need to build the media for deployment.  there is a Advanced Configuration folder at the bottom of your deployment share.  There is a option for Media, create a new Media for your deployment.  just remember it needs to be in its own folder, NOT in the deployment share.

  • Guys,

    Every time I run this, it gets to the "Execute Sysprep" part and then keeps asking me for random windows drivers from the C:\drivers\1394 folder.

    For example, amdagp.sys and a few other sys files. I cant find them on any machine or xp disk..

    "The file AMDAGP.SYS on windows cd is needed"

    Any ideas please?

    Thanks

  • Hi guys,

    I ran through this and at the end when I've run litetouch.wsf and hit Begin - nothing happens.  No sysprep starts, no error messages... nothing.  Any idea what I should be looking for?  

  • I've gotten this task sequence to run, it also captured the image for me.  After reloading the image with a another task sequence everything comes up fine, but is there a way to keep if from trying to reconnect the share after OS loads.  

  • Thanks for this nice tutorial! I've used it :-)

    Note: run cmd as Administrator (even if you are logged in as Administrator) otherwise you get thisError:

    FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object

  • @Paul:

    Doesn't the MDT wizard continue after the OS loads? There's your problem. When the OS loads, the wizard should continue, install apps if you've got them, tattoo etc. then gives you the summary that deployment was successfull. When you close the summary the deploymentshare will be disconnected and the c:\MININT directory will be removed.

    Check the logs in the MININT directory on the client to see what fails, if your wizard doesn't continue

  • @Eric

    I had the same problem and found the answer by mistake while searching for one of the error messages from the log... you have to be logged into the PC as the local administrator rather than your domain account.  So, log in as local admin, map a drive to your deployment share using your domain credentials and THEN run the LightTouch.wsf script.  Once I did that it ran as expected.