The default KMS keys used for volume licensing editions of Windows 8.1 and Windows Server 2012 R2 has been updated.
| Operating system edition | KMS Client Setup Key |
|---|---|
|
Windows 8.1 Professional |
GCRJD-8NW9H-F2CDX-CCM8D-9D6T9 |
|
Windows 8.1 Professional N |
HMCNV-VVBFX-7HMBH-CTY9B-B4FXY |
|
Windows 8.1 Enterprise |
MHF9N-XY6XB-WVXMC-BTDCT-MKKG7 |
|
Windows 8.1 Enterprise N |
TT4HM-HN7YT-62K67-RGRQJ-JFFXW |
|
Windows Server 2012 R2 Server Standard |
D2N9P-3P6X9-2R39C-7RTCD-MDVJX |
|
Windows Server 2012 R2 Datacenter |
W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9 |
|
Windows Server 2012 R2 Essentials |
KNC87-3J2TX-XB4WP-VCPJV-M4FWM |
They can be used as product key when installing the OS in Enter the product key to activate windows:
![clip_image001[4]](http://lh6.ggpht.com/-TZerngc7VL0/Uk62G2fEq_I/AAAAAAAABJc/__cw-3cHBQE/s1600-h/image%25255B29%25255D.png "clip_image001[4]")
And the keys are used by VAMT from the ADK, of course activation will only work if a KMS server is available.
Windows Assessment and Deployment Kit
![clip_image001[6]](http://lh6.ggpht.com/-V0N9oVxgchA/Uk62H3NwIII/AAAAAAAABJs/n9lbpGHYgIM/s1600-h/image%25255B15%25255D.png "clip_image001[6]")
When you choose to automatically install a KMS client key (GVLK), VAMT will use these KMS keys:
![clip_image001[8]](http://lh6.ggpht.com/-s0Rd6i3pc6c/Uk62ItO1zCI/AAAAAAAABKA/53WmwsRhJLU/s1600-h/image%25255B25%25255D.png "clip_image001[8]")
Server changed to KMS key and as shown in partial key the last part is matching the KMS key:
![clip_image001[10]](http://lh6.ggpht.com/-P83SmCQxfYw/Uk62Jp-ZbYI/AAAAAAAABKM/56hLJnkZTms/s1600-h/image%25255B21%25255D.png "clip_image001[10]")
