Fighting with KMS licensing

[thunder9231]

This is for work, just for starters. I'm reaching out to other net or server admins that might have any ideas or are in the same position as I am.

 

If this post should be in under Windows Operating Systems, feel free to move it or delete/lock it so that I can post it there. Felt that it was server related so it's posted here.

 

LTSC = Long Term Service Channel (Was LTSB)

 

So, Server 2019 and Windows 10 LTSC 2019 are out. Awesome. I'm trying to do heavy testing of LTSC 2019 before I have a mass deployment to our student machines in the summer '19. The one problem I'm stuck on is getting the licensing and activation going correctly.

Currently, our KMS host resides on a Server 2012 R2 domain controller (Not looking to upgrade for a while longer, such stability) that has a Server 2016 KMS volume key installed. This is working great but does not activate LTSC 2019. 

 

I have read countless support articles from Microsoft and multiple posts on Technet, but I can't seem to find an answer. 

 

Pictured below is the working Server 2016 KMS key on a Server 2012 R2 running slmgr.vbs /dlv. Note that it says what is circled in red. IDs and partial product key hidden.

 

When I install our Server 2019 KMS key, it should do the same thing as circled in picture above except change from WS16 to WS19, but it doesn't. Pictured below in red.

 

This should work according to Microsoft's documentation, linked here and a Technet blog post here. (Yes, the KMS host server has the latest updates and the KB updates listed in the Technet link)

 

I'm struggling with an answer. I know that Server 2019 and LTSC 2019 just got re-released yesterday and I'm probably tackling this project too early on. I have reached to Microsoft but I didn't get anywhere with the VLSC support, probably not the right place to go to. Tomorrow I'm reaching out again and see if there is a different solution from Microsoft but I wanted to reach out to the LTT community and see if anyone has either ran into this problem and found a solution or is in the same boat as I am.

 

Thank you for any help!

 

[leadeater]

Might be easier for you to diagnose your issue if you use VAMT

[Jarsky]

I wonder if this could be related: https://support.microsoft.com/en-us/help/4343884/windows-10-update-kb4343884

 

---

Symptom	Workaround
After installing this update, installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.	Microsoft is working on a resolution and will provide an update in an upcoming release.

[thunder9231]

8 hours ago, Jarsky said:

I wonder if this could be related: https://support.microsoft.com/en-us/help/4343884/windows-10-update-kb4343884

 

---

Symptom	Workaround
After installing this update, installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.	Microsoft is working on a resolution and will provide an update in an upcoming release.

 

This would have worked but the update only applies to Server 2016, not Server 2012 R2. I looked for a similar update for 2012 R2 but the update I found that contains the same as the 2016 update didn't install since there is an update that has superseded it. I think I'm going to try and move the KMS from 2012 R2 to a 2016 server and try again. That would be a better result I would hope.

I'm going to patch the 2016 server with the update you linked, if it doesn't do it via WU. Thank you for the link!

[Mikensan]

Have you tried activating clients, just in case what you're seeing is just a "typo" to be corrected later? Remember you'll need to meet the minimum number of clients before it will activate clients.

 

If you have the resources I would create a quick lab to try and recreate the issue in a clean environemnt. This is to see if it is a M$ issue or an issue with your server (GPOs or whatever may cause it).

 

 

[Falconevo]

If I remember rightly, when we started deploying 2016 during it's original debut we needed a patch applied to our KMS(s) to allow for 2012 R2 to license 2016 machines.  This came around 3 weeks after the OS was released if memory serves.   I'll ask the licensing guy's tomorrow what the crack is with 2019 licensing but I would imagine it will have a KB update requirement for the KMS to allow it to be aware of the licensing for the new OS.