Kvz100018 - Office 2010 not staying activated after sysprep in VDI

Troubleshooting: Office 2010 not staying activated after sysprep in VDI



Document ID: KVZ100018/ Created on: Jan 23, 2011/ Updated on: Jan 23, 2011


Symptoms



I am having a problem when creating a production virtual desktop image for a client. I have a volume license (MAK) for Office 2010 standard. When I get the Office suite installed, I run through the activation process in the applications (usually Word). I then restart the machine and perform a sysprep. This is an automated process using our VDI solution (Kaviza). Once the image is done with sysprep, it saves the template as a base image from which the users' desktops are cloned.

The problem is that the newly started linked-clones from the base image are prompting for users to activate the Office suite. Is there a way to maintain the "Activated" status of the Office suite after a sysprep has run?



Cause


Response from Microsoft:
By design, there is not. In general, VMs running Office are considered separate instances. This is one anti-piracy measure; otherwise, it would be simple enough to activate one image, distribute it, and then maintain that activated status for anybody who gets that image.




Resolution


Response from Microsoft:
You may want to consider these options:

1.) Activate for the users. On first boot of the virtual desktop, run the ospp.vbs /act command (you may need to run ospp.vbs /puserops in the base image first to allow non-admins to activate). This will request activation, and the user will never see any prompts for activation. However, if hardware changes on the hosting side, e.g. the VM is moved to another server, then the user will be prompted for re-activation. This will use up another MAK activation count on your MAK key.

More info on the ospp.vbs script: http://technet.microsoft.com/en-us/library/ee624350.aspx#section1

2.) (Recommended) Set up a KMS host. If you have many desktop instances, the easiest thing to do may be to set up a KMS host and use KMS activation instead of MAK. In this way, activation is transparent to users — they will not be prompted to activate. If hardware changes are detected and re-activation is required, then Office will just re-activate with the KMS host, again invisible to the user. You won't need to worry about burning up any more MAK activations on your key.

If you have a WS 2008 R2 server, WS 2003, or W7 client to serve as your KMS host, then you can pursue this option. Here's a video that walks you step-by-step through setting up a KMS host:

http://www.bing.com/videos/watch/video/setting-up-an-office-2010-kms-host/10t43c92f