How to set up a KMS server


To do this for Windows 7 and server 2008R2 you need to do the following
·         Pick a 2008 R2 server
·         Apply the 2008 R2 KMS licence key for the server (see below for which one). Do not under any circumstances apply any other licence key.
·         To apply the key type the following at an Admin command prompt
o   slmgr.vbs -ipk <KMS key>
That’s should be it

For Office 2010 do the following
1.       Download and run the KeyManagementServiceHost.exe file on this page on a supported operating system. (\\codms-1\Apps\Office 2010)
2.       Enter your Office 2010 KMS host key when prompted.
3.       Click OK to continue with activation.
4.       Open port 1688 and allow the KMS host service through the firewall.
a.       Windows 7 volume editions or Windows Server 2008 R2.
                                                               i.      Open Control Panel and click on the Windows Firewall icon.
                                                             ii.      Click on the “Allow a program through Windows Firewall” link.
                                                            iii.      Click on the Change Settings button.
                                                           iv.      Check the box for Key Management Service.
5.       Read the documentation to learn more about configuring your KMS host (including activation by telephone) with slmgr.vbs at TechNet.

That’s it. If you want to view what is going on you can install VAMT 2. This is a clunky piece of software but you can use it to manage and change license keys in use for 2008/R2 Vista/Win7 and Office 2010 and check what is licensed and what isn’t. You can run it on your PC if required rather than the server which may be preferable, though it doesn’t like having more than one network card.

NOTE:
All installs of Windows and office 2010 that are to use the KMS server to authenticate need to have the out of the box licence key, no other key should be applied to them. If you have the put another key on the image you need to revert it to the OOB one. To do this apply one of the following key as appropriate to the server or Client PC. All PCs in the company should be running Windows 7 Enterprise, Windows 7 Pro is incorrect and those PCs should be rebuilt with the correct license, Appling the correct licence may be sufficient to “Upgrade” them.

Platform
Operating system edition
Product key
Windows 7 and Windows Server 2008 R2
Client
Windows 7 Professional
FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Client
Windows 7 Professional N
MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Client
Windows 7 Professional E
W82YF-2Q76Y-63HXB-FGJG9-GF7QX
Client
Windows 7 Enterprise
33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Client
Windows 7 Enterprise N
YDRBP-3D83W-TY26F-D46B2-XCKRJ
Client
Windows 7 Enterprise E
C29WB-22CC8-VJ326-GHFJW-H9DH4
Server
Windows Server 2008 R2 Web
6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Server
Windows Server 2008 R2 HPC edition
TT8MH-CG224-D3D7Q-498W2-9QCTX
Server
Windows Server 2008 R2 Standard
YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Server
Windows Server 2008 R2 Enterprise
489J6-VHDMP-X63PK-3K798-CPX3Y
Server
Windows Server 2008 R2 Datacenter
74YFP-3QFB3-KQT8W-PMXWJ-7M648
Server
Windows Server 2008 R2 for Itanium-based Systems
GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Vista and Windows Server 2008
Client
Windows Vista Business
YFKBB-PQJJV-G996G-VWGXY-2V3X8
Client
Windows Vista Business N
HMBQG-8H2RH-C77VX-27R82-VMQBT
Client
Windows Vista Enterprise
VKK3X-68KWM-X2YGT-QR4M6-4BWMV
Client
Windows Vista Enterprise N
VTC42-BM838-43QHV-84HX6-XJXKV
Server
Windows Web Server 2008
WYR28-R7TFJ-3X2YQ-YCY4H-M249D
Server
Windows Server 2008 Standard
TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Server
Windows Server 2008 Standard without Hyper-V
W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
Server
Windows Server 2008 Enterprise
YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Server
Windows Server 2008 Enterprise without Hyper-V
39BXF-X8Q23-P2WWT-38T2F-G3FPG
Server
Windows Server 2008 HPC
RCTX3-KWVHP-BR6TB-RB6DM-6X7HP
Server
Windows Server 2008 Datacenter
7M67G-PC374-GR742-YH8V4-TCBY3
Server
Windows Server 2008 Datacenter without Hyper-V
22XQ2-VRXRG-P8D42-K34TD-G3QQC
Server
Windows Server 2008 for Itanium-Based Systems
4DWFP-JF3DJ-B7DTH-78FJB-PDRHK


Which keys to use?
KMS uses a heirarchical structure so you have to apply the key to the server that corresponds to the highest level you wish to authenticate, for example if you wish to authenticate Server std and windows 7 you would use the KMS B key, if you wish to go up to Datacentre you need to apply the KMS C, you apply this key no matter what level of OS you install the software on.
I would recommend that you install the KMS C key if you have access to one as it will do everything.

Volume product group
Windows products
Key type
Products activated by key type
Windows Vista
Windows Vista Business
Windows Vista Enterprise
KMS
Windows Vista Business
Windows Vista Enterprise
Windows 7
Windows 7 Professional
Windows 7 Enterprise
KMS
Windows Vista Business
Windows Vista Enterprise
Windows 7 Professional
Windows 7 Enterprise
Windows Server 2008 R2
Server Group A:
Windows Web Server® 2008 R2
Windows Server 2008 R2 HPC Edition
Windows HPC Server 2008 R2
KMS_A
Windows Server 2008 R2 Group A
Windows Server 2008 Group A
Windows Vista Volume Editions
Windows 7 Volume Editions
Windows Server 2008 R2
Server Group B
Windows Server 2008 R2 Standard
Windows Server 2008 R2 Enterprise
KMS_B
Windows Server 2008 R2 Group A
Windows Server 2008 Group A
Windows Server 2008 R2 Group B
Windows Server 2008 Group B
Windows Vista Volume Editions
Windows 7 Volume Editions
Windows Server 2008 R2
Server Group C
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 for Itanium-Based Systems
KMS_C
Windows Server 2008 R2 Group A
Windows Server 2008 Group A
Windows Server 2008 R2 Group B
Windows Server 2008 Group B
Windows Server 2008 R2 Group C
Windows Server 2008 Group C
Windows Vista Volume Editions
Windows 7 Volume Editions

Comments

Post a Comment

Popular posts from this blog

Scripting DNS entries

For reasons to do with DR we needed to change our IP addressing scheme, either for our servers or for our PCs and printers and what not. Obviously changing PCs and printers was a whole lot easier due to the possible issues of inept developers’ hard coding IP addresses causing no end of problems with re-addressing the servers. This has entailed changing all the DNS entries for our printers, (whatever happened to the paperless office?) That in itself is no real challenge, they all have web interfaces so a quick connect and amend the setting then next printer. Updating the DNS entries was going to be a bit tiresome so I did a quick Google on how to do this with a script and up popped DNSCMD. You can run this from a CMD box on your PC, the main options you need to know are /recorddelete and /recordadd. To delete a record you simple need to type dnscmd <ServerName> /recorddelete <ZoneName> <NodeName> <RRType> <RRData>[/f] What does all that mean? Well i
Read more

Enterprise Vault - Failed Exchange Task

Here's another weird one. Enterprise Vault, we use this for e-mail archiving. It does a reasonable job. Probably no better or worse than any similar product. A couple of days ago I noticed that there was warning that it hadn't archived anything from one of our mailbox servers for a couple of days, not big issue as there is just a couple mailboxes on there as it used for testing at the moment. I had a look at the associated task and it was stopped. Started it and it failed. Error in the event log looked something like below The Task 'Exchange Mailbox Archiving Task for EXCH' failed to log on to Exchange server 'EXCH' using mailbox 'SMTP:EnterpriseVault@symantec.local'. Please ensure the mailbox has not been hidden, that the server is running and that the Vault account has sufficient permissions on the server. I went through every conceivable setting in AD, EV and Exchange trying to work out what had happened and why it wasn't working on thi
Read more

Windows Phone to iPhone - a painful transition

Windows Phone died a death due to a whole heap of incompetence from Microsoft.  My phone was an old Nokia 925, about 4 1/2 years old and bought and paid by my company. There were always low requirements for company phones, if it rung and you answered it, all was good. Then Hangouts reared its head (Google want to destroy MS, so WP support) but third-party support gave a stay of execution. The final nail was a requirement for out of hours support software that had no app for Windows Phone. I had to be “downgraded” to an iPhone 6s (yes, it is a low spec 2 version old iPhone, better hardware than my 925 but not really up there as a current version, how my company loves their staff, buy expensive crap rather than cheap crap). Stuff that just worked on my old phone, now needs 'me' to be re-engineered to work the Apple way.  This is only slightly less bad than the Google eat all your life and sell it back to you way, but it is like stepping back in to the 1990s Microsoft way
Read more