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/
In-place upgrade possibility planned for Windows Server 2025 Datacenter Azure Edition ?
There is currently no official ISO for Windows Server Datacenter: Azure Edition that supports setup.exe /auto upgrade for in-place upgrades. Azure Update Manager does not support OS version upgrades for Azure Edition through optional features. Is anyone aware of a supported workaround?Windows Admin center V2 Authentication issue
Windows Admin center V2 "Modernized" v2.0.01 will not operate in Windows Authentication mode. If you run the installer in Remote Express mode, it is set to Forms Authentication. This mode will not allow a login with an Active Directory administrator the V2 gateway is joined to, only the local machine administrator. If you rerun the setup in custom mode and attempt to indicate Kerberos / Windows Authentication the gateway will not run. If you use the powershell admin script to run the command "Set-WACLoginMode -Mode WindowsAuthentication" on a functioning gateway in Forms auth mode, the gateway will crash/not run. Both methods of setting integrated authentication produce this .NET runtime error below. Running the indicated netsh command produces no change in behavior and no change in future .NET runtime errors. Running a netsh show command clearly displays the indicated urlacl exists. The gateway server OS is Windows 2022 STD Desktop Exp. This is not installed SxS with V1 gateway. V1 gateway operates without issue on this server when installed. Application: WindowsAdminCenter.exe CoreCLR Version: 6.0.2523.51912 .NET Version: 6.0.25 Description: The process was terminated due to an unhandled exception. Exception Info: Microsoft.AspNetCore.Server.HttpSys.HttpSysException (5): The prefix 'https://+:6600/' is not registered. Please run the following command as Administrator to register this prefix: netsh http add urlacl url=https://+:6600/ user=DOMAINHIDDEN\WAC$ See "Preregister URL prefixes on the server" on https://go.microsoft.com/fwlink/?linkid=2127065 for more information. at Microsoft.AspNetCore.Server.HttpSys.UrlGroup.RegisterPrefix(String uriPrefix, Int32 contextId) at Microsoft.AspNetCore.Server.HttpSys.UrlPrefixCollection.RegisterAllPrefixes(UrlGroup urlGroup) at Microsoft.AspNetCore.Server.HttpSys.HttpSysListener.Start() at Microsoft.AspNetCore.Server.HttpSys.MessagePump.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.WindowsAdminCenter.Core.HostingRuntime.StartAsync(CancellationToken cancellationToken) at Microsoft.WindowsAdminCenter.Executable.WindowsService.OnStart(String[] args) at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state) at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() at System.Threading.Thread.StartCallback()FEATURE REQUEST - Welcome to a new era of activation tooling - this is not an announcement
Dear Windows Server Team, with exception of Hyper-V Clusters using AVMA or Azure (HCI) Activation, I really hope this this feature request will bear some fruits. With the deprecation / revoked support and future removal of Visual Basic Scripting slmgr.vbs is certainly one of the most used scripts in this regard. Probably, next to some printmgr.vbs stuff some might still rely on. Since we believe you do not want to update Server Manager anymore, that this feature request might be helpful. Affects: Windows Client Windows Server sconfig Windows Admin Center (in Azure) does not affect (I believe since we have a config plane here) Azure Stack HCI How about bringing Windows Activation and Management over to WAC? This would ultimately make WAC more needed for average users - A possible WAC extension (since there are changes like product version and names) for Windows Server and Client activation. - A PowerShell (preferably PS7) commandlets for all of these so these could be used as an alternative to WAC plus of course used by sconfig (starting from WS 2022). proposed features of this extension / PShell commandlets: - install / uninstall key(s) - view keys - view activation status - activate key - show remaining activation key count (MAK, OEM) - show activation source (ADBA, AVMA, KMS, MAK, OEM) - links to learn.microsoft.com about AVMA generic keys, how AVMA works, ADBA, VAMT, and at last KMS for legacy systems. - more verbose error messages, if any related WAC feedback item
