I have setup a Windows 7 image on a fog server ver. 0.32 with the generalize option in sysprep. I noticed that once I deploy the image, the rearm count on the imaged PC goes down to one to 2. In the long run this can cause issues in the future as I am constantly updating the images. If I were to update the image and sysprep it again the next time I deploy it the rearm count will go down again to 1. As Windows only allows 3 rearms I would run out of rearms very quickly.

The solution I have come up with is to have two separate images, one base image and a deployable image. I will update the base image and upload to the image that will need to be deployed. That way my base image always keeps the original rearm count and I do not run into the issue of running out.

This seems like a hassle; does any one have a better idea or know how to avoid having to keep to images to avoid running out of rearms? Thank you in advance for your help.

Using a “master image” as BWelmers mentioned, either the original Microsoft image which has never been rearmed or the first iteration of your standard image which has been rearmed once, also works well, just remember to always update your image from that “master image” and you won’t exceed two rearms.

Alternatively, if you are planning a small deployment, Joseph’s suggestion of utilizing SkipRearm may work quite well with a standard image, allowing Sysprep to perform all of its normal functions except rearming the activation of your image.

Though both of those methods may work to accomplish your task with FOG, you may also want to consider the use of the Microsoft Deployment Toolkit (MDT). Many find MDT to be extremely beneficial as it combines all of the official tools (Sysprep, Windows Automated Installation Kit (Windows AIK), and Windows System Image Manager (WSIM)) into a single workbench interface that can help automate the entirety of the process. Additionally, it is compatible with Windows XP, Windows Vista, Windows 7, and Windows Server 2003, 2008, and 2008 R2, which means learning one utility to do all of your deployments. Furthermore, as stated above, it is exceptionally useful in creating “universal” images as it can easily add or remove drivers or applications from the deployment images.

Also, one more side note is to check out Build a better desktop image as it is a great article for more detailed information on desktop image management.

I create a lot of images and this is the only reliable way I have found to keep building updated images without using TB's of space, or as WinOutreach5 mentions MDT, WAIK etc. to deploy and then automate adding updates, however this will not work easily if you have a lot of non MS updates.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.