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/Server 2025 Domain Join Error ASN.1
hallo we wanna join an appliance (cisco ISE) to our domain/forest and get an error. Domain Controllers was updated from Server 2022 to Server 2025 preview it was ok with the appliance in ad. With Server 2025 final we get this error: Test Name :Kerberos test obtaining join point TGT Description :Tests TGT Obtaining in joint point Instance :CCLOUD-AD Status :Failed Start Time :10:13:54 22.11.2024 MET End Time :10:13:54 22.11.2024 MET Duration :<1 sec Result and Remedy... Could not obtain TGT : ASN.1 failed call to system time library. Check Kerberos related AD configuration What we done in troubleshooting, yet: DNS Resoluion works. domain is resolvable NTP is ok and correct time from pdc and synced to all other DCs and Clients/Servers domain join user credentials and permission are correct We tested also with an Domain Admin User/Cred Container/OU and Computer Object Permissions/Owner rights are set to the join account. Delete and let the Appliance create a new Object did not work can anyone help with ideas?Documentation on "Microsoft.OSConfig" PowerShell Module
Hi Server Insiders, is there any documentation available on the PowerShell Module "Microsoft.OSConfig"? https://learn.microsoft.com/en-us/powershell/module/osconfiguration/?view=windowsserver2025-ps does not help that much and also "Get-Help" is not that helpfull on most of the Commands. 🙂 Thanks! Best regards, Jan
Will Windows Server 2025 kernel be resilient to Croudstrike-like failures?
I know that Windows Server 2025 will soon be ready for GA, but I'm also thinking that last week's events happened still on time to do something from MS side in order for kernel of Windows Server 2025 to be more resilient to third party (or its own Defender) influence. Can Microsoft introduce something easy, like automatic last known good kernel configuration if BSOD is detected, which would automatically restart Windows without human intervention with the previous version of antivirus, and just signal in System Event Viewer, that last antivirus update had something crashing the system?
26080 and 26063: Cloud features (like copilot) should bis disabled by default.
There are many cloud features, which are activated by default. This includes copilot, prominently visible in the lower right corner, prominently placed in Edge. In other places it includes OneDrive. Or Azure Arc (which has been rolled out and activated on Server 2019 and 2022 too without consent). Probably countless other places which I just have not yet stumbled upon. Luckily the Weather, Widgets and some other cloud AppxPackages are not there, so I have to give credit in that regard. But all those cloud-components should NOT be active by default on a sever OS. This is, from my point of view, a very serious security concern. For companies it is already difficult to trust Windows 11, and enterprises invest a huge amount of time and money to disable as many of those features as possible. Now they have to fight the same data protection and security concerns for the Server OS as well, which is not good for Microsoft. A suggestion would be a "cloud-features" collection on the "Add Features" pane within the GUI, similar to "Message Queuing" or "Remote Server Administration tools". And none of them installed. They can be listed as "available" in the Get-WindowsFeature list, but not "Installed". Pushing that responsibility to the Admins, which then will create "Server 2025 cleanup for improved security" scripts. Which pose a problem themselves. Instead Microsoft should act responsible to make the Server secure by default, which includes having all those cloud-connected tools not installed by default. The only exception where such a connection to a cloud backend, by default on, if fine is the virus protection. Thank you for reading.
