ISSUE: Microsoft ADK b25217 or earlier, VAMT 3.1 has issues with Windows Server 2019 / 2022

[Karl-WE]

Affected Products:

Windows ADK VAMT 3.x - W11 version 22H2

Windows ADK VAMT 3.x - W11 version 21H2

Windows ADK VAMT 3.x - W10 version 21H2

Windows ADK VAMT 3.x - WS2022 version

Windows ADK VAMT 3.x - current preview 

1. VAMT 3.1 has the issue that the Windows Server 2022 is still named Windows Server 2021 in the configuration.

Introduced with ADK Windows 11 ADK 21H2 / Windows Server 2022 ADK

Problem: 

2. GVLK for Windows Server 2019 Datacenter or Standard are no longer accepted.

Introduced with ADK Windows 11 ADK 22H2 (eventually previous versions)

Problem: WS 2019 Standard + Datacenter generic keys can no longer be added to VAMT database.

Other product keys seem unaffected.

error:

GVLK Key source https://learn.microsoft.com/windows-server/get-started/kms-client-activation-keys

Thank you for flagging this to the team, it has been discussed in other topics, but I hope the next release of ADK will provide a fix (DB connection issue, is already fixed). TYVM in advance.

[#2]

- Server 2021 name issue will not be fixed i presume 🙂

- Since build 15063, ADK can support only two versions:
pkconfig_win10.xrm-ms = locked on build 14393 (Server 2016)
pkconfig_winNext.xrm-ms = the equivalent build keys

e.g.
Server 2022 ADK or later = support Server 2022, but not Server 2019
the next Server 2025 ADK = support Server 2025, but not Server 2022 or 2019

[#3]

I could live with the number but to decide for a VAMT for 2019 or 2022 or or later is extremely hard to handle in day to day scenarios.
How should we execute activation at scale of WS 2019 against ADBA if we cannot install the GVLK?

[#4 · Accepted solution]

Windows 10 LTSC 2021 had similar issue with ADK 22000 & 20348
you can add the support for WS 2019 manually in the same steps
https://learn.microsoft.com/en-us/answers/questions/638230/issue-adding-windows-10-ltsc-2021-license...

[#5]

As always thank you very much sharing the insights. You are not only a hero in the area of Windows Servicing, but also one for your duly service. Kudos!

[#6]

I have found a workaround and have written an how-to. Hope it's helpful to the community 

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/how-to-use-vamt-3-1-for-windows-ser...

Dear Microsoft team, I plea to fix this unfortunate regression. It is hard to understand why we haven't had same issues with WS 2016 / 2019.

[#7]

We've opened a work item for this issue. Thanks for reporting it.

[#8]

Hi @Mary Hoffman that's great news to hear. Thank you very much for your help! 

[#9]

Hi Mary, do you know if this is addressed in a ADK preview release or an ETA from the PG?

[#10]

@Mary Hoffman I have re-assessed the situation with VAMT 3.1 from b25290 Insider Preview ADK.

Adding WS 2019 keys, there is a little change in the message box, yet in the end, it doesn't work.

Sidenote the link "Check for updates online" is no longer functional for a long time

leading to https://download.microsoft.com/download/9/9/F/99F5E440-5EB5-4952-9935-B99662C3DF70/adk/adksetup.exe

[#11]

Hello @Karl-WE,

I have a similar issue when I try to add the WS2022 KMS licence on my KMS host.

Do you have any news about you last post?

Do you know if I can have Active Directory-Based Activation with 2019 and 2022 licence on the same host KMS?

At this moment, I have the WS 2019 ADBA working fine and I wanna add a WS2022 key. 

Regards,

[#12]

@XaviCusido

Have not heard back. It's on the list of internal issues, thanks to @Mary Hoffman.

In case you have overlooked it this is a workaround. Thanks for a thumbs up over there. 

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/how-to-use-vamt-3-1-for-windows-ser...

[#13]

Great! Thanks for the response. 😉