Seems it is out of testing stage: https://forums.mydigitallife.net/th...-techbench-only-atm.83200/page-5#post-1657144
seems like latest script from abbodi1406 activates it properly Spoiler ************************************************************ *** Windows Status *** ************************************************************ Name: Windows(R), ServerDatacenter edition Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel Partial Product Key: 6VM33 License Status: Licensed Volume activation expiration: 259200 minute(s) (180 day(s)) Configured Activation Type: All Most recent activation information: Key Management Service client information Activation interval: 43200 minutes Renewal interval: 43200 minutes KMS host caching is enabled Windows(R), ServerDatacenter edition: Volume activation will expire 10/25/2021 2:51:01 PM ____________________________________________________________
KMS and KMS38 will always work, the keys for testing only work during the test period, they no longer working and no exp. date nor watermark suggests the testing period has ended.
An old bug is still present even if this release has reached an advanced stage in the release cycle. It warns the current user at restart/shut down that there is another user logged on even if there is none, except for a possible internal hidden user. The "Use my sign-in info..." which might have something to do with the behaviour described above is still greyed out regardless of the activation status or relevant Group Policy configured or not. I think this behaviour was acknowledged earlier by Microsoft in one of the blog articles related to a previous preview release, but nothing has changed since then and there have been few months since then.
Anyone having a problem activating 20344? When I use my own KMS server service (running as a local service), the command: "slmgr -ato" just hangs and is getting nowhere However, using @abbodi1406's script it works!
Might need a different activation key for KMS 2022 if you run a legit one. Otherwise, anything can change in the requirements without notice.
anyone tried using wsl2 on server 2022? When I try setting the default version to 2 with "wsl --set-default-version 2" it only prints usage help of wsl tool and default stays on version 1. Hyper-V virtualization works without problems.
For sure, Server 2022 will require SLIC version 2.6 Otherwise MS would almost hand out a "free" upgrade from 2019 to 2022
MRP Log & 20344 Server Standard 2022 desktop: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-358#post-1657419
Wondered if it might be prelude to a rebrand of some sort, but the way Setup now refers to it constantly by the clunky title of "Microsoft Server Operating System" ("MSOS"? You really want it shortened to something that includes "SOS"?) is just hilarious and amateurish-looking to see in a high end professional OS.
Maybe they will replace it with Server 2022 branding at some point. When installing I also wondered "What the heck is this branding?" Hopefully they replace it...
But if they were intending to do that... "Windows Server 2022" is a lot shorter and easier than the weird clunky way they did it.I could see them going to a title ("Windows Server insert-word-here") because I just can't see why else they would've gone with what they did.