Server 2022 GVLK Keys not visible in GUI

[Flol0]

Hello,

the Server 2022 GVLK Keys are not visible in the GUI

[simonmicro]

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml

...but I struggle to do that for you, because I'll need some more information for that:

• SkuId of the CSVLK
• GroupId
• MinKeyId
• MaxKeyId
• InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

[didotb]

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml

...but I struggle to do that for you, because I'll need some more information for that:

* SkuId of the CSVLK

* GroupId

* MinKeyId

* MaxKeyId

* InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

How were those info gathered?
I can look it up if I knew how it was found on the other versions.

[simonmicro]

Ooof, I have no idea where those came from. My first guess would be that the slmgr.vbs script know more about them...

[didotb]

it's my first time reading about how KMS works and it's still confusing me.. Although I found a CSVLK Pack which I extracted from update KB3172614

[patan32]

@simonmicro
I hope this helps.

[BenPi-Ross]

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml

...but I struggle to do that for you, because I'll need some more information for that:

• SkuId of the CSVLK
• GroupId
• MinKeyId
• MaxKeyId
• InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

From another fork of py-kms, I found this version of the database file that includes Windows Server 2022 :
https://raw.githubusercontent.com/hyperboreanwolfgirl/py-kms/master/py-kms/KmsDataBase.xml

• GroupId : 206
• MinKeyId : 551000000
• MaxKeyId : 570999999
• InvalidWinBuild : [0,1,2]

Using that file, the GUI is showing the following SKU ID :

• 9bd77860-9b31-4b7b-96ad-2564017315bf (Windows Server 2022 Standard)

As for the WinBuilds section of the database file, it's missing an entry for Windows Server 2022 and from what I gathered on the Net, it should looks like that :

<WinBuilds>
        [...]
        <WinBuild BuildNumber="20348" DisplayName="Windows Server 2022" UseForEpid="true" PlatformId="3612" MayBeServer="true" UsesNDR64="true" MinDate="18/08/2021"/>
</WinBuilds>

[Matthew-Beckett]

@simonmicro I've pulled in the changes mentioned by @BenPi-Ross into a PR at #96

[xadammr]

@Matthew-Beckett I have tested the PR, and it doesn't resolve the issue. I have located an updated KmsDataBase.xml and have raised PR #99

[daf-scripts]

Does this help? (Make sure to scroll over) Utilized pkeyconfigreader with a pkeyconfig from Windows 11. Not sure why it is called Server 2021 when it is really Server 2022

ActConfigID	RefGroupID	EditionID	ProductDescription	ProductKeyType	IsRandomized	PartNumber	EULAType	Product Key	Product ID	Extended PID	RefGroupID
{ec868e65-fadf-4759-b23e-93fe37f2cc29}	4327	ServerRdsh	Windows Server 2019 RTM ServerRdsh Volume:GVLK	Volume:GVLK	FALSE	[RS5]X21-83765	Volume	CPWHC-NT2C7-VYW78-DHDB2-PG3GK	00432-70000-00000-AA869	XXXXX-04327-000-000000-03-1033-9200.0000-2462023	4327
{19b5e0fb-4431-46bc-bac1-2f1873e4ae73}	4469	ServerTurbine	Windows Server 2019 RTM ServerTurbine Volume:GVLK	Volume:GVLK	FALSE	[RS5]X22-30731	Volume	NTBV8-9K7Q8-V27C6-M2BTV-KHMXV	00446-90000-00000-AA458	XXXXX-04469-000-000000-03-1033-9200.0000-2462023	4469
{9bd77860-9b31-4b7b-96ad-2564017315bf}	4541	ServerStandard	Windows Server 2021 RTM ServerStandard Volume:GVLK	Volume:GVLK	FALSE	[Fe]X22-39407	Volume	VDYBN-27WPP-V4HQT-9VMD4-VMK7H	00454-10000-00001-AA343	XXXXX-04541-000-000001-03-1033-9200.0000-2462023	4541
{ef6cfc9f-8c5d-44ac-9aad-de6a2ea0ae03}	4546	ServerDatacenter	Windows Server 2021 RTM ServerDatacenter Volume:GVLK	Volume:GVLK	FALSE	[Fe]X22-39426	Volume	WX4NM-KYWYW-QJJR4-XV3QB-6VM33	00454-60000-00001-AA230	XXXXX-04546-000-000001-03-1033-9200.0000-2462023	4546
{f5e9429c-f50b-4b98-b15c-ef92eb5cff39}	4556	ServerStandardACor	Windows Server 2021 RTM ServerStandardACor Volume:GVLK	Volume:GVLK	FALSE	[Fe]X22-39464	Volume	67KN8-4FYJW-2487Q-MQ2J7-4C4RG	00455-60000-00001-AA970	XXXXX-04556-000-000001-03-1033-9200.0000-2462023	4556
{39e69c41-42b4-4a0a-abad-8e3c10a797cc}	4557	ServerDatacenterACor	Windows Server 2021 RTM ServerDatacenterACor Volume:GVLK	Volume:GVLK	FALSE	[Fe]X22-39465	Volume	QFND9-D3Y9C-J3KKY-6RPVP-2DPYV	00455-70000-00001-AA521	XXXXX-04557-000-000001-03-1033-9200.0000-2462023	4557
{8c8f0ad3-9a43-4e05-b840-93b8d1475cbc}	4562	ServerAzureCor	Windows Server 2021 RTM ServerAzureCor Volume:GVLK	Volume:GVLK	FALSE	[Fe]X22-39475	Volume	6N379-GGTMK-23C6M-XVVTC-CKFRQ	00456-20000-00001-AA869	XXXXX-04562-000-000001-03-1033-9200.0000-2462023	4562
{e4db50ea-bda1-4566-b047-0ca50abc6f07}	3895	ServerRdsh	Windows Server Next Beta ServerRdsh Volume:GVLK	Volume:GVLK	FALSE	[RS3]X21-41298	Volume	7NBT4-WGBQX-MP4H7-QXFF8-YP3KX	00389-50000-00001-AA010	XXXXX-03895-000-000001-03-1033-9200.0000-2462023	3895

[miljw002]

Hi,

Just thought I'd add my 2.2 cents worth as I can see a few pull requests for this.

I've been happily using pyKMS for years, but was running it on a Linux box using systemd. Recently been moving small footprint things across to Docker containers in stead, so only been looking at this more in depth as part of that.

pyKMS has been successfully activating Windows 10/11, Office 2021, Server 2022 etc, but I also encountered the issue of Windows Server 2022 not appearing as such in the WebUI as this was the first time I actually explored the Web UI.

I tried using the updated KmsDatabse.xml from #106, and while the WebUI had the correct product name and showed as 'activated' the Windows Servers 2022 were failing saying the KMS server was unavailable.

I then tried using #96 as the basis, and the activations started working again, and the WebUI was showing the correct Windows Server 2022 name, but it didn't have the Windows 11 changes.

So, I tried grabbing the KmsDataBase.xml from the current branch, and just added in the Windows Server 2022 entries from pull request 96.

I now have all the clients still successfully activating (including Windows Server 2022), and the WebUI is listing Windows Server 2022 and Windows 10/11 Enterprise etc. Attaching incase this helps anyone else, and I can see there are a few different pull requests with different KmsDataBase.xml files. The attached is working for me.
KmsDataBase.zip