Friday, July 16, 2010

MDT 2010 failure during sysprep and capturing

I am using MDT 2010 to do a sysprep and capturing task sequence on the Windows 7 reference machine.
First of all, I mapped the deploymentshare$ to drive Z. After that, I execute the Litetouch.wsf file under the deploymentshare$\script and then go thru the wizard. Everything run smooth until the sysprep finished, a failure occur like the screenshot below.
This failure happened due to the registry key CloneTag under HKLM\SYSTEM\Setup is deleted during the start of the sysprep. There are few ways to counter this failure:
  • Go to your sysprep and capturing task sequence, Execute Sysprep, Options tab, Add, Registry Setting. Enter SYSTEM\Setup in the key box, and enter CloneTag in the value name box and leave the value box blank. This whole step is to add the registry key back to HKLM\SYSTEM\Setup after the sysprep completed.
  • You can also modify the script to prevent the registry key from being deleted. Go to your deploymentshare folder and look for a script named LITSysprep inside the scripts folder. Right click, edit to do modification in the script. You can either remove the oShell.RegDelete "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" or you might want to add .// infront to turn it into a comment.
Both ways stated above can resolve the failure occur during sysprep and capturing. This topic also discussed in technet forum, and here's the link.

10 comments:

  1. I actually had to put a value of 0 for the CloneTag but it worked like a charm....

    THANKS!

    ReplyDelete
  2. Thank you so much for this post, it was driving me crazy, actually not a drive, just a short walk! Seriously, your help was really appreciated!

    ReplyDelete
  3. Cindy is correct, did not work until I put a value of 0 in for the CloneTag. Thanks to both of you!!!

    ReplyDelete
  4. Just wanted to say thanks for this and the other commentators, this solved my problems! :)

    ReplyDelete
  5. Thx worked like a charm.

    ReplyDelete
  6. This post is amazing, I have been chasing that for a while and here these simple but accurate paragraphs solved the issue.

    ReplyDelete
  7. Thanks for this. I hope everyone looks at the comments and includes the value of 0.

    Dan@switchtechnologies.com

    ReplyDelete
  8. While the advice in this post will allow you to bypass the error, this is not a good thing. The clone tag missing means that sysprep did not complete successfully and the computer is in a half way state. This can lead to many problems when trying to re-deploy the image (BSODs etc.). You can check the sysprep logs under C:\windows\system32\sysprep\panther to get an idea of why it is failing. The most common reason I've come across is the windows media player network sharing service is running. I would suggest stopping the service and trying the sysprep again.

    ReplyDelete
  9. thanks. changing the script did the trick for me. just once i'd like to update and redeploy my image without hours of searching for fixes. mdt is a piece of ****.

    ReplyDelete
  10. Worked for me! I just removed all references of clonetag outta the ltisysprep script and wolla it bloooody worked!

    ReplyDelete