Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows Server 2012 R2 / Installing KMS Server on Windows Server 2012 R2

April 11, 2018 Windows Server 2012 R2

Installing KMS Server on Windows Server 2012 R2

Own KMS server allows you to significantly simplify the process of activating Microsoft products on the corporate network and in contrast to a usual the activation process doesn’t require granting each computer an access to the Internet to Microsoft activation servers. KMS infrastructure is rather simple, reliable and easily scalable (a single KMS server can serve thousands of clients).

In this article, we describe how to install and activate the KMS server on Windows Server 2012 R2 on the local corporate network.

The main aspects of the functioning of KMS technology, which is widely used for Microsoft products activation, are described in detail in the article KMS Activation FAQ .

Contents:
  • Installation and Configuration of the Volume Activation Services Role
  • Using Windows 2012 R2 KMS for Activation of Volume-Licensed Systems

Installation and Configuration of the Volume Activation Services Role

KMS requires installation and configuration of a separate server role – Volume Activation Services. You can install this role using the Server Manage console or PowerShell:
Install-WindowsFeature -Name VolumeActivation -IncludeAllSubFeature
If you are going to install a role through the graphical interface of the Server Manager console, run the Add Roles and Features Wizard, and in the Server Roles selection step, select Volume Activation Services.

Install Volume Activation Services role in Windows Server 2012 R2

After the installation is complete, start Volume Activation Tools console. The activation service installation wizard will start. Specify that you are going to install Key Management Service (KMS) server.

Note. If all Windows OSs activated on this KMS server are in the same Active Directory domain and you are using not older than Windows 8 / Windows Server 2012 operating systems – you can use the special extension of KMS technology – Active Directory Based Activation (activation via AD).

install key managment service win 2012 r2

Note. The account under which the KMS server is configured must have Enterprise Admin privileges.

Next you need to obtain your corporate KMS key (KMS host key – this is the KMS server activation key) in your personal section on Microsoft website (https://www.microsoft.com/Licensing/servicecenter/home.aspx). You can find it in the section Downloads and Keys –> Windows Server –> Windows Server 2012 R2.

get gvlk key for kms service at Microsoft Site

Find the key with type KMS (not MAK) and copy it to the clipboard.

Paste the copied KMS host key in the corresponding field of the installation wizard (Install your KMS host key).

install kms key

If the system accepts the key, you will immediately be prompted to activate it. Based on the entered key, the system will determine the product to which it applies, and will offer two options for activation (by phone or Internet). In the second case, you will have to give the server temporary access to the Internet (only for the activation time).

activating of kms server

After the key is activated, you have to configure Key Management Service options: activation and renewal intervals (by default, the clients will renew the activation every 7 days), port (by default, KMS listens on port 1688) and Windows Firewall exceptions. To automatically create a DNS record necessary to automatically search a KMS server in the domain (SRV record _vlmcs._tcp), check the option DNS Records – Publish.

If the KMS server is designed to serve clients from different domains, you can publish DNS records in other DNS zones. Specify the zone names in the Publish to Custom DNS zones list.

publicate kms server in dns

Note. If you have Windows Firewall enabled, make sure that the rule that allows incoming connections to port 1688 is active. If there is no active rule, enable it via PowerShell:

Get-NetFirewallRule -DisplayName *key*
Enable-NetFirewallRule -Name SPPSVC-In-TCP

firewall kms rule SPPSVC-In-TCP (1688)

Using Windows 2012 R2 KMS for Activation of Volume-Licensed Systems

Now the configuration is over. Verify that a special DNS record pointing to your KMS server was created:
nslookup -type=srv _vlmcs._tcp.corp.woshub.com
Then get the information about the KMS server current status:
slmgr.vbs /dlv
check kms server status

Pay attention to the following fields:

  • Partial Product Key – the last 5 symbols of the KMS key are shown.
  • License status – license activation status (it should be Licensed).
  • Total requests received – the number of activation requests (0 yet).
Tip. Remember that a KMS server has so called activation threshold counter. It means that an activated KMS server starts to activate clients only when the number of clients that addressed it in the last 30 days exceeds the pre-defined thresholds:

  1. The activation threshold for client operating systems: Vista / Windows 7 / Windows 8 / Windows 10 is 25 clients;
  2. In case of server operating systems: Windows Server 2008/ 2008 R2 / 2012 / 2012 R2 / 2016 it is 5 clients.

Now the KMS server can activate clients. To successfully activate your systems on the KMS server, you need to perform a number of actions on the client side:

  1. Specify the public KMS (GVLK) key from the corresponding edition of Windows on the client (links below):slmgr /ipk xxxxx- xxxxx - xxxxx - xxxxx – xxxxx
  2. If your KMS server is not published in DNS, specify it address manually: slmgr /skms kms-sr1.woshub.com:1688
  3. Activate the OS with the command: slmgr /ato

The KMS server that is activated with the KMS host key for Windows Server 2012 R2 (VOLUME_KMS_WS12_R2 channel) supports the activation of all Windows operating systems up to Windows 8.1 / Windows Server 2012 R2 (to activate Windows 10 and Windows Server 2016, you need to install a special update on KMS host and re-activate the KMS server with a new key).

If you try to install a new KMS key for Windows 10 on a KMS server running Windows Server 2012 R2 using VAMT without installing the specified update, you receive an error:

Unable to verify product key. The specified product key is invalid, or is unsupported by this version of VAMT. An update to support additional products may be available online.

Unable to verify product key. The specified product key is invalid, or is unsupported by this version of VAMT.

  Some tips:

  • Public KMS keys (GVLK – Generic Volume License Key) for Windows 7 / Server 2008 /2008 R2 can be found here, for Windows 8.1 / Server 2012 R2 here, for Windows 10 / Windows Server 2016 here and here, respectively.
  • For convenient MS product keys management, clients activation and reports generation, you can use the Microsoft Volume Activation Management Tool.
  • Using the same KMS server, you can activate not only Windows OS, but also MS Office products (for details see Activation of MS Office 2013 VL, KMS activation of Office 2016).
  • To activate virtual machines running on the Hyper-V, you can use the special activation type: AVMA (Automatic Virtual Machine Activation).

2 comments
0
Facebook Twitter Google + Pinterest
previous post
How to Clear Pagefile.sys at Shutdown in Windows 10 / 8 / 7
next post
Outlook 2016: Manual Setup Exchange Account

Related Reading

Using TSADMIN.msc and TSCONFIG.msc Snap-Ins on Windows Server...

February 2, 2021

Updating the PowerShell Version on Windows

December 24, 2020

Zerologon (CVE-2020-1472): Critical Active Directory Vulnerability

December 4, 2020

How to Run CMD/Program under SYSTEM (LocalSystem) in...

December 3, 2020

Remote Desktop Services Is Currently Busy

October 27, 2020

2 comments

Jeff July 21, 2016 - 5:03 pm

Hi  and thanks for the nice article.  I actually have a question.  We did the Volume_KMS_2012-R2_Win10 channel because we are deploying windows 10 in our environment.  The server has been up for a couple of days, and we have hundreds of Win 10 clients and probably 40 Win 2012 R2 servers that would be requesting  a license and yet we are not getting any activations.  We also installed VAMT 3.1.  We tried MS Activation support but they kept bouncing us between activation and activation support several times and we got no where.
Can you give us some help?

Reply
Daniel August 2, 2018 - 8:15 pm

It is worth noting that “Volume Activation Tool” is not “Volume Activation Management Tool” … and you can launch “Volume Activation Tool” by going into Server Manager, clicking “VA Services” on the left hand side, then right-clicking on your server and selecting “Volume Activation Tools”. If it can’t find it, then you need to add the Remote Server Administration Tools feature “Volume Activation Tools”. I believe in powershell the command is: Install-WindowsFeature -Name RSAT-VA-Tools

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Run Program without Admin Privileges and to Bypass UAC Prompt?
  • Updating List of Trusted Root Certificates in Windows 10/8.1/7
  • Installing SFTP (SSH FTP) Server on Windows with OpenSSH
  • How to Install .NET Framework 3.5 on Windows Server 2012 R2
  • Managing Printers and Drivers with PowerShell in Windows 10 / Server 2016
  • How to Clean Up “System Volume Information” Folder
  • PSWindowsUpdate: Managing Windows Updates from PowerShell
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top