Applies to: Windows 7, Windows Server 2008 R2
In this section are articles that give more in depth technical information on a specific topic.
As part of deployment, many enterprise customers set up the Key Management Service (KMS) to enable activation of Windows in their environment. It is a simple process to set up the KMS host…and the KMS clients discover and attempt to activate on their own. But what happens if it doesn’t work? What do you do next?
This document is aimed at helping all who need to know 1) how Windows Volume License product keys are organized, and 2) how to choose the right one, based on the individual organization’s deployment.
Sometimes it can be challenging to keep track of product keys and prevent their leakage to unauthorized personnel. VAMT 2.0 enables you to manage and protect the following product key types, regardless of how your organization obtained them: Multiple Activation Key keys (MAK), Key Management Service (KMS) host keys, and retail keys.
VAMT 2.0 is an important tool that helps customers automate and centrally manage a range of activities related to Windows and Office 2010 activation. We cover several scenarios using VAMT to perform MAK, KMS host, KMS client, and retail activations.
We often hear from customers asking about tools they can use to track and report activation data for Windows operating systems activated using Key Management Service (KMS) or Multiple Activation Key (MAK). VAMT 2.0 can help you monitor activation information, including retail activations.
We provide a step-by-step walk through of how to use proxy activation with VAMT 2.0 to activate systems in disconnected environments, e.g., branch offices and high-security zones within a production environment. In our example we use MAKs, but you can also activate a Key Management Service (KMS) host or retail systems using product keys obtained through various programs such as volume licensing, MSDN and Microsoft Partner Network, using this process.