Explanation of what re-arming a Microsoft operating system is all about

Very good piece in one of the Citrix VDI in a box best practice articles at http://support.citrix.com/article/CTX134349.

VDI-in-a-Box 5.1 offers a new setting at the template level to reset the activation timer. Leaving this unchecked implies that the image’s activation clock is not rearmed during prepare. Checking the box implies that the image’s activation clock is rearmed during prepare, decrementing the activation count. If the image’s activation clock is rearmed more than 3 times before the image is activated by KMS (Microsoft activation Key Management Service), the image cannot be prepared because the /generalize will fail.


According to Microsoft: “Resetting the activation timer prevents the image’s grace period from expiring before the image is deployed. Running Sysprep.exe does not remove the installed product key, and administrators are not prompted for a new key during mini-setup… When building demo virtual machines (VMs) for internal use (e.g., building VMs for the organization’s sales department or to set up a temporary training environment), running the Slmgr.vbs script with the /rearm command-line option extends the grace period another 30 days, which in turn resets the activation timer but makes no other changes to the computer. The activation timer can be reset three times for computers running Windows 7 or Windows Server 2008 R2.”

How to tell if your PC supports XP Mode on Windows 7

Thinking of rolling out Windows 7 ? Then it could be that you will want to run XP Mode for backwards compatibility of older applications. XP mode allows you to run applications in a Windows XP SP3 virtual machine and present the application to the user as though it is running locally on the Windows 7 machine. Well, if you have a fleet of machines in your organisation then its likely you have purchased over time and don’t know which support hardware assisted virtualisation and which don’t. Microsoft have now bought out a simple tool that you can run on a logged on machine (admin privileges using run as required of course) that will tell you if the processor supports virtualisation and, more importantly, if its enabled for virtualisation.

There’s also a command line giving the opportunity to run a start up script and write a log file centrally so that you can see which machines can support this feature and which can’t.

You can download the free tool from http://go.microsoft.com/fwlink/?LinkId=163321.