locked
Sysprep and capture task sequence does not Sysprep and capture. RRS feed

  • Question

  • I have been playing around with MDT for years and never really got it to work (I think it was actually Dell drivers fault all along but when you are learning always I assumed it was me doing something wrong) but every six or so months I dust it off and try again.

    I am running MDT 6.1.2373.0 (MDT 2012 SP1 I believe) on a Windows Server 2003 R2 SP2 box.  I have deployed Windows 7 Enterprise x64bit using a MDT deployment task sequence along side a few programmes.  After updating to Windows 7 service pack one I would like capture my reference computer (a physical laptop as my work machines just does not have it in it to run virtual machines) to be used to deploy down to all machines.

    I created a sysprep and capture task sequences using my Windows 7 Enterprise x64bit operating system (not service pack one) that I originally deployed to my reference computer as the reference image, jumped onto the laptop, browse to the deployment file share and ran litetouch.vbs.  I fill in my user-name and password, select my capture task sequence and then nothing.  After the initial wizard disappears I see a little progress bar pop up and then I get a message saying "Success, operating system deployment completed successfully.  The computer is now ready to use.  During the deployment process, 0 errors and 0 warnings were reported." but MDT never actually syspreps and captures my reference computer.

    I have looked through BDD.log, LiteTouch.log and smsts.log files but everything seems normal to me (link to them below) so would really like some help to get MDT to work.

    https://skydrive.live.com/redir?resid=6E2ADB8362328B8F!7677&authkey=!ABQuH5f9xSDXUUI

    Tuesday, June 25, 2013 1:07 AM

Answers

  • What's your CustomSettings.ini look like?  Do you have DoCapture configured anywhere?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek


    I have left the CustomSettings.ini, Bootstrap.ini, Unattend.xml and the task sequence all at their default values so I have not specified DoCapture anywhere myself.

    Edit: As I was typing a response to this I think I found my issue.  Under the CustomSettings.ini SkipCapture
    was set to YES.  I changed this to NO and I got a new wizard page I had not seen before that allowed me to specify the UNC path where the captured image should go and now the sysprep and capture process is
    working (or at least looks like it is).

    • Marked as answer by BWMerlin Thursday, July 4, 2013 12:17 AM
    Tuesday, June 25, 2013 4:57 AM

All replies

  • What's your CustomSettings.ini look like?  Do you have DoCapture configured anywhere?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, June 25, 2013 2:20 AM
    Answerer
  • What's your CustomSettings.ini look like?  Do you have DoCapture configured anywhere?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek


    I have left the CustomSettings.ini, Bootstrap.ini, Unattend.xml and the task sequence all at their default values so I have not specified DoCapture anywhere myself.

    Edit: As I was typing a response to this I think I found my issue.  Under the CustomSettings.ini SkipCapture
    was set to YES.  I changed this to NO and I got a new wizard page I had not seen before that allowed me to specify the UNC path where the captured image should go and now the sysprep and capture process is
    working (or at least looks like it is).

    • Marked as answer by BWMerlin Thursday, July 4, 2013 12:17 AM
    Tuesday, June 25, 2013 4:57 AM
  • Yup, that will do it.  If you want to leave that Wizard page hidden (to help with automation), but still force the capture, the settings is DoCapture=YES.  You may not want to put it in the [Default] segment, though, as it would then set that value for everything.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, June 25, 2013 1:13 PM
    Answerer
  • I can't get it to work in 8.1 either - been trying for days and everytime I get over one hurdle another pops up - seems the guys the wrote 8.1 and the sysprep guys have never met.  Good thing this tool is free or I would want my money back. Wait - when you count the man hours I have put into this it is anything but free!!  I could have deployed manually to about 20 systems in the time I have fought with this - and I am still no further ahead.  I google error code after error code and get wierd suggestions and then try them out of desperation, but they seldom do any good. It seems like every error code has about 100 possibilities of what might be the cause. I deeply regret upgrading to the 2013 vesion of MDT and Deployment kit.
    Tuesday, November 12, 2013 8:18 PM
  • Greg,

    I've syspreped and captured 8.1 numerous times with MDT 2013,  that's not saying I don't share your frustrations.  I'd love to have those hours I spent googling and tracking down error messages.  It comes with the job and always feels great once solved.  Can you post your logs?  People on here are more than happy to help you out.


    -BrianG (http://supportishere.com)

    Wednesday, November 13, 2013 8:09 AM
  • Thanks - I finally got it to work by creating a new reference machine from scratch.  I built my new reference machine by using the MDT to deploy Win 8.1 , then manually added Office 2013 and then Sysprepped and captured immediately. It seems that having a domain user log on and test app functionality and then leave the domain was a bad idea - sysprep no like that. It was giving me the Clone Tag error when I tried to sysprep the same machine twice.  And then there was problems with the windows 8 apps - this link helped me figure out why it was erroring - but did not deal with having domain users log on - seems to be different than local users - the fix did not quite work.

    http://4sysops.com/archives/how-to-remove-windows-8-apps-before-you-run-sysprep/

    So to others out there I say sysprep your reference machine right away after creation and installation of standard apps.

    Thursday, November 14, 2013 8:39 PM