I'm running into a problem where I can only Sysyprep my corporate Windows 7 Image 3 times before I run into fatal errors during the Generalize Phase of Sysprep. According to the research I have done, Microsoft recommends you rebuild your image from scratch at this point. I was wondering what anyone else does to get around this?
More Background Info
Here is the way I have things setup:
I have my master Windows 7 image
Each month I want to update the image to incorporate the latest Windows/Adobe/Java updates
After making the updates, I have been Sysprep'ing the image, and saving the Ghost files
On the fourth iteration of the image, I recieve an error during Sysprep
I have found these links:
After following these steps, I added this code to my answer file:
<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">
This seems to allow Sysyprep to proceed, but the rearm count never goes back to three and Microsoft doesnt recommend leaving that section of code in the answer file:
You must make sure that the <SkipRearm> setting is removed from the final unattended file that is used to deploy computers in a production environment. If <SkipRearm> is not removed from the unattended file that is used to deploy computers in a production environment, the KMS current client count does not increase for new clients that are added to the network.
Soooo....How do you get around this? Did I do something wrong when I was following those steps? I find it hard to believe that corporations out there have to completely rebuild their Windows image every 3rd iteration of Sysprep. Please help!
Thanks a bunch!!