KMS Server on WIndows 2008 r2


I want to be able to install a KMS server on a Windows 2008 r2 server. I know you need 5 servers to be able to start activation and 30 Vista or Windows 7. I have that number, but they're already activated via the MAC code.

Can I change enough of these to get the KMS up and running? Also, can KMS run on 2008 r2?

Best wishes

Who is Participating?
you will have to choose a kms key that can activate all of the os;s in you enviuronment:
See this link for more information:

Choosing the KMS Key
With KMS, product keys are associated with a product group and can activate the Windows editions within that specific product group as well as any editions below it in the product hierarchy. The first and least-inclusive group of the hierarchy is the Client Volume Licensing product group; Server Group C is the most inclusive group in the KMS hierarchy.

This hierarchy extends to Windows Vista and Windows Server 2008 Volume License editions and product key groupings. Separate KMS keys will be issued for each product key grouping, meaning that a customer will have access to a KMS key for Client VL for both Windows 7 and Windows Vista. The KMS key for the newer Windows products will also activate the previous generation, meaning that a customer can have a single KMS key to activate multiple editions and generations of Windows. Table 4 shows the correlation between the product groupings.

Table 4. Product Group Correlation

Volume License product key group
 Windows edition

(Windows 7 and Windows Server 2008 R2)
 Windows edition

(Windows Vista and Windows Server 2008)
Client VL
 Windows 7 Professional

Windows 7 Enterprise
 Windows Vista Business

Windows Vista Enterprise
Server Group A
 Windows Web Server 2008 R2

Windows Server 2008 R2 HPC Edition

Windows HPC Server 2008 R2
 Windows Web Server 2008

Windows Compute Cluster Server 2008
Server Group B
 Windows Server 2008 R2 Standard

Windows Server 2008 R2 Enterprise
 Windows Server 2008 Standard

Windows Server 2008 Enterprise

Includes editions without
Server Group C
 Windows Server 2008 R2 Datacenter

Windows Server 2008 R2 for Itanium-based Systems
 Windows Server 2008 Datacenter

Windows Server 2008 for Itanium-Based Systems

Includes editions without
yes KMS can run on Windows 2008 R2.

Installing KMS Hosts
To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsofts activation services. Computers running Windows 7 or Windows Server 2008 R2 can both serve as KMS hosts.

Windows Vista, Windows Server 2003, and Windows Server 2008 can also serve as KMS hosts. The KMS clients that a KMS host can activate are dependent on the host key used to activate the KMS host. For more information about KMS host keys, see the Volume Activation Planning Guide.

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

yes, you can convert the MAK codes on the already activated clients (and server) to KMS...

Converting MAK Clients to KMS and KMS Clients to MAK
By default, Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. To change existing KMS clients to MAK clients, simply install a MAK key. Similarly, to change MAK clients to KMS clients, run:

slmgr.vbs /ipk <KmsSetupKey>

Manually Specifying a KMS Host
Administrators can manually assign a KMS host to KMS clients by using KMS host caching. Manually assigning a KMS host disables auto-discovery of KMS on the KMS client. A KMS host is manually assigned to a KMS client by running:

Copy Code
slmgr.vbs /skms <value>:<port>
where value is either the KMS_FQDN, IPv4Address, or NetbiosName of the KMS host and port is TCP port on the KMS host.

Manually Activate a KMS Client

By default, KMS clients automatically attempt to activate themselves at preset intervals. To manually activate KMS clients (for example, disconnected clients) before distributing them to users, use the Control Panel System item, or run slmgr.vbs /ato at an elevated command prompt. The Slmgr.vbs script reports activation success or failure and provides a result code. To perform activation, the KMS client must have access to a KMS host on the organizations network.


proximityworldAuthor Commented:
Thanks for the replies. So if I use the commands above with my Windows 2008 r2 KMS key I am all set and I have a KMS server. What about Vista and Windows 7 clients? Do I have add KMS keys to the server as well?

I appreciate the feedback.

Best wishes

oh...and good luck... you may have to call you microsoft volume manager to get some assistance to pick the right key.
Your question was how to convert MAK activation to back to default KMS, That’s mean that client is normal KMS client again ready to get activation number from Installed and activated KMS host:

Already installed and activated KMS host somewhere on network.

1. You have to get default keys for default KMS clients: (section KMS Client Setup Keys)
2. convert  MAC  to default KMS per OS with command slmgr.vbs /ipk <KmsSetupKey>
3. Run slmgr.vbs /ato to activate back default KMS client

If your number is under 5 W2008 servers or 25 Vista/W7 you will get error on clients regarding numbers
When you will be on threshold, all system will be activated.

You will immediately find event ID 12290 in Key Management Service log in the Applications and Services Logs folder on KMS host server.  The Key Management Service log records activation requests from KMS clients. Each event displays the name of the computer and the time stamp of each activation request.

Regards Ales
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.