Forum Discussion
Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
We recently dropped our new Server 2022 KMS host key onto our KMS server. After the necessary update to accept the 2022 key and activating the new 2022 host key, we were able to activate our most com...
With 2019 KMS you refer to the key or an KMS Server?
Considering the network and permission design VAMT from the said ADK is perfect for inventory. Reports for activation status and activation source etc.
Alternatively while you cannot add them effectively the add server feature of Server Manager gives an overview about the editions of Servers and Clients in your AD and also the versions, including LTSC
The best approach would be to use PowerShell and CSV exports filtering the OS description and build.
Has anyone tried ADBA with a 2022 KMS key?
Considering the network and permission design VAMT from the said ADK is perfect for inventory. Reports for activation status and activation source etc.
Alternatively while you cannot add them effectively the add server feature of Server Manager gives an overview about the editions of Servers and Clients in your AD and also the versions, including LTSC
The best approach would be to use PowerShell and CSV exports filtering the OS description and build.
Has anyone tried ADBA with a 2022 KMS key?
were having the same issue. I see a lot of people have opened tickets, but I didnt see any resolutions yet or did I miss something? Is there a solution?
Thanks
- https://support.microsoft.com/en-gb/topic/november-22-2021-kb5007254-os-build-20348-380-preview-9a960291-d62e-486a-adcc-6babe5ae6fc1
there is no mention of this bug in this bulletin - 2022 has an own update history will double check.
The problem was recognized only for 2016 and 2019 Servers. But not for Windows Server 2022!!!
- ajc196 it is now in the known issues in Windows Update history
https://support.microsoft.com/en-us/topic/november-22-2021-kb5007266-os-build-17763-2330-preview-c9ba0c4c-c8b7-409a-8fac-a76ffae8f94f
After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK).
Note This does not affect activation of any other version or edition of Windows.
Client devices that are attempting to activate and are affected by this issue might receive the error, "Error: 0xC004F074. The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."
Event Log entries related to activation are another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs > Application. If you see only event ID 12288 without a corresponding event ID 12289, this means one of the following:
The KMS client could not reach the KMS host.
The KMS host did not respond.
The client did not receive the response.
For more information on these event IDs, see Useful KMS client events - Event ID 12288 and Event ID 12289.
We are working on a resolution and will provide an update in an upcoming release. xwinger61 Doesn't seem to be a fix yet....Going to switch us to ADBA and use a 2019 KMS Key for now.
