Windows 7 and Windows Server 2008 R2

Microsoft Corporation
Published: June 2009

Abstract

This guide is for IT pros and developers who use the Windows® 7 and Windows Server® 2008 R2 operating systems in development environments. It describes activation techniques for development environments.

On This Page

Introduction
Developing and Testing Using Volume Licensing Editions
Developing and Testing Using Non–Volume Licensing Editions

Introduction

Product activation is the process of validating software with the manufacturer. Activation confirms the genuine status of a product and that the product key is not compromised. It is analogous to the activation of credit cards or new mobile phones. Activation establishes a relationship between the software’s product key and a particular installation of that software on a device. All editions of the Windows® operating systems require activation; the options available are based on the edition of Windows.

Development and test environments are dynamic. When using physical hardware to test, developers and test engineers frequently reimage their computers to reset the test environments. When using virtualization, they frequently discard their undo disks to reset their test environments quickly. In any case, an incorrect activation configuration can interrupt the development and testing effort, because Windows will remind users about activation regularly. Activation is easy, and you can integrate it in to any development environment. Figure 1 summarizes the activation options for development environments that this guide describes.

Figure 1. Activation in development environments

Developing and Testing Using Volume Licensing Editions

In development and testing environments that use Microsoft® Volume Licensing editions of the Windows 7 or Windows Server® 2008 R2 operating system, take advantage of the grace period. If activation does not occur immediately after installing the operating system, Windows 7 and Windows Server 2008 R2 still provide the full functionality of the operating system for a limited amount of time—30 days for Windows 7 and Windows Server 2008 R2. After the grace period expires, both operating systems remind the user through notifications to activate the computer. The initial 30-day grace period of a computer running Windows 7 or Windows Server 2008 R2 can be reset three times without activating it by running slmgr.vbs -rearm. Therefore, if rebuilding lab computers within 120 days, these computers need not be activated.

If lab computers do require activation, use Key Management Service (KMS) or Multiple Activation Key (MAK) activation. Use KMS activation if the computers have connectivity to a core network that is using KMS. If the lab environment does not have access to the production environment and the number of computers in the lab meets the KMS activation threshold, deploy a local KMS host to the lab environment. Use MAK activation in lab environments that require activation but do have access to the production network and do not quality for KMS activation. MAK clients are activated by telephone or over the Internet—whichever is available to the lab.

MAK Proxy Activation with the Microsoft Volume Activation Management Tool (VAMT) can also be used in a lab scenario. Install VAMT in the isolated lab network and in a network that has access to the Internet. In the isolated lab, VAMT performs discovery, obtains status, installs a MAK product key, and obtains the installation ID (IID) of each computer in the lab. This information can then be exported from VAMT, saved to removable media, and then the file imported to a computer running VAMT that has access to the Internet. VAMT sends the IIDs to Microsoft and obtains the corresponding confirmation IDs (CIDs) needed to complete activation. After exporting this data to removable media, take it to the isolated lab to import the CIDs so that VAMT can complete the activations. For more information about using VAMT, see the Windows Automated Installation Kit (Windows AIK) at http://go.microsoft.com/fwlink/?LinkId=136976 .

If using virtual machines (VMs) in the lab environment, use KMS activation. This will transparently support activation throughout the hardware changes associated with moving or replicating VMs across physical systems. Additionally, using KMS activation in the VM environment seamlessly supports the use of undo disks and other reset operations that could otherwise consume many activations. If conditions require using a MAK for activation, perform the activation after core virtual hardware configurations are complete. For Hyper-V™, apply the Integration Services package. If using another VM manager that supports installation of additional packages on the virtual guest, be sure to apply those. At that point, perform the activation. This process enables fewer reactivations resulting from movement or configuration change with the Virtual guests.

Developing and Testing Using Non–Volume Licensing Editions

In development and testing environments that use retail editions, take advantage of the grace period. For more information about leveraging the grace period, see the section, “Developing and Testing Using Volume Licensing Editions.”

Windows 7 and Windows Server 2008 R2 products acquired through a retail store are individually licensed and are activated in the same way as retail versions of the Windows Vista® and Windows Server 2008 operating systems. Each purchased copy comes with one unique product key, found on the product packaging, which is typed in during the installation of the product. The computer uses this product key to complete the activation after the installation of the operating system is complete. Retail software can be activated either online or by telephone.

In development and testing environments that require activation of retail editions of Windows 7 or Windows Server 2008, perform online activation or telephone activation. The following list describes how to perform telephone activation:

1. Run slmgr.vbs /dti to display the information necessary to complete telephone activation.

2. Run slui.exe 4 to obtain the telephone number for an Activation Call Center in your region.

3. Use the Interactive Voice Response (IVR) system to obtain the CID; then, run slmgr.vbs /atp CID to install the CID. You can store and reuse the CID to reactivate the operating system after rebuilding the computer.