Skip to content

Conversation

@MrRubberDucky
Copy link

@MrRubberDucky MrRubberDucky commented Feb 12, 2025

Changes

  • Based on latest SKUs & GVLKs posted by Hotbird64 on MDL forums from License Manager 5.1 (so uses 2.0 version)
  • Windows 11 + Windows Server 2025 added to <WinBuilds>
  • Tidied up file formatting
  • Cleaned up and re-ordered things around, needs further testing to see if it will activate everything properly (De-duplicated entries while at it as otherwise py-kms seemed to have a bit of trouble by giving me dreaded F74 error back)
  • Proper pkeyconfig settings for Server 2025 and Server 2022

This adds support for following:

  • Office 2024 LTSC (incl. Preview)
  • Office 2021 LTSC (incl. Preview)
  • Office 2021 Preview GVLKs
  • Office 2019 Preview GVLKs
  • Windows 10/11 Insider Preview GVLKs (Volume)
  • Windows 10/11 Insider Preview GVLKs (Retail)
  • Windows Server 2022 Azure Core, Datacenter Azure Edition, Datacenter (Semi-Annual Channel), Standard (Semi-Annual Channel)
  • Windows Server 2025 (incl. Datacenter Azure Edition and Azure Core)

Additional notes

Closes: #99
Closes: #126
Closes: #128
Closes: #129

Testing

Download and mount KmsDataBase.xml to /home/py-kms/KmsDataBase.xml and restart container.

Does it activate?

Yes.

Office 2024
Windows 11
Windows Server 2025

@MrRubberDucky MrRubberDucky changed the title [WIP - Partially Done] Update KmsDataBase.xml, add missing entries and SKUs etc. Update KmsDataBase.xml, add missing entries and SKUs etc. Feb 14, 2025
@MrRubberDucky MrRubberDucky marked this pull request as ready for review February 14, 2025 23:27
Copy link

@bslatyer bslatyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@FDrebin
Copy link

FDrebin commented Aug 23, 2025

Any idea when this would be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows Server 2025 details for a database.xml update Office 2024

4 participants