Forum Discussion
HOW-TO : Use VAMT 3.1 for Windows Server activation 2016 through 2022 and license management
Hello Nick,
I am afraid there no solution but unfeasible workarounds. You are not alone with that issue and I personally consider VAMT still a worthy tool for licensing overview and license assigment.
True, AVMA + M365 might make things, including ADBA obsolete, but it is still a thing. Especially for VMware scenarios.
I will try to check if anyone want to be assigned to this issue.
Status quo:
- CSP (subscriptions) do not offer KMS keys anymore, which make VAMT even more needed for non AVMA scenarios
- currently we can either add WS 2022 or WS 2019 keys (MAK / CVLK).
Hi Karl,
Noticed something weird in VAMT under AD Based Activation. My CSVLK Volume_KMS_WS22 channel key is only showing supported products of Windows 8 and Server 2012.
However in Product Keys the Same CSVLK is showing as Edition: ServerDatacentre;ServerStandard with a Description Windows Server 2021 RTM ServerDatacenter;ServerStandard. Is this yet another bug or do I have the wrong CSVLK for 2022?
Thanks
Nick