The initial indication I had problems was that the local administrator account was disabled after sysprep on both the source laptop, and also on any VMs or laptops I tried to image.

We (I) am building a quick first MDT 2012 Windows 7 image for a new client, with the intent to bring them up to a full-blown MDT image in the near future, as they do have an SCCM 2012 and KMS server base. I have built several MDT images to date, but all were built from source CD up to drivers and apps.

In this particular case the client was already using ghost images and we had a short deadline to update their image for our break/fix shop. So, in this case I did a sysprep / capture with MDT 2012, sent the image to our tech who then made several updates and sent it back to me.

I did not realize the Rearm count had decremented to (0) and am now in a delima. We don't have time for the tech to redo his manual work, and our Rearm count is at 0.

Is there a ligit (even if I have to contact Microsoft) way to reset the Rearm count (for legitamte purposes) to avoid loosing days + of work?

Thank you,

0 Comments   [ - ] Hide Comments


  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment

Answer this question or Comment on this question for clarity



if this is a wim image you could mount the wim r/w and then edit the sysprep answer file and add

<settings pass="generalize">
        <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

you also may need to edit the offline registry at C:\Windows\System32\config

and add a value of one to the key


Answered 03/18/2013 by: SMal.tmcc
Red Belt

Please log in to comment

Upon more research I found a solution. I had found parts and pieces of these processes previously but this was the first answer with all the pieces.

Please read the two references below carefully and combine them - it resolved my issue.

From http://www.system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times/

Verify these settings:

After done with the registry, do the following :

  1. Start -> Run : msdtc -uninstall (wait few seconds)
  2. Start -> Run : msdtc -install (wait few seconds)
  3. Restart the machine
  4. Check the registry for the right registry keys values
  5. sysprep with the new XML answerfile.

The following was referenced in the article above and also needs to be performed before syspreping:
Edit your unattend.xml file per http://support.microsoft.com/kb/929828
which further substantiates the process above.

This worked great for my situation. The Remaining Rearm count is still (0), but it allowed me to sysprep my image addition times - following the above processes.

Answered 03/18/2013 by: 99scooter
Senior White Belt

  • I am going through the same issue but using UIU. It creates it's own sysprep file but I'm wondering how to edit the answer file?
Please log in to comment