Monday, October 26, 2009

Windows 7 Activation Issues

Now that Windows 7 is finally released to the public, it's time to start looking into all of the potential activation issues (among other things) that users are running into. The one issue in particular that I encountered was with activating the Enterprise edition of the software against a KMS (Key Management Server). If you have been running Vista in your organization using KMS Licensing (the replacement for Volume Licensing, if you will), then you are more than likely familiar with what I am talking about. If this is your first run-in with the new licensing system, then you may be in for a bit of frustration.

What is KMS (Key Management Server)


Starting with Windows Vista, Microsoft introduced a new model for enterprise licensing in large organizations. Previously, MS had provided the organization with a single license key which would be valid for x number of clients. While this model was relatively pain free and easy to implement, it caused problems in terms of software piracy, exceeding the available number of licenses, etc. So Microsoft came up with the idea of the Key Management Server (KMS). With this model, you still get your volume license key, but it is installed on a server within your domain. When the server is initialized, it creates SVR records in your domain's DNS servers that tell machines where to go for activation. This means that computers no longer have to phone home to Microsoft to activate. They simply contact the KMS within the company's domain. And providing that the organization protects the master key (MAK), users who are not on the domain will not be able to activate their machines, thereby preventing software piracy.

I have a MAK key, now what?


If you have the volume license key or MAK key for your software or operating system, there are a couple of ways that you can set up the activation server. Microsoft recommends setting the server up on a Domain Controller or DNS server within your network. This provides a good centralized location within your network for the KMS server to function. Another option is to simply set the KMS server up on the device that you are attempting to activate. Although this is far from ideal, it was originally needed when Vista was first released as they did not enable the software on Windows Server 2003 at the time of release. Users had to perform a workaround to get their OSes to activate, and that workaround was to run the KMS service locally or on another Vista computer within the domain. NOTE: If you wish to install the KMS on a Windows Server 2003 box, you will need to download the Key Management Service Package for Windows Server 2003.


How do I enable the KMS server?


The KMS server is relatively easy to initialize. You simply type a couple of commands at the command prompt on the machine where you want to install it and it's ready to go. The following steps will get you up and running with a KMS Server on your domain.


  1. Obtain an original KMS key (MAK Key) from Microsoft Volume Licensing Services.

  2. Download and install the appropriate Key Manager Service package if you plan to install the KMS on Windows Server 2003 (see links above).

  3. Open an command prompt with elevated privileges (right click and select "run as administrator" on Windows Server 2008. On Windows Server 2003, just log on as an account with administrator privileges).

  4. Type the following command followed by the Enter key to install the KMS key:

    cscript C:\windows\system32\slmgr.vbs -ipk <MAK key>

  5. Type the following command followed by the Enter key to activate the KMS server host:

    cscript C:\windows\system32\slmgr.vbs -ato



At this point, the KMS server configuration is complete. The KMS host will automatically publish its SRV records in the domain's DNS servers (If you have third party DNS servers such as Bind on your network, you may need to manually enter the SRV records). All Windows Vista machines should now automatically use DNS auto discovery to detect the KMS host and activate. Another thing to note is that all machines attempting to activate will need to be connected to the organization's network. Laptops, for example, will not be able to activate from home without first being connected via VPN to your corporate network.

For computer and other tech product reviews be sure to visit TechDealsGalore.com.

No comments: