Forum Discussion
Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
ajc196 thank you for your follow-up and sharing the outcome of your support request. Maybe you want to share the SR so it could be used as reference just in case others want to point on this one.
I understand your contraints for ADBA. It is not a one fits all solution, just wanted to make clear that fiddling with slmgr or using KMS is not the best solution for AD deployed machines anymore.
Hello All, I have the same situation here. Windows Server 2022 KMS Host which does not activate my LTSC Clients. Has any body conatct to the MS Support about this?
Markus
- ItzikT2095Nov 30, 2021Copper ContributorDid you even read the discussion? Yes, many of us opened cases, read through and you'll have all the info you need.
- Carlin ZotzDec 01, 2021Copper Contributor
Does anyone have confirmation if this issue exists in ADBA as well? I was about to switch us from 2012 R2 to ADBA and 2022 KMS host key, but I may have to just use the 2019 key instead for now. Thoughts?
- kwester-ebbinghaus-businessDec 01, 2021Iron Contributor
I can confirm that ADBA works great also in junction with VAMT3 from the Windows 11 ADK.
One-time caveat with the DB though:
https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/adk-for-windows-11-and-adk-for-windows-server-2022-vamt-does-not/m-p/2719842
and some strange glitches: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/issue-windows-server-2022-generic-kms-keys-appear-as-server-2021/m-p/2833861#M5871
p.s. mind that my report is about ADBA with Windows Server 2022 KMS key and Windows Server, while some here reported issues with LTSC clients. I cannot tell much whether LTSC clients issues would be solved with that switch to ADBA.