I have reached to Microsoft but I didn't get anywhere with the VLSC support, probably not the right place to go to. I know that Server 2019 and LTSC 2019 just got re-released yesterday and I'm probably tackling this project too early on. (Yes, the KMS host server has the latest updates and the KB updates listed in the Technet link)
This should work according to Microsoft's documentation, linked here and a Technet blog post here. 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. Note that it says what is circled in red. Pictured below is the working Server 2016 KMS key on a Server 2012 R2 running slmgr.vbs /dlv. I have read countless support articles from Microsoft and multiple posts on Technet, but I can't seem to find an answer. This is working great but does not activate LTSC 2019. The one problem I'm stuck on is getting the licensing and activation going correctly.Ĭurrently, 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.
I'm trying to do heavy testing of LTSC 2019 before I have a mass deployment to our student machines in the summer '19. So, Server 2019 and Windows 10 LTSC 2019 are out. LTSC = Long Term Service Channel (Was LTSB) Felt that it was server related so it's posted here.
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. I'm reaching out to other net or server admins that might have any ideas or are in the same position as I am.
0 kommentar(er)
