Heya. for those of you in Azure and using WS 2022,...
# citrix-vadm
Matt Nation
06/26/2024, 3:34 PMHeya. for those of you in Azure and using WS 2022, which version of 2022 are you deploying? datacenter or datacenter azure edition or something else?
a
Aaron O'Reilly
06/26/2024, 10:36 PMLatest customer has been using Azure edition for all static servers to benefit from the patching improvements coming with it, and plain datacenter for their MCS master images.
đź‘Ť 1
m
Matt Nation
06/28/2024, 5:10 PMThanks @Aaron O'Reilly. have you seen issues with 2022 taking a day to activate the OS against msft' KMS?
a
Aaron O'Reilly
07/01/2024, 12:15 AMHaven't seen that issue. Originally did have a few issues with the bug where the GUI showed the server was not activated (even though it had been via CLI) if the timezone was set to anything other than UTC.
m
Matt Nation
07/03/2024, 1:56 PM@Aaron O'Reilly we're seeing this too. Is there a workaround?
Matt Nation
07/09/2024, 2:53 PM@Aaron O'Reilly received this from msft and it seems to fix it.
slmgr /ckms (cleans the DNS cache of the KMS)
slmgr /skms azkms.core.windows.net:1688 (force the KMS to point to Azure's FQDN)
slmgr /ipk NTBV8-9K7Q8-V27C6-M2BTV-KHMXV (forces the correct activation key)
slmgr /ato (activates the machine)
Schtasks /change /TN "\Microsoft\Windows\Clip\LicenseImdsIntegration" /RU “NT Authority\System”