Finally after much searching I came across this article, which describes how to get around this limitation. It cost me a day of work, so I hope someone finds this helpful. If you have any questions, feel free to leave a comment below. I also noticed that I had to do this registry change Hack binary option time before taking an image.
The image does not retain this value, it gets reset after doing the sysprep. Let me know how it works out! Thanks for the tip, it worked great for the Windows 7 laptop image I am working on. The location in the registry was slightly dfferent, but it worked which is the important part!
Thanks for the head’s up on the Windows 7 Registry Key — I updated the post to include that. Do you know the registry location for this OS? If the first registry key above doesn’t resolve it, then I’m not really sure where it might be. If you figure it out, be sure to let me know, and I’ll update the post! Our organization doesn’t and this registry hack was a great workaround for us. I’m glad that others have found this useful — and I’m happy it saved you some time! And you won’t have to continually make the reg change each time.
Faced with a similar problem where we were supplied with a corporate image with only 1 rearm remaining. Meant that we had only one sysprep remaining. What about next year when we update the systems with updates and newer software. Many folk think that Microsoft has a limit of 7 of these skiprearms.
This is only true for non-volume licensing. With volume licensing you can skiprearm unlimited. I’m not sure the impact specfically to Token based or Volume Net Authenticated. The other reasons apply to resellers or mfcts. It wouldn’t be a good thing to get audited, and your systems have identical authentications.
Microsoft does try to counter this in their own way, by forcing a reauth based on hardware config changes. However with KMS, the licensing methods gives much greater latitude in hardware changes. Still means you have to rearm per the EULA. MAK activiation is actually separate from this problem. So, regardless of whether you use MAK or KMS, you could run into this problem when you’re trying to taking an image with Altiris. Hopefully that clarifies the issue, if not, let me know! Also it seems like the system has entered into the 30-day grace period when i do the slmgr command.
This post saved me at least a week of work. I’m glad that you saved you some time — I was hoping this would help many so my suffering was not in vain! Your blog, has saved me a few times now, from having to rebuild an image from scratch after spending countless hours builing it. Make sure you don’t have windows updates pending, and a reboot necessary.