Forum Discussion

Karl-WE's avatar
Karl-WE
MVP
Dec 13, 2022

HOW-TO : Use VAMT 3.1 for Windows Server activation 2016 through 2022 and license management

VAMT looks like legacy, albeit being updated and tremendously helpful: Do you use VAMT to manage your Office and Windows Server licensing, modern Windows Server or Office ADBA, traditional KMS or MA...
Management
Office
windows
Windows Server
IT_Nick's avatar
IT_Nick
Brass Contributor
Feb 27, 2024

Karl-WE 

Hi Karl,

Thanks for the workaround but I am not sure it will fix my problem. I am having the same problem when adding 2022 MAK keys to VAMT 3.1.

 

I am migrating an ancient 2012 R2 server VAMT over to a new 2022 server. I followed the MS documentation and installed the server, installed SQL Express 2022, then the latest ADK. Connected the VAMT to the SQL creating a new table for it. I brought in the backup I did of keys etc from the old server and imported them without a problem. I then added my new CSVLK for 2022 also without a problem. However, when I tried to bring in the MAK keys for 2022 I got the same error as you show in the article which this workaround is linked to.  Any ideas on what is going on here and if there is a workaround for this?

Any assistance greatly appreciated.

Thanks

Nick

  • Karl-WE's avatar
    Karl-WE
    MVP
    Feb 27, 2024

    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).

    • IT_Nick's avatar
      IT_Nick
      Brass Contributor
      Feb 29, 2024

      Karl-WE 

       

      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

Resources