Forum Discussion
Solved
ISSUE: Microsoft ADK b25217 or earlier, VAMT 3.1 has issues with Windows Server 2019 / 2022
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 ...
- 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-licenses-to-vamt.html
- 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
- 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
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?
How should we execute activation at scale of WS 2019 against ADBA if we cannot install the GVLK?
- 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-licenses-to-vamt.htmlAs 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!