Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update KmsDataBase.xml #129

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update KmsDataBase.xml #129

wants to merge 1 commit into from

Conversation

ProfessorCha0s
Copy link

This change to KmsDataBase.xml adds support for Windows Server 2025 Datacenter and Windows Server 2025 Standard.

This also separates/breaks out Windows Server 2022 into Windows Server 2022 Datacenter and Windows Server 2022 Standard.

Still need to add Windows Server 2025 Datacenter: Azure Edition as mentioned in #128, however we do not have the Activation ID for that version at this time to include it.

I have built this into a new Docker image for testing and have successfully activated Windows Server 2025 and it shows the correct SKU ID and License status as per screenshot below:

py-kms

Feel free to merge or to use the information from my changes to update the existing KmsDataBase.xml file separately.

@ProfessorCha0s
Update KmsDataBase.xml
fae0a03 
Add Server 2025 Datacenter and Server 2025 Standard

Break out Server 2022 Datacenter and Server 2025 Standard
@mattish91
Copy link

Id like to review this, and the ID's seams to be matching mine (Both DC and Standard). Any way to implement this change manually on my container so i can leave a proper review? (Im a novice docker user unfortunately, but know my way around to some extent.)

I might also be able to add Office 2024 LTSC as im figuring out how to grab the ID's from the KMS (It does activate just fine).

@ProfessorCha0s
Copy link
Author

Id like to review this, and the ID's seams to be matching mine (Both DC and Standard). Any way to implement this change manually on my container so i can leave a proper review? (Im a novice docker user unfortunately, but know my way around to some extent.)

I might also be able to add Office 2024 LTSC as im figuring out how to grab the ID's from the KMS (It does activate just fine).

Sure thing. You will need to either clone my repo with the change or clone the master and copy over your own KmsDataBase.xml with the new keys for Server 2025 and any other ones (such as Office 2024 LTSC you mentioned).

Then you will build the docker image and put it somewhere where you can deploy it (I'm using a local repository myself). Here is the command to build and push to a repo (make sure you specify the -f with the path to the Dockerfile since it's not at the root)

docker buildx build -f /<path to cloned repo>/py-kms/docker/docker-py3-kms/Dockerfile --push --platform linux/amd64 --tag <ip of repo>:<port of repo>/<some image name> /<path to cloned repo>

Here is mine for example:

docker buildx build -f /home/ProfessorCha0s/py-kms/docker/docker-py3-kms/Dockerfile --push --platform linux/amd64 --tag 192.168.1.10:5000/py-kms-updated /home/ProfessorCha0s/py-kms/

Then you spin up a container using the new image. If you are replacing your current py-kms instance, you should just need to run cscript //nologo slmgr.vbs /ato on your Windows Server 2025 and it will now show up correctly when you check the py-kms website as my screenshot shows.

mattish91
mattish91 approved these changes Jan 2, 2025
View reviewed changes
Copy link

@mattish91 mattish91 left a comment

Choose a reason for hiding this comment

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

This is confirmed working for me (see screenshot):

image

@Rodin1a
Copy link

Rodin1a commented Jan 2, 2025

Id like to review this, and the ID's seams to be matching mine (Both DC and Standard). Any way to implement this change manually on my container so i can leave a proper review? (Im a novice docker user unfortunately, but know my way around to some extent.)

I might also be able to add Office 2024 LTSC as im figuring out how to grab the ID's from the KMS (It does activate just fine).

When will this be resolved? I want to update Office.
I know it gets authenticated, but the display is all over the place.

@ProfessorCha0s
Copy link
Author

I have the Generic Volume License Key for Office 2024 LTSC, so if anyone has the Activation ID for it, I can add it to the KmsDataBase.xml as well. Would want to have the ID for Professional and Standard.

Also needed are the individual Activation IDs for the 2024 versions of

  • Access
  • Excel
  • Outlook
  • PowerPoint
  • Project Profession
  • Project Standard
  • Skype For Business
  • Visio Professional
  • Visio Standard

I'll see what I can find to add those, but if anyone has that then please share.

@Rodin1a
Copy link

Rodin1a commented Jan 2, 2025 •
edited
Loading

I have the Generic Volume License Key for Office 2024 LTSC, so if anyone has the Activation ID for it, I can add it to the KmsDataBase.xml as well. Would want to have the ID for Professional and Standard.

Also needed are the individual Activation IDs for the 2024 versions of

  • Access
  • Excel
  • Outlook
  • PowerPoint
  • Project Profession
  • Project Standard
  • Skype For Business
  • Visio Professional
  • Visio Standard

I'll see what I can find to add those, but if anyone has that then please share.

I’m getting an error saying "/LICENSE": not found, and the build doesn’t proceed. I want to build for arm64, but do I need to build on amd64 instead?

and => CANCELED [ 1/11] FROM docker.io/library/alpine:3.15 too..

@ProfessorCha0s
Copy link
Author

When you build, you have to be in the root of the folder and use -f to specify the path to Dockerfile. I have an example in one of my posts above.

So far, only Server 2025 Standard and Datacenter have been added to this update. Just keep that in mind until we are able to add Office and the others at another time (once we have the Activation IDs -- I'm researching this now).

@mattish91
Copy link

mattish91 commented Jan 6, 2025 •
edited
Loading

My output for Office LTSC 2024 Professional Plus:
PRODUCT ID: 00502-40000-00000-AA293
SKU ID: 8d368fc1-9470-4be2-8d66-90e836cbb051
Last 5 characters of installed product key: GCVGB

My output for Office LTSC 2024 Standard:
PRODUCT ID: 00503-50000-00000-AA605
SKU ID: bbac904f-6a7e-418a-bb4b-24c85da06187
Last 5 characters of installed product key: H6HGR

I hope this helps to some degree?

@didotb
Copy link

didotb commented Jan 6, 2025 •
edited
Loading

Also needed are the individual Activation IDs for the 2024 versions of

Check back in a few since ODT installation for some reason takes quite a lot of time, but I'm already installing them all in bulk.
I'll update this as soon as the said apps are installed.

Already updated with activation status given by the OSPP script.

On another note, wouldn't it be better to push it to next branch instead?
Unless you didn't include the patch for the Python 3.12?

Access

PRODUCT ID: 00501-00000-00000-AA655
SKU ID: 72e9faa7-ead1-4f3d-9f6e-3abc090a81d7
LICENSE NAME: Office 24, Office24Access2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259197 minute(s) before expiring)
Last 5 characters of installed product key: JMCWD

Excel

PRODUCT ID: 00501-20000-00000-AA071
SKU ID: cbbba2c3-0ff5-4558-846a-043ef9d78559
LICENSE NAME: Office 24, Office24Excel2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: CKGJG

Outlook

PRODUCT ID: 00501-50000-00000-AA250
SKU ID: bef3152a-8a04-40f2-a065-340c3f23516d
LICENSE NAME: Office 24, Office24Outlook2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: RJWB9

PowerPoint

PRODUCT ID: 00501-70000-00000-AA395
SKU ID: b63626a4-5f05-4ced-9639-31ba730a127e
LICENSE NAME: Office 24, Office24PowerPoint2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: FYCWP

Project Professional

PRODUCT ID: 00501-90000-00000-AA852
SKU ID: f510af75-8ab7-4426-a236-1bfb95c34ff8
LICENSE NAME: Office 24, Office24ProjectPro2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259199 minute(s) before expiring)
Last 5 characters of installed product key: 76HF4

Project Standard

PRODUCT ID: 00502-20000-00000-AA771
SKU ID: 9f144f27-2ac5-40b9-899d-898c2b8b4f81
LICENSE NAME: Office 24, Office24ProjectStd2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: G87F8

Skype for Business

PRODUCT ID: 00503-40000-00000-AA945
SKU ID: 0002290a-2091-4324-9e53-3cfe28884cde
LICENSE NAME: Office 24, Office24SkypeforBusiness2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: F64P3

Visio Professional

PRODUCT ID: 00503-60000-00000-AA670
SKU ID: fa187091-8246-47b1-964f-80a0b1e5d69a
LICENSE NAME: Office 24, Office24VisioPro2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259199 minute(s) before expiring)
Last 5 characters of installed product key: YY89G

Visio Standard

PRODUCT ID: 00503-70000-00000-AA965
SKU ID: 923fa470-aa71-4b8b-b35c-36b79bf9f44b
LICENSE NAME: Office 24, Office24VisioStd2024VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 179 days  (259179 minute(s) before expiring)
Last 5 characters of installed product key: WQQTV

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

@mattish91 mattish91 mattish91 approved these changes

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ProfessorCha0s @mattish91 @Rodin1a @didotb