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 2019 / KMS Activation for Windows Server 2019

July 8, 2019 Windows 10Windows Server 2019

KMS Activation for Windows Server 2019

Due to the recent release of the new Windows Server 2019, it is time to update the KMS activation infrastructure in your domain and add the support of new versions of Windows Server and Windows 10 1809 / LTSC 2019 (Long Term Service Channel) on your KMS server. If you want to learn more about Microsoft KMS activation, we recommend to start with studying Microsoft KMS Activation FAQ.

Contents:
  • Installing New KMS Server on Windows Server 2019
  • Updating Windows Server 2012 R2/2016 KMS to Support Windows Server 2019 Activation
  • GVLK Keys for Windows Server 2019 & Windows 10 LTSC

Installing New KMS Server on Windows Server 2019

If you don’t have any KMS servers in your domain, you can install the Volume Activation Services role on your new Windows Server 2019 host. The procedure is similar to the installation and activation of a KMS server on Windows Server 2012 R2 or Windows Server 2016. Here’s what to do in brief:

  1. Install the Volume Activation Services role on your server from the Server Manager console or using the PowerShell command: Install-WindowsFeature -Name VolumeActivation -IncludeAllSubFeature –Include ManagementTools
  2. Enable the firewall rules that allow access to the KMS server: Enable-NetFirewallRule -Name SPPSVC-In-TCP
  3. Sign in to your account on Microsoft Volume Licensing Service Center (VLSC) website and go to License -> Relationship Summary -> Select License ID for your Active License contract -> Product Keys. Copy the key for Windows Srv 2019 DataCtr/Std KMS;
  4. Install the KMS key using the following command: slmgr /ipk <KMS_host_key_Windows_Server_2019>;
  5. Activate your KMS server on Microsoft activation servers: slmgr /ato
  6. If you are going to use this KMS server to activate MS Office products, you need to install the license packages for the Office versions you have (Office 2010, Office 2013, or Office 2016 / 2019). Then specify the KMS Host Key to activate your Office edition and activate your KMS server (you can find the detailed instructions following the links above);
  7. Now you can use your KMS server to activate all supported Windows (from Windows 7 to Windows 10) and Windows Server versions (2008R2 to 2019).

Updating Windows Server 2012 R2/2016 KMS to Support Windows Server 2019 Activation

If your company has an activated KMS server running Windows Server 2016 or 2012 R2 and you don’t want to deploy a new server running Windows Server 2019, you can use the old hosts to activate new versions of Windows Server and Windows 10 1809 / LTSC 2019. To do it, you need to specify a new KMS Host Key on the old activation server.

In my case, I tried to specify the new Windows Srv 2019 DataCtr/Std KMS key on the KMS server running Windows Server 2016 using the command:

slmgr /ipk <KMS_host_key_Windows_Server_2019>

But the following error appeared:

Error: 0xC004F015 On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0xC004F015’ to display the error test.

slmgr - Error: 0xC004F015 On a computer running Microsoft Windows non-core edition

At the same time the error with the following description can be found in the event log:

Installation of the Proof of Purchase failed. 0xC004F015
Partial Pkey=xxxxxxxxxxxx
ACID = xxxID

Installation of the Proof of Purchase failed. 0xC004F015

When trying to activate the KMS key via the GUI, the following error appears:

Invalid product key or license mismatch.  Please confirm this product key is entered correctly and is valid for this application or Windows edition.

confirm this product key is entered correctly and is valid for this application or Windows edition

Of course, Windows 10 LTSC 2019 and WS2019 also cannot be activated on this KMS server with an ‘activation server unavailable’ error: Error code: 0xC004F074.

To use your old KMS server to activate new Windows versions, you must install some special KMS servers updates in order to support Windows 10 LTSC 2019, Windows 10 1809 and Windows Server 2019.

Install these updates on Windows Server 2012 R2:

  1. KB3173424  — Servicing Stack Update, July, 2016;
  2. Any Windows Server 2012 R2 cumulative update released after December, 11, 2018 (KB4471320) or newer.

The following updates are necessary on Windows Server 2016:

  1. KB4132216 — Servicing Stack Update, May, 2018;
  2. Any Windows Server 2016 cumulative update released after November, 27, 2018 (KB4467681) or newer.

After you have installed the updates and restarted the KMS server, you can add a new KMS host key (VLSC) and activate it.

GVLK Keys for Windows Server 2019 & Windows 10 LTSC

The list of public KMS activation keys (GVLK – Generic Volume License Key) for different Windows Server 2019 and Windows 10 LTSC editions is given in the following table:

OS Edition GVLK Key
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows 10 Enterprise LTSC 2019 M7XTQ-FN8P6-TTKYV-9D4CC-J462D
Windows 10 Enterprise N LTSC 2019 92NFX-8DJQP-P6BBQ-THF9C-7CG2H

To install a public KMS key on your computer or server, run this command:
slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
You can specify the KMS server for activation manually:
slmgr /skms corp-kms-ws2019.woshub.com:1688
To activate your OS on the KMS server:
slmgr /ato
To check Windows activation status:
slmgr /dlv

14 comments
0
Facebook Twitter Google + Pinterest
previous post
Tracking and Analyzing Remote Desktop Activity Logs in Windows
next post
Fix: The Local Print Spooler Service Not Running in Windows 10

Related Reading

How to Sign a PowerShell Script (PS1) with...

February 25, 2021

How to Shadow (Remote Control) a User’s RDP...

February 22, 2021

Configuring PowerShell Script Execution Policy

February 18, 2021

Configuring Proxy Settings on Windows Using Group Policy...

February 17, 2021

Updating Group Policy Settings on Windows Domain Computers

February 16, 2021

14 comments

ahdung September 26, 2019 - 1:52 am

So how to handle slmgr /ipk got 0xC004F015?

Reply
admin September 30, 2019 - 12:25 pm

Install the latest Servicing Stack and cumulative update for your Windows Server version.

Reply
HanGyi October 6, 2019 - 1:56 pm

i still can’t activate windows server 2019 and can you help me pls?

Reply
admin October 8, 2019 - 4:44 am

Please, specify your WS 2019 activation error.

Reply
admiPC November 6, 2019 - 3:08 pm

Installation of the Proof of Purchase failed. 0xC004F050
Partial Pkey=922PR
ACID=?
Detailed Error[?]

Reply
Shailesh December 13, 2019 - 11:56 am

if we want to migrate windows 2008 R2 KMS server to Windows 2019 server.. What will be steps involve?

Reply
admin January 15, 2020 - 9:36 am

1) Get your new WS2019 KMS host key from the VLSC
2) Deploy a new server running Windows Server 2019
3) Install the Volume Activation Services role
4) Install the KMS host key, activate your KMS host and update the SRV (_VLMCS) record in DNS by pointing it to the new KMS server

Reply
MANU May 3, 2020 - 12:56 pm

Is it possible to activate LTSC Evaluation build 17763.rs5 on home computer?

Reply
admin May 7, 2020 - 3:28 pm

First, you should upgrade your Evaluation edition to the Full LTSC version, and then use the MAK key to activate your Windows 10 LTSC copy.

Reply
muzzol June 8, 2020 - 12:14 am

how do you upgrade from evaluation to full LTSC?

Reply
Vijesh May 11, 2020 - 11:09 pm

Hi Admin,

OUR KMS host is W2012 R2 server and it has the patch KB3173424 and the latest security update KB4512488. I installed the Windows Srv 2019 DataCtr/Std KMS key on this host machine and it was successful. Now on my client which is a server 2019 std when I try to activate I get an error stating 0XC004F074 No KMS service could be contacted. This client can actually communicate to the host like I can telnet to KMS Host on port 1688 and then I have manually set the KMS host by using the slmgr.vbs /skms hostserver:1688 cmd.

on the cliet I can see event ID 12288 and on the host, I can see event ID 12290. The time settings on both the machines are fine. I am wondering if I am still missing a patch? I haven’t restarted my KMS host server, not sure if that’s needed

Reply
admin May 15, 2020 - 6:34 am

The first of all, check the time on the kms host and client (the time of the server and client should not be so different, otherwise actication requests may be rejected).
Have you activated your KMS host with a new KMS host key?
What version (build) of Windows are you trying to activate?

Reply
Gaurav Chopra June 17, 2020 - 2:39 pm

How to validate if Win2019 Server key is installed on existing KMS host? The dlv command doesn’t give clear picture

Reply
Shailendra Arya July 4, 2020 - 8:26 am

I don’t have KMS server in my home lab environment, I wanted to activate Windows server 2019 Std/DC edition. Will that be possible and what is the key?

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 Allow Multiple RDP Sessions in Windows 10?
  • How to Repair EFI/GPT Bootloader on Windows 10?
  • How to Restore Deleted EFI System Partition in Windows 10?
  • Network Computers are not Showing Up in Windows 10
  • Booting Windows 7 / 10 from GPT Disk on BIOS (non-UEFI) systems
  • How to Run Program without Admin Privileges and to Bypass UAC Prompt?
  • Removable USB Flash Drive as Local HDD in Windows 10 / 7
Footer Logo

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


Back To Top