Sep 09 2021 11:48 AM - edited Dec 01 2021 08:28 AM
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 common OS types in a quick test afterward -- Win10 Education 21H1, Server 2022, Server 2019, etc.
In the next few days, and even more today, we've been getting reports that Win10 Enterprise LTSB/LTSC across some signage devices and laboratory machines stopped activating. Sure enough, I could reproduce the issue from a known good network.
Just this morning I spun up entirely fresh VMs and verified all the above is still reproducible with the following results:
Windows Server 2022 = Successfully activated
Windows Server 2019 = Successfully activated
Windows Server 2016 = Successfully activated
Windows 10 Education 21H1 = Successfully activated
Windows 10 Enterprise LTSC 2021 = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise LTSC 2019 = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise 2016 LTSB = FAILED ACTIVATION (0xC004F074: License server reported that the computer could not be activated.)
Windows 10 Enterprise 2015 LTSB = Successfully activated (odd, after the previous two)
Windows 8.1 Enterprise = Successfully activated
Windows 7 Enterprise = Successfully activated
Anyone else seeing this or could possibly test and confirm? I feel like this **has** to be a bug with 2022 host keys, but it's so new that I can't find anyone else in the same boat. I have a Premier ticket open for this.
Feb 01 2022 12:37 PM
Feb 02 2022 03:15 AM
Dear @Mary Hoffman may I ask you to check with the team, if the fix for the Windows Server 2022 is on the way? From what I read it is not fixed for Windows Server 2022 but only Windows Server 2019, where is was also a known issue. For Windows Server 2022 it does not seem to be a known issue.
Addresses a known issue 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 might not activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK) and after installing updates released April 22, 2021 or later.
source: January 25, 2022—KB5009616 (OS Build 17763.2510) Preview (microsoft.com)
compare with: January 25, 2022—KB5009608 (OS Build 20348.502) Preview (microsoft.com)
Feb 03 2022 09:12 PM
A fully updated Windows Server 2022 does not recognize the KMS key. Knows it as Volume_KMS_WS19 and does not activate clients.
Feb 04 2022 07:45 AM
Feb 04 2022 10:39 AM
Feb 07 2022 01:42 AM
@Carlin Zotz both should work
- 2019 KMS Server with the 2022 CSVLK Key (with the patch).
- ADBA with the 2022 CSVLK Key (without any patch)
Feb 10 2022 12:39 AM
Feb 11 2022 08:09 PM
Feb 14 2022 06:46 AM
Feb 15 2022 03:02 PM
Feb 16 2022 03:06 AM
Feb 16 2022 04:01 AM
Feb 16 2022 04:12 AM
Feb 16 2022 04:27 AM
Feb 16 2022 04:57 AM
Feb 16 2022 05:20 AM
Feb 16 2022 06:19 AM
OK, So our KMS server is running Server 2019, so the equivalent update for that OS is KB5010427?
Has anyone tried that and got it working with the 2022KMS Host key?
Feb 16 2022 08:37 AM
Feb 16 2022 08:41 AM
Feb 16 2022 09:00 AM