Like most of what I plan to put in here, this is something that I'd forgotten about until a co-worker ran into the problem. Of course I've run into this before so I got out onto the interwebs and found the answer again. Here you go.
The easy way to get
around the three time limit of sysprepping is to either a) use a virtual
machine and save a snapshot before the first time you sysprep, or b) capture an
image through the console of the state before sysprepping, and then deploy it
when it to the same class machine when it needs updated. If you accidentally reached the three rearm
limit without having to start over from scratch, here is a step by step how to
get around it.
- Open up Registry Editor. (Start > Run > regedit)
- Browse to HKEY_LOCAL_MACHINE\System\Setup\Status\Sysprep Status.
- Change the value of CleanupState to 2. (0x00000002)
- Change the value of GeneralizationState to 7. (0x00000007)
- Browse to HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform.
- Change the value of SkipRearm to 1. (0x00000001)
- Open an administrative command prompt. (Start > Run > cmd... right click on the cmd icon and go to Run as Administrator)
- Type msdtc -uninstall and push enter. Wait a minute and reboot.
- Type msdtc -install and push enter. Wait a minute and reboot.
- Browse to c:\windows\system32\sysprep. Delete the panther folder.
- Run sysprep. It should now complete, and you can capture the image.
No comments:
Post a Comment