How to configure a KMS server in Windows Server 2. R2. Well I have had the pleasure of setting up a KMS server in our environment, and found that the documentation from Microsoft is somewhat confusing. In light of this I will write the steps I used to configure the first KMS server in our organisation for use with Windows Server, Windows client and Microsoft Office activation. These steps will only include the installation of 1 KMS server.
Hi Everyone, Can you please let me know, that can i host KMS Server on windows 7 Enterprise to activate Windows server 2008 and windows server 2012 all version with. We have a problem with the Windows 7 KMS activation on a Dell Optiplex 745. The activation fails due to a missing BIOS feature. This is not a dell issue.
Windows Vista 7-8-8.1-10 Kms Activator Ultimate 2016 1.6. Windows Kms Activator Ultimate,ile sisteminizi lisanslayabilirsiniz, test edildi kesin sonu This is your destination for technical resources, free tools, and expert guidance to ease the deployment and management of your Windows 7 desktop.
Installing first KMS Server. Below are the steps I used to install the KMS server. We determined that due to the number of client activations, and the capacity of our infrastructure we had no problems installing this server on our secondary domain controller. From here on we will call it DC2.
Log onto https: //www. Win Srv 2. 00. 8 R2 Data Ctr/Itan KMS C” – Note your key may be similar, but either way it must end in either KMS B, or KMS C. On DC2 we run CMD with elevation. Type slmgr /ipk xxxxx- xxxxx- xxxxx- xxxxx- xxxxx where the last section is the Key from your volume licensing website. Open “Windows Firewall with Advanced Security” via Start menu - > Administrative Tools.
Under Inbound Rules scroll down to “Key Management Service (TCP- In)”, right click and select enable. Reboot the machine – note you can restart the Software Licensing service but I preferred to reboot it (seeing as the server was not in use for anything else). Activate server after reboot. This can be done via the GUI or by executing the following command from an elevated command prompt. Enables automatic DNS publishing by the KMS host by entering the below command in an elevated command promt.
Note this should already be enabled, but just in case, we execute the command. Office KMS activation will be covered in a later section. I do recommend verifying that the SRV record in DNS is created.
Note that you should have no problems with the automatic creation if you are using the vanilla install of AD and have no specific security restrictions in DNS. To verify that the DNS record has been created open up DNS and check. Refer to the screenshot below to see where it lives: Installing Office KMS Host. As mentioned above we have determined that the one KMS box (DC2) is suitable to do all of our activations for Microsoft products, so now we have to configure the Office KMS host on DC2. To do this we do the following: Log onto https: //www. Office 2. 01. 0 Suites and Apps KMS” – Note your key may be similar. Manual De Procedimientos De Hoteleria. If unsure speak to your Microsoft Account Manager.
Download the Office 2. KMS Host License Pack from the Microsoft website: http: //www. Family. ID=9. 7b. Its only 9. 03kb so wont take too long. Execute Key. Management.
- Anyone having any issues with KMS activation of Windows 10? I have a Windows Server 2012 R2 setup with KMS that is happily servicing Windows 7, 8 and Office KMS.
- 45 thoughts on “ Update Your KMS Service Key To Activate Windows Server 2012 R2 And Windows 8.1 ” Pingback: Windows Server 2012 R2 & Windows 8.1 KMS Service.
- The proper way to license and activate a deployment of Windows 7 on VMware View is to use a KMS. Here's how to set up KMS for VMware View and overcome “composer.
- What are the differences (and maybe pros and cons) of KMS and MAK license activation for Windows 7?
Service. Host. exe from your existing KMS server> In our case its DC2. Follow the prompt to finish the setup process. When prompted enter the KMS key for Office 2. Thats it. Just as easy to setup. Now you are ready to activate Office 2. KMS. To help monitor this, please refer the the section below.
Administering the KMS server. I take it now you want to see whether it works and if clients can be activated.
Now i will go into administering the KMS server, which will be quite brief as there is not much to it, and is really only there to aid in troubleshooting, and to have a sticky beak when implementing it. Once its running there is no real reason to keep going in and checking up on it. All functions to view settings and make changes are done through the already used VBS script slmgr. To see all the commands simply run slmgr from the command prompt. Note to execute changes you will need elevated command prompt. You will see the following screens: So the most common command that i used were: Displays license information (KMS Activation Count)cscript slmgr.
Displays detailed license informationcscript slmgr. For Office specific information you can run the below command to get the info wanted: cscript slmgr. Note I add cscript to the front of the command so that the output stays within the command window, this lets me output/scroll if there is a lot of data where as the usual vbs dialog crops the output.
Configuring KMS Clients. By default, Volume Licensing edition of Windows Vista, Windows 7 , Windows Server 2. Windows Server 2.
R2 are KMS clients. If the computers the organisation wants to activate using KMS are using any of these operating systems and the network allows DNS auto- discovery, no further configuration is needed.
How can I setup KMS (key management server) for activating Windows 1. Setup Server 2. 01. R2. Jump to Step 3 !
If you are using Server 2. R2 please go to step 2.
Step 2. Install a hotfix to add support for activating later versions of Windows. I wasn't prompted to reboot, but you may want to do so anyway. Step 3. Login to the Volume License site. You need to get a new KMS Host key from the Volume License Service Center that is capable of activating Windows 1. To do so, login with adequate credentials and then click License, then Relationship Summary. Click the License ID of your current Active license. You may have more than one Active License, so if it does not appear under one, check the other.
Once the page changes, click Product Keys. Scroll down the list and look for. Windows Srv 2. 01.
R2 Data. Ctr/Std KMS for Windows 1. Save this key somewhere safe, you'll need it later. Step 4. Add the Volume Activation Services role. After installing Windows Server 2. Server Manager and choose Add roles and features, choose Role- Based or Feature- Based installation. Choose your local Windows Server 2.
Server from the Server Pool. Choose the Volume Activation Services role. You may be prompted to add features that are required for Volume Activation Services such as Remote Server Administration Tools, if so, click on Add features and continue through that wizard until completion. Click Close when done, you will see a Yellow Triangle in Server manager which means that the role is installed but there is additional post deployment configuration required. Step 5. Configure the Volume Activation Services role.
To configure it, click VA Services in the left pane. Next click on the More text to the right of Configuration required for Volume Activation Services at SERVERNAME. This will popup All Servers Task Details and Notifications. Volume activation tools link and then decide what Volume Activation Method you want to use in the Select Volume Activation Method screen, use the default (Key Management Service (KMS))on the Product Key Management screen enter your KMS host key retrieved above in Step 3 from the VLSC site. After entering a valid Windows 1.
KMS Host Key, you'll need to commit the change and you'll see that it has been acceptedyou may be prompted to activate the key, click on Activate Productyou can select to Activate Online or by Activate by. Phone and then click on the Commit button,answer Yes when prompted and review the final screen and then continue through that wizard until completion. Step 6. Get the Windows 1. KMS Client Setup keys. The Windows 1. 0 Client KMS keys are available here.
Operating system edition KMS Client Setup Key. Windows 1. 0 Professional W2.
N- WFGWX- YVC9. B- 4. J6. C9- T8. 3GXWindows 1.
Professional N MH3. W- N4. 7XK- V7. XM9- C7. GCQG9. Windows 1. Enterprise NPPR9- FWDCX- D2. C8. J- H8. 72. K- 2.
YT4. 3Windows 1. 0 Enterprise N DPH2. V- TTNVB- 4. X9. Q3- TJR4.
H- KHJW4. Windows 1. Education NW6.
C2- QMPVW- D7. KKK- 3. GKT6- VCFB2. Windows 1. Education N 2. WH4. N- 8. QGBV- H2. JP- CT4. 3Q- MDWWJWindows 1. Enterprise 2. 01.
LTSB WNMTR- 4. C8. 8C- JK8. YV- HQ7. T2- 7. 6DF9. Windows 1. Enterprise 2. 01. LTSB N 2. F7.
B- TNFGY- 6. 9QQF- B8. YKP- D6. 9TJTo test the KMS server configuration, open a cmd prompt as shown below and enterdepending on whether you have less that 2. I'm specifying the kms host manually, you do not need to do that if DNS is working properly.
Find and Update Your KMS Service Host Key To Activate Windows 1. I have done a series of blog post on preparing your KMS environment for Windows 1. You should be set to go but the final step you need to take is update the KMS Service Host Key. But you cannot find and updated KMS Service key right now for Windows Server, that will probably work again when Windows Server 2. RTM. But for now you need to get the key by using a bit of a different path than you. Got to Licenses and select Relationship Summary.
Navigate to the correct license id and click it to open the details of your license. There you select Product Keys. In the list of keys under that license you. They are the keys of clients that activate against a KMS server.
If you have you volume licensing media that. You can read more in my blog Windows 1. KMS Client Setup Keys.
These are found on the Volume License Servicing Center as well when you have a valid license. You also need to have installed an update on your KMS Service hosts. You can read all about that in my blog post KB3. Update that enables Windows 8. Windows 8 KMS hosts to activate Windows 1. Just follow the instructions and you. If you run in to any issues here, restarting the KMS Service can help ((“net stop sppsvc” and “net start sppsvc“) .
Try that first. slmgr. PIRAT- ESARE- NOTGE- TTING- AKEY! Be patient, it. As far as you are concerned this is the Navy .
How to Activate Windows with your KMS Server. If you installed windows with a MAK key and need to change it to KMS or installed windows, never activated, and need to activate it with your KMS server, then here is how to do it. Step 1. Open command prompt on the machine you are wanting to activate and type: slmgr. XXXXX- XXXXX- XXXXX- XXXXX- XXXXX (XXXX is your KMS key in the list below)Step 2. Run this command to activate: Slmgr /ato. Below are the collection of KMS license keys from Microsoft.
They are hard to find on their website. Thankfully edugeek had a nice list. Windows Server 2.
Windows Server 2. Core. BN3. D2- R7.
TKB- 3. YPBD- 8. DRP2- 2. GG4. Windows Server 2. Core N8. N2. M2- HWPGY- 7.
PGT9- HGDD8- GVGGYWindows Server 2. Core Single Language. WN2. H- YGCQR- KFX6. K- CD6. TF- 8. 4YXQWindows Server 2. Core Country Specific.
K3. 6P- JN4. VD- GDC6. V- KDT8. 9- DYFKPWindows Server 2. Server Standard. XC9. B7- NBPP2- 8. 3J2.
H- RHMBY- 9. 2BT4. Windows Server 2. Standard Core. XC9. B7- NBPP2- 8. 3J2.
H- RHMBY- 9. 2BT4. Windows Server 2.
Multi. Point Standard. HM7. DN- YVMH3- 4.
JC3- XYTG7- CYQJJWindows Server 2. Multi. Point Premium. XNH6. W- 2. V9. GX- RGJ4.
K- Y8. X6. F- QGJ2. GWindows Server 2. Datacenter. 48. HP8- DN9.
B- MYWDG- T2. DCC- 8. W8. 3PWindows Server 2. Datacenter Core. 48. HP8- DN9. 8B- MYWDG- T2. DCC- 8. W8. 3PWindows 8. Windows 8 Professional.
NG4. HW- VH2. 6C- 7. KW- K6. F9. 8- J8. CK4. Windows 8 Professional NXCVCF- 2. NXM9- 7. 23. PB- MHCB7- 2. RYQQWindows 8 Enterprise.
JNW- 9. KQ8. 4- P4. T8- D8. GGY- CWCK7. Windows 8 Enterprise NJMNMF- RHW7. P- DMY6. X- RF3. DR- X2.
BQTWindows Server 2. Windows Server 2. R2. Windows Server 2. R2 HPC Edition. FKJQ8- TMCVP- FRMR7- 4.
WR4. 2- 3. JCD7. Windows Server 2. R2 Datacenter. 74. YFP- 3. QFB3- KQT8. W- PMXWJ- 7. M6. 48.
Windows Server 2. R2 Enterprise. 48. J6- VHDMP- X6. 3PK- 3. K7. 98- CPX3. YWindows Server 2. R2 for Itanium- Based Systems. GT6. 3C- RJFQ3- 4. GMB6- BRFB9- CB8.
VWindows Server 2. R2 Standard. YC6. KT- GKW9. T- YTKYR- T4. X3. 4- R7. VHCWindows Web Server 2. R2. 6TPJF- RBVHG- WBW2.
R- 8. 6QPH- 6. RTM4. Windows Server 2. Datacenter. 7M6. 7G- PC3.
GR7. 42- YH8. V4- TCBY3. Windows Server 2. Datacenter without Hyper- V2. XQ2- VRXRG- P8. D4. K3. 4TD- G3. QQCWindows Server 2.
Itanium- Based Systems. DWFP- JF3. DJ- B7.
DTH- 7. 8FJB- PDRHKWindows Server 2. Enterprise. YQGMW- MPWTJ- 3. KDK- 4. 8M3. W- X4.
Q6. VWindows Server 2. Enterprise without Hyper- V3. BXF- X8. Q2. 3- P2.
WWT- 3. 8T2. F- G3. FPGWindows Server 2. Standard. TM2. 4T- X9. RMF- VWXK6- X8. JC9- BFGM2. Windows Server 2. Standard without Hyper- VW7. VD6- 7. JFBR- RX2.
B- YKQ3. Y- 6. FFFJWindows Web Server 2. WYR2. 8- R7. TFJ- 3. X2. YQ- YCY4. H- M2. DWindows 7. Windows 7 Professional. FJ8. 2H- XT6. CR- J8.
D7. P- XQJJ2- GPDD4. Windows 7 Professional NMRPKT- YTG2.
K7. D7. T- X2. JMM- QY7. MGWindows 7 Enterprise. PXH- 7. Y6. KF- 2.
VJC9- XBBR8- HVTHHWindows 7 Enterprise NYDRBP- 3. D8. 3W- TY2. 6F- D4. B2- XCKRJWindows 7 Enterprise EC2. WB- 2. 2CC8- VJ3. GHFJW- H9. DH4. Vista. Windows Vista Business. YFKBB- PQJJV- G9.
G- VWGXY- 2. V3. X8. Windows Vista Business NHMBQG- 8.
H2. RH- C7. 7VX- 2. R8. 2- VMQBTWindows Vista Enterprise. VKK3. X- 6. 8KWM- X2.
YGT- QR4. M6- 4. BWMVWindows Vista Enterprise NVTC4. BM8. 38- 4. 3QHV- 8.