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

[Karl_Wester-Ebbinghaus]

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 MAK? License assignment and reporting at scale? You should. In many cases it can also assist to get rid of KMS Server altogether and making it super easy to determine activation methods, migrate to other keys or from KMS to ADBA where appropriate. 

Whatever your usecase is, VAMT 3.1 is still being updated with every release of Windows ADK. One reason is the appearance of new OS or Office LTSC releases, but also added support to manage your Windows Client and Windows Server ESU at scale. WS 2012 / 2012 R2 ESU will be next. 

The issue:

If you are using it, you might be currently on a release that may not allow to add Windows Server 2019 GVLK, or otherwise one that does not allow to add Windows Server 2022 GVLK. 

How to adress this:

I found a workaround for this, without fiddling in the files. 

- Install ADK Windows 10 before 22H2 > VAMT 

- Install all needed GVLK keys in VAMT 3.1.

- Windows Server 2008-2019, Windows 7-10

- uninstall ADK. 

- install Windows 11 ADK (currently latest 22H2) > VAMT

- run VAMT, choosing the same database, 

- add Windows Server 2022 GVLK keys to VAMT.

- now is a good time to backup the database using the latest SQL Management Studio (SMSS) 

Hint: Preferably place the VAMT database into an appropriate central SQL Standard instance, instead of the default SQL Express 2019 or later (e. g. Citrix Studio / PVS / License DB instance).

The VAMT DB is a quite compact, mostly static database. Running an SQL Express instance for just this matter increases RAM and management overhead, even though SQL Server (Express) 2017 - 2022, can now be directly and automatically patched via WU / WSUS / Azure Update Manager etc.

[#2]

VAMT related articles

Issue report Windows Server Insider:
https://techcommunity.microsoft.com/t5/windows-server-insiders/issue-microsoft-adk-b25217-or-earlier...

Renaming of Windows Server 2022 missing in VAMT (no functional regression):

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/issue-windows-server-2022-generic-k...

VAMT Database connection issue (fixed with ADK Windows 11 22H2):

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/adk-for-windows-11-and-adk-for-wind...

Later Windows or Office 2021 LTSC keys could not be added (fixed with ADK Windows 11 22H2):

https://learn.microsoft.com/en-us/answers/questions/638230/issue-adding-windows-10-ltsc-2021-license...

Kudos for ongoing support and knowledge in Windows Servicing and VAMT area

@abbodi1406 🙏🏼

Official documentation:

https://learn.microsoft.com/windows/deployment/volume-activation/volume-activation-management-tool

Hint: Consider en-us version for the latest updates. 

[#3]

@Karl_Wester-Ebbinghaus 

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

[#4]

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

[#5]

@Karl_Wester-Ebbinghaus 

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