In addition to servers and clients, KMS can activate and handle Office 2010 licenses as well. Managing License States Adding an Office 2010 KMS Key to Your KMS Server.
How to troubleshoot the Key Management Service (KMS) From your client machines you can test that they can see the SRV record, by running the following command įor further troubleshooting, see the following links. To allow the service, Start > Firewall.cpl > _tcp > You will see an entry for _VLMCS that points to your KMS Server.Ģ. If you do NOT then you need to allow access through the local firewall for the “Key Management Service”, (this runs over TCP port 1688).
In a corporate environment (behind an edge firewall) you may have the local firewall disabled on the server. You may now need to activate your copy of Windows with Microsoft, this is done as normal, if you can’t get it to work over the internet you can choose to do it over the phone.Ĥ. You will receive a warning that you are using a KMS Key > OK. Select “Change Product Key” > Enter the new KMS Key > Next.ģ. Start > Right Click “Computer” > Properties. Armed with your new key, you simply need to change the product key on the server that will be the KMS server, to the new key. (You DO for Office 2010, but I’ll cover that below).Ģ.
You do NOT need to add additional keys for Windows 7. Note: To License/Activate Server 2008 R2 AND Windows 7 THIS IS THE ONLY KEY YOU NEED.
The most difficult part is locating your KMS Key! If you have a Microsoft License agreement, log into the the Microsoft Volume License Service Center, and retrieve the KMS License Key for “Windows Server 2008 Std/Ent KMS B”
Install Microsoft Windows 2008 R2 Key Management Service (EASY)ġ. Then how to test it, and finally how to add Microsoft Office 2010 Licenses to the KMS Server. In addition, after that I’ve outlined how to deploy KMS from command line. I’ve gone into a fair bit of detail below but most of you will simply need to follow steps 1-4 (immediately below). To be honest it’s more difficult to find out how to deploy a KMS server, than it actually is to do. Note: If you are using Server 2003 it will need SP1 (at least) and this update. I will also add in the licensing KMS mechanism for Office 2010 as well. I’m deploying KMS on Windows Server 2008 R2, and it is for the licensing and activation of Serer 2008 R2 and Windows 7. So after activating a dozen servers over the phone, I decided enough was enough “I’m putting in a KMS Server!” Unfortunately the “Administrators” of this proxy server were not disposed to give me any help, or let me anywhere near it, to fix it. Their internet access is through a proxy server, that refuses to let Windows activation work. However these last few weeks I’ve been putting in a new infrastructure for a local secondary school. Like most technical types, I find a way that works for me, and that’s the way I do things from then on. Given the amount of deployments I do, it’s surprising that I don’t use KMS more often.