Test Lab Guide: Demonstrate Volume Activation Services
Updated: June 1, 2012
Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2
This test lab guide describes the steps for configuring the Volume Activation Services server role in a Windows Server 2012 demonstration or test environment. Although the same steps can be used to deploy Volume Activation Services in a production environment, additional planning would be needed to ensure that your Volume Activation Services deployment meets the needs of your environment.
The following steps are needed to set up Volume Activation Services in a Windows Server 2012 test lab:
Step 1: Set up the base test lab configuration
Step 2: Install the Volume Activation Services server role
Step 3: Configure Active Directory-based Activation
Step 4: Verify that Active Directory-based Activation works
Step 5: Configure Key Management Services (KMS)
Step 6: Verify that KMS volume activation works
Test labs enable you to get valuable hands-on experience with new products and technologies. The following base test lab configuration uses a predefined and tested methodology that results in a working configuration. The following instructions define what servers to create, how to configure the operating systems and system services, and how to install and configure additional products or technologies. This enables you to see all of the front-end and back-end components that are required for a product or technology, such as Volume Activation Services, or for a multiproduct or technology solution.
To prepare a base test lab infrastructure
Create the base configuration test lab as described in the following document: Test Lab Guide: Base Configuration (http://go.microsoft.com/fwlink/?LinkId=236358). The base configuration test lab contains the following computers:
DC1 A domain controller running Windows Server 2012.
AD DS must be at the Windows Server 2012 schema level to store activation objects. Domain controllers running earlier versions of Windows Server can activate clients after their schemas have been updated using the Windows Server 2012 version of Adprep.exe. For more information, see Running Adprep.exe.A new installation of Windows Server 2012 and AD DS with the configuration settings that are described in the base configuration test lab guide will be at the Windows Server 2012 schema level.
APP1 A computer running Windows Server 2012 that can be configured as a Key Management Service host.
CLIENT1 A computer running Windows 8 or Windows Server 2012 to serve as a volume licensing client for Active Directory-based Activation.
CLIENT2 (optional) A computer running Windows 7 or Windows Server 2008 R2 that is added to the base configuration to test Active Directory-based Activation and KMS activation at the same time.
Configuration of CLIENT2 is not covered in the base configuration test lab guide.
Complete all the network configuration tasks for the base test lab.
Local administrator permissions are needed on all computers in this configuration to complete these setup steps. Enterprise admin permissions are needed to manage or modify Active Directory Domain Services on DC1.
The Volume Activation server role can be installed by using Windows Server Manager, Windows PowerShell DISM cmdlets, or Windows PowerShell ServerManager cmdlets.
To install Volume Activation Services by using Server Manager:
On either server running Windows Server 2012, open Windows Server Manager
Click Manage, click Add Roles and Features, and then click Next.
On the Select installation type page, select Role-based or Feature-based installation, and then click Next.
On the Select destination server page, select DC1 from the SERVER POOL, and then click Next.
On the Select server roles page, select Volume Activation Services, and then click Next three times.
On the Confirm installation selections page, confirm that the information is correct, then click Install.
On the Installation progress page, wait until the progress indicator shows that the installation was successful. Because additional configuration is required, click the Volume Activation Tools link. At this point, move to Steps 3 or 5 later in this document to configure either KMS-based volume activation or Active Directory-based Activation.
To install the Volume Activation Services by using the DISM cmdlets
To import the DISM cmdlets, open a Command Prompt window, type import-module dism, and then press ENTER.
Open a Windows PowerShell console and at the command prompt, type the following command, then press ENTER: enable-windowsoptionalfeature -online -featurename VolumeActivation-Full-Role
To install the Volume Activation Services by using the ServerManager cmdlets
To import the ServerManager cmdlets, open a Command Prompt window and type: import-module servermanager
Open a Windows PowerShell console and at the command prompt, type the following command, then press ENTER: Install-WindowsFeature VolumeActivation
To configure Active Directory-based Activation
On DC1, open Server Manager, select Tools, and then click Volume Activation Tools.
On the Select Volume Activation Method page, select Active Directory-based Activation. If the account you are currently using does not have enterprise administrator permissions, enter the credentials for an account that has permissions to create a new container on the domain controller, and then click Next.
Enter the KMS host key and an optional name for the Active Directory object, and then click Next.
Although license data is presented in English, the optional name option supports the Unicode character set, which enables you to more easily identify each volume license key in any language.
Activate the key online or by phone, and then click Commit. If you have no other changes, click Close.
After the KMS host key has been activated, client computers that are joined to a domain running Windows Server 2012 or Windows 8 with generic volume license keys (GVLKs) installed will automatically activate without user intervention.
All Active Directory-based Activation events are logged to the Windows Application event log under the Source: Microsoft-Windows-Security-SPP. Look at Event 12308 for confirming information.
With clients running Windows Server 2012 or Windows 8, activation should occur automatically the next time the computer is started and the user logs on.
If you set up multiple domain controllers, replication between domain controllers must be complete before clients can access this data. Therefore, in a production environment, you might need to wait until replication is complete before you start the client system and the user logs on to complete Active Directory-based Activation.
To verify that Active Directory-based Activation works
Log on to CLIENT1.
Open Windows Explorer, right-click Computer, and select Properties.
Scroll down to the Windows activation section and verify that this client has been activated.
Active Directory-based Activation will not work for operating systems earlier than Windows Server 2012 or Windows 8. It also will not work with Microsoft Office 2010. Use KMS volume activation to activate Windows clients and applications that do not support Active Directory-based Activation.
In earlier versions of Windows, Key Management Services (KMS) could be installed only from the command line. The following procedure describes how to complete this task by using the Volume Activation Tools console in Windows Server 2012.
To configure KMS
On DC1, open the Volume Activation Tools console.
If you did not open the console when you completed the server role installation in Step 2, open Server Manager, click Volume Activation Services, right-click the name of the server on which you installed the server role, and then select Volume Activation Tools. When the Volume Activation Tools console is open, click Next.
Select Key Management Service (KMS) and select APP1 as the server that you want to install KMS on.
If the account you are using does not have administrator permissions on APP1, enter the User name and Password for an account that does in the boxes, and then click Alternate credentials (optional).
After you have completed both tasks, click Next.
On the Manage KMS Host page, enter your KMS host key, and then click Commit.
On the Product Key Installation Succeeded page, click Activate Products, and then click Next.
Activate your key online or by phone, and then click Next.
On the Configure Key Management Service options page, review the default configuration options, click Commit, and then click Close if you have no other changes.
Administrators should validate the firewall configurations in their environment to ensure that the appropriate exceptions are enabled for KMS traffic. If you need to change the firewall or other default options at a later date, you can open the Volume Activation Tools console and return to this dialog box at any time to modify the configuration.
You can verify KMS volume activation from the KMS host server, APP1 and from the client computer, CLIENT2.
If you set up and configured Active Directory-based Activation before configuring KMS activation, you must use a client computer that is not running Windows 8 or Windows Server 2012to verify that KMS activation works. Otherwise, the activation will be complete before your clients contact the server that is hosting KMS.
KMS volume activation requires a minimum threshold of 25 computers before activation quests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host. However, unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.
To verify that KMS volume activation works
On APP1, open the event log and confirm that DNS publishing is successful.
On CLIENT2, open a Command Prompt window, type Slmgr.vbs /ato, and then press ENTER. The response should show the license state and detailed Windows version information.
On either CLIENT2 or APP1, open an elevated Command Prompt window, type Slmgr /dlv, and then press ENTER. The response should return an error that states the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.
For more information about Volume Activation Services, see the Volume Activation Overview.
For more information that can help you prepare to deploy Volume Activation Services in your organization, see Plan for Volume Activation.
For more information about Microsoft test lab guides, see Test Lab Guides on the Microsoft TechNet Wiki.
To provide the authors of this guide with feedback or suggestions for improvement, send an email message to email@example.com.