I’ve been avoiding activating Windows installations in my home test environment with the product keys from my TechNet subscription because I’ve been afraid of running out of keys. Fortunately that fear has been mostly unfounded. I won’t go into what I really think about product activation but if you’re interested in how to manage your TechNet or MSDN keys, I have discussed how I’m doing that here.
Microsoft delivered a webcast recently, entitled Product Activation in Development Environments, which discusses Windows Product Activation for development and test environments. Although aimed at developers using an MSDN subscription (IT Pros don’t have to worry about licensing and product activation?) the concepts discussed apply to TechNet subscriptions as well.
A companion white paper, Windows Activation in Development and Test Environments, can be viewed on TechNet or downloaded as a Word document. The webcast and white paper go into plenty of detail about production activation, different product key types and how to manage product activation, but they are focused on corporate development and test environments. If you have a personal TechNet subscription for your own testing, your options are limited in comparison.
What do you get with a TechNet subscription?
Quite a lot actually. If you don’t already have a TechNet Plus subscription you should read about it here (read about MSDN subscriptions here - MSDN gives you much more than TechNet, but with a price to match).
However it is interesting to discuss what you don’t get with a TechNet or MSDN subscription, and that is the activation feature that would make activation simplest – Key Management Service (KMS) keys. You do get retail and MAK (Multiple Activation Key) keys. This means that the number of activations that you are entitled to are finite. What I wasn’t aware of is what the number of activations is for each product.
Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2 and Office 2010 products must all be activated using Volume Activation (VA) 2.0 product keys. TechNet provides MAK keys for Windows Server and Enterprise editions of Windows 7. Retail keys are provided for all other editions and other VA 2.0 products.
In the case of Windows Server 2008 R2 (Standard and Enterprise) and Windows 7 Enterprise, the number of activations is 500 for each. Windows Server 2008 MAK keys also provide for 500 activations, but Windows Vista Enterprise gets only 10. At this stage, I only have access to Retail keys for Office Professional Plus 2010, but I do get 10 activations for each version (totalling 30) of Visio and Project 2010 (Standard, Professional and Premium). Perhaps more keys for Office 2010 are forthcoming.
Strategies for managing production activations
TechNet and MSDN subscriptions are not entitled to KMS keys, so you will have to use at least some of those MAK activations. In my own test environment, I have activated my Hyper-V host, a domain controller and a server used for hosting databases and a couple of other services. I am now going to activate almost all of my virtual machines that I intend on keeping for any extended period of time.
To enable reuse of activations in the event of redeploying Windows to a virtual machine, there are a couple of steps you should follow:
- Assign virtual machines by operating system, i.e. virtual machines should run Windows Server or Windows client operating systems
- Don’t delete your virtual machines (VHDs or VMDKs are OK to delete), instead reuse them
Reinstalling the same version and edition of Windows using the same product key on a machine should not count against your total activation account.
Update: OK, my information in regards to MAK keys wasn’t exactly correct. The TechNet site doesn’t make it exactly clear as to what happens specifically with keys provided to subscribers; however it’s worth reading this page: Frequently Asked Questions About Volume License Keys for lot’s of good information about activation. I was able to speak with TechNet technical support to get some answers on product activation, so I’ll summarise here:
- MAK keys provide a set number of activations (in the case of the newer products, TechNet subscribers get 500 activations). This number is not directly related to what you are licensed to install - it’s just a limit on the number of activations per key.
- Activations of MAK keys will count against the total activations whether you are reinstalling on the same hardware or not. The TechNet representative alluded to a current (as at May 2010) issue with activations in virtual environments. I couldn’t get more information on that but I don’t believe that this impacts MAK activations anyway.
- However: if you the VAMT to proxy activate your machines, those machines will use the same activation if you reload and proxy reactivate on the same hardware. When proxy activating you will must store the proxy activation information - if you loose that, you will lose the activations that you have completed.
- MAK keys provided in TechNet (and MSDN subscriptions) are the same as MAK keys provided to Volume License customers. So the same thing applied to where-ever you are using MAK keys.
- Retail keys (like those provided for Office 2010) should reactivate on the same hardware and not count against your total number of activations.
- The good news is that if you run out of activations for a particular MAK key or set of MAK keys, you can contact Microsoft to increase the number of activations as long as you are using those keys for installing products for testing purposes and not production. If you need to increase your activation counts just contact your TechNet Regional Service Centre and they’ll be happy to help.
If you would prefer not to activate Windows, you can do the following:
- Rearm Windows every 30 days, up to 3 times, to extend the pre-activation period to 120 days with the SLMGR –rearm command.
- Create unattended deployments using the Microsoft Deployment Toolkit (or even SCCM) so that you can redeploy Windows to those test machines once the pre-activation period is up. If you can separate the data from the machine, then reinstalling Windows shouldn’t be that much of an issue.
Knowing that I have 500 activations for most of the products that are important to me, then perhaps activation isn’t that much of an issue. I am also fairly certain that when my current subscription expires on Wednesday and my new subscription kicks in, I will get a new set of keys – far more machines than I could get running on a single hypervisor with 12 GB of RAM.
Using the VAMT to track activations and product keys
The Volume Activation Management Tool (VAMT) 2.0 is provided to manage keys and you can use this with TechNet, MSDN or Volume License keys to keep track of machine and key status.
The tool itself is very simple. In the example screenshot below, I have imported a list of machines from Active Directory and this shows the status of machines that I have scanned:
Once machines are imported, I can select a machine or a group of machines and update their status to view the installed products (Windows and Office 2010 will be reported). Remote machines must be powered up to gather their status, unfortunately this information isn’t stored in AD and I can’t scan powered down virtual machines. Product keys can be installed and activated on remote machines directly from the VAMT console.
By importing product keys into the VAMT, you can track the number of activations for MAK and KMS keys (it doesn’t report on Retail keys). This will help you discover the total number of activations you have for each product and keep track of the number of actual activations.
For more information on VAMT and how to use it to management production activation in your environment, see the following links:
- Volume Activation Management Tool (VAMT) 2.0
- Product Activation Using VAMT 2.0
- Manage Activation Using VAMT 2.0
- Manage Product Keys Using VAMT 2.0
- Activation in Disconnected Environments Using VAMT 2.0
- Reporting Activation Information Using VAMT 2.0
It is important to note that even if your TechNet or MSDN subscription expires you should still have access to your keys, and can activate those that you might have saved. It is worth obtaining all of the keys that you are entitled to and exporting them from TechNet well before your subscription expires.
For complete information on Volume Activation, your first port of call should be the Windows Volume Activation site on TechNet.