none
can't capture anymore.. please help! RRS feed

  • Question

  • hi,

    i've been using mdt 2010 in the last 4ish years to deploy several hundreds of machines. now due to some mysterious reason, capturing doesn't work anymore. the visible symptom is a error message containing something about the clonetag registry entry not being writeable. i hacked around this by regedit'ing the clonetag value back in, but the result was an image that doesn't join the domain. i also deactivated the "inject mass storage driver" step and the wmp net service, but no luck.

    i don't know why sysprep fails all of a sudden. all i did was update the image with a few software installations and updates. when i try to sysprep without saving the image to the mdt deployment share, it reports that it completed successfully. if i save the image, it reboots and continues with the deployment task. which fails with the clonetag error. i've tried it with and without installing the latest windows updates. the image size is around 10 gigs, free space on the ds is around 40 gigs. after an unsuccessful capture attempt, the local admin account is locked and the hidden system partition has a drive letter.

    please help me find the error..

    my logs are here (hopefully)

    thanks,

    haklinz

    Friday, June 20, 2014 10:31 AM

Answers

  • NO! Please do *NOT* import clonetag registry key. NO, NO, NO!

    The problem here is that Sysprep *FAILED*, if sysprep succeeded, then the Clonetag key would exist.

    Yes you can work around the fact that sysprep failed, by importing the key, however the machine is *still* in an unknown/unsupported state.

    My recommendation is to check the c:\windows\system32\sysprep log files to find out why sysprep is failing.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, June 24, 2014 6:59 PM
    Moderator

All replies