Forum Discussion
Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
Sorry, to clarify: AD is at a functional level of 2012 R2. Using ADBA for 2019 LTSC I'm having this same issue, as described.
Deleted Who knows.
the upcoming Windows ADK for Windows Server, version 23H2 (build 25398) is around the corner, we shall see
thank you abbodi1406 for confirming this once again.
So there is no hope this will be fixed in VAMT (as part of ADK) in the future?
- Sorry, I'm unaware about that particular item.
Deleted That's ADK restriction / design
OS updates don't fix or changed it
Cheers ajc196 for the update on this update #punintended.
do you know if this said KB also fixed the issue that ADK may not import WS 2022 and / or WS 2019 GVLK into VAMT? Depending the version of ADK you could only import WS 2019 or 2022 keys, which led me to create a DB as template for customers.
- KB5010427 fixed this post's specific issue back in February 2022. If you're facing problems, it's likely another root cause.
Wondering if there was ever a solution to getting 2022 to activate?
Deleted I installed the latest version of VAMT, just to test. Same exact error on 2019 LTSC. We're rolling out 2022 soon-ish, so I suppose I can just wait until then. Just frustrating, as we've all experienced.
- KB5010427 for Server 2019 back in February fixed the issue in our environment and it has not recurred, at least not to my knowledge. Only extra thing we had to do was re-activate our 2022 host key after installing the patch.
- Deleted More meaning all DCs are 2012 R2. Though I was obscure in my response, it does make me wonder how ADBA works if you have - for instance - a Server 2022 DC and a 2012 R2 DC. Do clients intermittently activate - only when they hit the 2022 server? I digress...
Yes, ADBA isn't working on 2012 R2 DCs to activate 2019 LTSC (0xC004F074). Works fine with 2016 LTSB. Hello Ryan, I do not believe there is a functional relation between KMS and the Forest or Domain Functional level. Do you have found anything in docs.microsoft.com stating this relation?
Do I understand correctly that ADBA is not working for you either?ajc196 is your issue as posted in the OP fixed by today, if yes do you know how? Sorry this topic is quite long.
