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