#KMS CLIENT FIREWALL SETTINGS HOW TO#
#KMS CLIENT FIREWALL SETTINGS LICENSE KEY#
#KMS CLIENT FIREWALL SETTINGS ACTIVATION KEY#
#KMS CLIENT FIREWALL SETTINGS INSTALL#
#KMS CLIENT FIREWALL SETTINGS WINDOWS 7#

#KMS CLIENT FIREWALL SETTINGS ACTIVATION KEY#

Every KMS supported Windows version automatically communicates with the KMS server to activate Windows and manage the activation key (configuring the Windows OS with a KMS key forces it to find a KMS Host and get activation from it). KMS shifts the activation requirement to a single machine which is activated with a special KMS Host (server) key. Starting with Windows Server 2008 & Windows Vista, Microsoft switched to an online activation system where every Windows OS requires activation. Note: As with Windows 7, and Server 2008 R2, Office 2010 comes with a KMS key already installed, if you have changed the key to a MAK key you can change it back using the Microsoft public KMS keys ( see here).The Microsoft Key Management Server (KMS) is part of the Microsoft Volume Activation 2.0 solution managing Windows OS activation keys and performs activation for supported clients automatically.

#KMS CLIENT FIREWALL SETTINGS LICENSE KEY#

First locate your Office 2010 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 вЂњOffice 2010 Suites and Apps KMSвЂќ

#KMS CLIENT FIREWALL SETTINGS INSTALL#

If you want a KMS Server for JUST OFFICE 2010 and not Windows, then simply install and run the Office 2010 Key Management Service Host.ДЎ. As mentioned above, unlike Windows clients, you only need five requests to the KMS server before it will start activating Office 2010 normally. You simply need to add in Office support, and your Office 2010 KMS key. 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.

#KMS CLIENT FIREWALL SETTINGS HOW TO#

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.

#KMS CLIENT FIREWALL SETTINGS 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.

Kms client firewall settings