Windows Server 2022 - KMS Activation yet?
I noticed Friday on my company's VLSC site that there are now MAK and KMS keys for WS2022. I have confirmed that I can now activate 2022 with a MAK key, volume license. However, I'm unable to activate it via our KMS server. I found the KMS key on our VLSC site: Windows Srv 2022 DataCtr/Std KMS XXXXX-XXXXX-XXXXX-XXXXX-KQDWV KMS (Masked for privacy) I used these commands on our KMS server (running WS2016): slmgr.vbs /ipk KMS key slmgr.vbs /ato Both commands were successful. When I type slmgr.vbs /dlv all, I see this entry: Name: Windows(R), ServerDatacenter edition Description: Windows(R) Operating System, VOLUME_KMS_WS22 channel Activation ID: --- Application ID: --- Extended PID: 03612-04573-000-204477-03-1033-14393.0000-1972021 Product Key Channel: Volume:CSVLK Installation ID: --- Use License URL: https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail Validation URL: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx Partial Product Key: KQDWV License Status: Licensed Remaining Windows rearm count: 1000 Remaining SKU rearm count: 1001 Trusted time: 7/19/2021 7:39:34 AM Key Management Service is enabled on this machine Current count: 50 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal (Items masked for privacy) This all appears normal. Does anyone know why WS2022 won't activate yet? This is what I get on my WS2022 systems: Something prevented us from communicating with our activation servers. Wait a few minutes and then try again. Error code: 0x87E10BC6 I can even enter this command on the 2022 system to manually tell it to use our KMS server (Yes, I joined the 2022 system to our AD domain) slmgr.vbs -skms ourkmsserver.domain.name That works, but when I try: slmgr.vbs /ato It gives essentially the same error. Does anyone know if these keys are simply too new? Might there be a patch or MCU required on older Windows Server O/Ss to be able to activate newer versions? I know there was a patch back in the day that 2012 R2 KMS servers needed to install before they could successfully activate 2016 servers. Thank you for any info you may have! - Michael
Windows Server 2022 Version 21H2 (OS Build 20348.169)
Hiya When is the next refresh of the iso for for windows server 2022? the current iso release of windows server 2022 will not let you extend the partition with disk management or diskpart disk management is grayed out and diskpart says There is not enough usable space https://ibb.co/H4sVYF2 Operating System: Windows Server 2022 (10.0, Build 20348) (20348.fe_release.210507-1500) this is with computer install and not a virtual machine[Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
I have installed 20303.1 and added the SMTP Service and add the management tools. Install-WindowsFeature SMTP-Server -IncludeManagementTools After the installation, I bring up the IIS 6 Management Console. If I right-click the [SMTP Virtual Server] node and select properties, I get an error like this: Clues?How to Install WSL 2 on Windows Server
A couple of months ago Microsoft announced the Windows Subsystem for Linux 2 (WSL 2), which is a successor of the Windows Subsytem for Linux shipped a couple of years ago. WSL 2 is currently available for Windows Insiders running Windows 10 Insider Preview Build 18917 or higher and with the Docker Tech Preview, you can now even run Docker Linux Container directly on WSL 2. With the latest Windows Server Insider Preview build 18945, you are also able to run WSL 2 on Windows Server. In this blog post, I am going to show you how you can install the Windows Subsystem for Linux 2 (WSL 2) on Windows Server. The Windows Subsystem for Linux was already available in earlier versions of Windows Server; however, WSL 2 brings a lot of new advantages. Read more here: https://www.thomasmaurer.ch/2019/08/how-to-install-wsl-2-on-windows-server/Windows Server 2022 (any build): Add Print Management Console to Server Manager to context menu
This is a long standing issue, eventually could also be backported to existing releases. Scenario: have a server with print server role installed add the server to server manager in Server Manager click on the left pane to to show all servers with print server roles installed right click on a print server from the server list behaviour: The context menu is missing the print management console. expected behaviour: the idea in server manager is that if you select a server from a role category and open the context menu it will show all possible MMC consoles and open them directly with the connection to the server you have selected. e.g. select DNS on the left pane in Server Manager, on the right hand select a Server listed in DNS, right click > DNS > will open DNS MMC for this server. Problem: this is only missing for Print Management Thanks for looking into this and fixing this issues (introed in Server 2012)Future of On-Prem Active Directory/ Active Directory Directory Services
What is the future of On-Prem Active Directory/ Active Directory Directory Services? Azure AD does not have the capabilities to do what AD/ADDS does and Azure AD does not work in environments where you cannot expose the systems to the internet. With Microsoft's push for hybrid everything. A large amount of important items are getting left behind.
ISSUE - Server 2022 b20234 - Configure Volume Shadow Copy is missing in context menu on ReFS volumes
Repro: open Windows explorer right click on an NTFS formatted drive vs right click on an ReFS formatted drive NTFS volume ReFS volume This entry is missing for ReFS formatted volumes. VSS is configurable on ReFS volumes expected behaviour: the entry should be added to the context menu to launch VSSUIRUN.exe Affected builds: Server 2012 and later, Server LTSC / SAC including Server 2022 reference: Shadow copies tab is missing from ReFS on Windows Server 2012 (microsoft.com) VSS Schattenkopien mit ReFS Volumes (microsoft.com)
Problems to join Debian/Ubuntu machines to a domain
Is not posible to join Debian/Ubuntu machines to a domain based on Windows Server 2025 (using realm at least) this is the error: ! Couldn't set password for computer account: XXXX$: Message stream modified adcli: joining domain xxxx.local failed: Couldn't set password for computer account: XXXX$: Message stream modified ! Failed to join the domain realm: Couldn't join realm: Failed to join the domain Domain is discoverable vía realm: root@lnms01:/home/administrator# realm discover xxxx.local xxxx.local type: kerberos realm-name: XXXX.LOCAL domain-name: xxxx.local configured: no server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: libnss-sss Tested on WS2025 build 26227 and Linux 6.1.0-21-amd64 x86_64, Linux 6.6.31+rpt-rpi-v8 aarch64 and Linux 6.8.0-31-generic x86_64. Those 3 versions of Linux joined to another doman based con Windows Server 2022 without issues.
