Forum Discussion

Karl-WE's avatar
Karl-WE
MVP
Oct 11, 2021
Solved

ISSUE: Windows Server 2022 Generic KMS Keys appear as Server 2021 in VAMT 3.x

When implementing Windows Server 2022 Generic Volume License Keys, the Server is recognized as Windows Server 2021.      
management
windows server
  • abbodi1406's avatar
    abbodi1406
    Oct 13, 2021
    It's not ADK issue, it can only be fixed with updated pkeyconfig.xrm-ms
abbodi1406's avatar
abbodi1406
Iron Contributor
Oct 12, 2021
All Server 2022 keys are named Server 2021 in the pkeyconfig (because that was the planed name)
don't get too attached to numbers 🙂
  • Karl-WE's avatar
    Karl-WE
    MVP
    Oct 13, 2021

    abbodi1406 Mary Hoffman so can we expect as you Mary said this a known issue and the ADK will be updated, also to fix the database issue (workaround from community works).

    Thanks for your reply Abbodi.

    • abbodi1406's avatar
      abbodi1406
      Iron Contributor
      Oct 13, 2021
      It's not ADK issue, it can only be fixed with updated pkeyconfig.xrm-ms
      • Karl-WE's avatar
        Karl-WE
        MVP
        Apr 23, 2022

        Hi Mary Hoffman, is there any ETA for a fix of both issues (wrong displayname for Windows Server 2022, VAMT DB issue as in reference?

         

        Thank you, I understand it is a minor thing, but it's been a while so sorry for asking and tagging. Hope you can help to tell more about the triage state so that the ADK / VAMT DB issue and the  config file as abbodi1406 mentioned could get fixed.

Resources