Windows Activation in Development and Test Environments - Microsoft White paper

Microsoft released a whitepaper ‘Windows Activation in Development and Test Environments’ (embedded below) – provide insights and recommendations to help minimize impact that Windows activation has on development or test environments. Whitepaper begins by providing a high level view of WATs policies and tools, including relationship between Windows activation and Windows licensing[...]Many customer deployment scenarios […]

Microsoft released a whitepaper ‘Windows Activation in Development and Test Environments’ (embedded below) – provide insights and recommendations to help minimize impact that Windows activation has on development or test environments. Whitepaper begins by providing a high level view of WATs policies and tools, including relationship between Windows activation and Windows licensing[...]Many customer deployment scenarios begin with testing on an OS acquired through MSDN subscription (not convered MSDN Academic Alliance), aren’t intended for use outside of development and testing. Because there’re many different options for product editions, product key types and activation methods, focus here's on Windows client and server licenses sold through volume licensing (that use volume activation) includes: Vista, Windows 7, Server 2008, and 2008 R2. VA options for a production environment are KMS or MAK. Following diagram displays various options. If you’re manually installing key, they can be found in Volume Activation Technical Reference Guide for Windows 7 and 2008 R2, and in Volume Activation Deployment Guide for Windows Vista and Windows Server 2008. See Converting Retail Editions to Volume Licensing Activation, and for guidance on activation in a development environment, see embedded doc:
 


Windows Activation in Development and Test Environments

[Source]