Unable to get Windows Admin Center v2 (2410) to work at all
So I had the old Windows Admin Center installed and working, using Windows Credentials in my domain. There were a few issues with some of the menus that just would not work like they should, but normal updates to Windows Admin Center would fix it for a little while. They release Windows Admin Center v2 and I do an install of that with the old Windows Admin Center still installed. I am able to use the existing cert and could log into Windows Admin Center and see all the machines. Though after the Windows Admin Center v2 install, always got a ajax 500 error, when trying to connect any machine with Windows Admin Center, even the local machine. This past week, uninstall Windows Admin Center off of the Windows 11 computer that I had been using, both the v2 and v1 versions of it. I then reboot and install the Windows Admin Center v2, using custom setup. Prior to this I went into certificates on the computer and requested a web server cert for this computer using the name of the computer in DNS. My AD CS provided the new cert and I installed it as a computer certificate, under personal. Afterwards I then assigned Network Service full control of the certificate. I selected that certificate during the Windows Admin Center v2 setup and selected Windows authentication, and left everything else as default. Windows Admin Center installs and I launch it, I get to the prompt for username and password from Windows, enter the correct domain credentials and it repeatedly loops through. I went 17 tries and was never able to get into Windows Admin Center. Never got anything saying that I couldn't login, just repeatedly ask for the credentials. So how do I get this blasted thing to work? Uninstall it again, install the Windows Admin Center v1 then the v2 and try and deal with the ajax 500 issue? Nuke the entire computer and install it from a fresh Windows 11 install? Or just give up and always use remote desktop to manage all the servers, which Windows Admin Center v1 helped me half avoid?Register-WACLocalCredSSP: Failed to register CredSSP session configuration.
Every time when install Windows Admin Center (v2), I will get this error when installation accomplished. How to deal with it? Thanks 2025/08/17 15:34:48 Level=INFO ExitCode=0 Message=Enable-WACPSRemoting: Successfully configured PowerShell Remoting. 2025/08/17 15:34:48 Level=INFO ExitCode=0 Message=Remove-WACSelfSignedCertificate: Successfully removed self signed certificate. 2025/08/17 15:34:49 Level=INFO ExitCode=0 Message=Set-WACEndpointFqdn: Added Service FQDN to the hosts file. 2025/08/17 15:34:49 Level=INFO ExitCode=0 Message=Set-WACEndpointFqdn: Updated Endpoint and Service FQDN. 2025/08/17 15:34:52 Level=INFO ExitCode=0 Message=Copy-WACTempUpdaterProcessFiles: Successfully copied Windows Admin Center Updater process files. 2025/08/17 15:34:54 Level=INFO ExitCode=0 Message=Register-WACUpdaterScheduledTask: Successfully registered Windows Admin Center Updater scheduled task. 2025/08/17 15:34:55 Level=INFO ExitCode=0 Message=Unregister-WACService: Successfully unregistered Windows Admin Center service. 2025/08/17 15:34:55 Level=INFO ExitCode=0 Message=Register-WACService: Successfully registered Windows Admin Center service. 2025/08/17 15:34:58 Level=INFO ExitCode=0 Message=Set-WACWinRmTrustedHosts: Successfully set TrustedHosts to *. 2025/08/17 15:34:59 Level=INFO ExitCode=0 Message=Set-WACWinRmOverHttps: Successfully set WAC WinRM over HTTPS configuration. 2025/08/17 15:35:00 Level=INFO ExitCode=0 Message=Set-WACSoftwareUpdateMode: Successfully set WAC software update mode. 2025/08/17 15:35:01 Level=INFO ExitCode=0 Message=Set-WACTelemetryPrivacy: Successfully set WAC telemetry privacy mode. 2025/08/17 15:35:02 Level=INFO ExitCode=0 Message=Set-WACOperationMode: Successfully updated WAC operation mode: Production. 2025/08/17 15:35:02 Level=INFO ExitCode=0 Message=Set-WACLoginMode: Successfully set WAC login mode. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=The certificate subject name for the front-end endpoint has been set to admin.compute.microbin.cn. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=The certificate subject name for the service endpoint has been set to admin.compute.microbin.cn. 2025/08/17 15:35:03 Level=INFO ExitCode=0 Message=Set-WACCertificateSubjectName: Successfully set WAC certificate subject name. 2025/08/17 15:35:04 Level=INFO ExitCode=0 Message=Set-WACCertificateAcl: Successfully set WAC certificate access control list. 2025/08/17 15:35:05 Level=INFO ExitCode=0 Message=Set-WACHttpsPorts: Successfully set WAC HTTPS ports. 2025/08/17 15:35:06 Level=INFO ExitCode=0 Message=Unregister-WACAccountManagementService: Successfully unregistered Windows Admin Center Account Management service. 2025/08/17 15:35:06 Level=INFO ExitCode=0 Message=Register-WACAccountManagementService: Successfully registered Windows Admin Center Account Management service. 2025/08/17 15:35:07 Level=INFO ExitCode=0 Message=Unregister-WACFirewallRule: Successfully removed WAC firewall rule. 2025/08/17 15:35:07 Level=INFO ExitCode=0 Message=Register-WACFirewallRule: Successfully created WAC firewall rule. 2025/08/17 15:35:09 Level=ERROR ExitCode=1 Message=Register-WACLocalCredSSP: Failed to register CredSSP session configuration. 2025/08/17 15:35:13 Level=INFO ExitCode=0 Message=Initialize-WACDatabase: Successfully initialized database. 2025/08/17 15:35:14 Level=INFO ExitCode=0 Message=Import-WACExistingExtensions: No previously installed extensions to import. 2025/08/17 15:35:14 Level=INFO ExitCode=0 Message=Import-WACExistingPlugins: No previously installed plugins to import. 2025/08/17 15:35:15 Level=INFO ExitCode=0 Message=New-WACEventLog: Successfully created Windows Admin Center event log.
The SSL certificate contains a common name (CN) that does not match the hostname.
I'm after a bit of assitance for the WAC 2025 deployed in Azure. The fundamentals are setup, and I can add standalone servers, however when I add the hyper v cluster or the nodes underneath individually, and connect, it throws up the following error. There's a self signed cert bound to the cluster listener and verified working, but it still throws the below. I'm not sure what i'm missing. The cert is also in the personal store of the local nodes with their SAN within that same certificate bound to the listener. cluster.domain.com node1.domain.com node2.domain.com Connecting to remote server name.domain.com failed with the following error message : The server certificate on the destination computer (name.domain.com:5986) has the following errors: The SSL certificate contains a common name (CN) that does not match the hostname. For more information, see the about_Remote_Troubleshooting Help topic.
[msft.sme.remote-desktop v4.30.2] RDP extension fails to load in WAC 2.4.1
Description Product: Windows Admin Center v2.4.1 Extension: Connect to a server or PC via Remote Desktop ID: msft.sme.remote-desktop Version: 4.30.2 Authors: Microsoft License: MIT Issue: When attempting to launch the Remote Desktop extension, the UI never renders (infinite spinner) and the browser console reports: Uncaught SyntaxError: Unexpected token '<' In addition, certain .js module requests return HTTP 403, and the loader falls back to “null” instead of the correct main.<hash>.js. Steps to Reproduce: Install or enable the msft.sme.remote-desktop extension (v4.30.2) on WAC 2.4.1. Open WAC in a modern browser and navigate to Remote Desktop. Press F12 → Console and Network tabs. Observe: The <base href="/modules/msft.sme.remote-desktop/"> page loads, but subsequent scripts (main.<hash>.js) resolve to “null” or return 403. Console errors Unexpected token '<' Remote Desktop never initializes. Expected Behavior: The RDP extension UI should load normally, register its translation tables, and allow launching a remote session without syntax or module‐loading errors. Impact: Cannot use the built-in Remote Desktop tool within Windows Admin Center. Work-around: deinstalling the remote desktop v4.30.2 and reinstalling the old version v4.26.0 until the problem is resolved in the newer versionWindows Admin Center fail to work after installing June cumulative update
I installed June cumulative update patch in 11/6 Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2025/6/11 10:14:09 Event ID: 43 Task Category: Windows Update Agent Level: Information Keywords: Started, Installed User: SYSTEM Computer: DC-MASTER.test.microbin.cn Description: Installation Started: Windows has started installing the following update: 2025-06 Cumulative Update for Microsoft server operating system version 24H2 for x64-based systems (KB5060842) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" /> <EventID>43</EventID> <Version>1</Version> <Level>4</Level> <Task>1</Task> <Opcode>13</Opcode> <Keywords>0x8000000000002008</Keywords> <TimeCreated SystemTime="2025-06-11T02:14:09.6577485Z" /> <EventRecordID>125631</EventRecordID> <Correlation /> <Execution ProcessID="22092" ThreadID="27544" /> <Channel>System</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="updateTitle">Applies to x64-based 2025-06 Cumulative Update for Microsoft server operating system version 24H2 of the system (KB5060842)</Data> <Data Name="updateGuid">{dc616f05-dd63-47e3-9365-ff4bc05397eb}</Data> <Data Name="updateRevisionNumber">1</Data> </EventData> </Event> and after restarting OS and get ApplicationError of Windows Admin Center. Starting the Windows Admin Center service and went to browser then get error "ERR_CONNECTION_CLOSED". Log name: Application Source: Application Error Date: 2025/6/11 10:32:31 Event ID: 1000 Task Category: Application Crash Event Level: Error Keywords: User: SYSTEM Computer: DC-MASTER.test.microbin.cn Description: Faulting application name: WindowsAdminCenterAccountManagement.exe, version: 2.4.2.1, time stamp: 0x674f0000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.4061, time stamp: 0xe6128e90 Exception code: 0xe0434352 Error offset: 0x00000000000c9f0a Faulting process ID: 0x2B94 Faulting application start time: 0x1DBC4776EBA8992 Faulting Application Path: C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenterAccountManagement.exe Faulting Module Path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 91c0debe-943e-426b-a15b-646e6545e2ba Faulting Package Full Name: Faulting Package Relative Application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-06-11T02:32:31.6246703Z" /> <EventRecordID>772255</EventRecordID> <Correlation /> <Execution ProcessID="31216" ThreadID="31368" /> <Channel>Application</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="AppName">WindowsAdminCenterAccountManagement.exe</Data> <Data Name="AppVersion">2.4.2.1</Data> <Data Name="AppTimeStamp">674f0000</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.26100.4061</Data> <Data Name="ModuleTimeStamp">e6128e90</Data> <Data Name="ExceptionCode">e0434352</Data> <Data Name="FaultingOffset">00000000000c9f0a</Data> <Data Name="ProcessId">0x2b94</Data> <Data Name="ProcessCreationTime">0x1dbc4776eba8992</Data> <Data Name="AppPath">C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenterAccountManagement.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">91c0debe-943e-426b-a15b-646e6545e2ba</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Log name: Application Source: Application Error Date: 2025/6/13 10:02:59 Event ID: 1000 Task Category: Application Crash Event Level: Error Keywords: User: NETWORK SERVICE Computer: DC-MASTER.test.microbin.cn Description: Faulting application name: WindowsAdminCenter.exe, version: 2.4.2.1, time stamp: 0x674f0000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.4202, time stamp: 0xfc5b8f29 Exception code: 0xe0434352 Error offset: 0x00000000000c85ea Faulting process ID: 0x75C8 Faulting application start time: 0x1DBDC0748F8CFA8 Faulting Application Path: C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenter.exe Faulting Module Path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 80f0b279-ffe4-4584-ac22-cb879fe49864 Faulting Package Full Name: Faulting Package Relative Application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-06-13T02:02:59.6057841Z" /> <EventRecordID>793400</EventRecordID> <Correlation /> <Execution ProcessID="15432" ThreadID="11684" /> <Channel>Application</Channel> <Computer>DC-MASTER.test.microbin.cn</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> <Data Name="AppName">WindowsAdminCenter.exe</Data> <Data Name="AppVersion">2.4.2.1</Data> <Data Name="AppTimeStamp">674f0000</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.26100.4202</Data> <Data Name="ModuleTimeStamp">fc5b8f29</Data> <Data Name="ExceptionCode">e0434352</Data> <Data Name="FaultingOffset">00000000000c85ea</Data> <Data Name="ProcessId">0x75c8</Data> <Data Name="ProcessCreationTime">0x1dbdc0748f8cfa8</Data> <Data Name="AppPath">C:\Program Files\WindowsAdminCenter\Service\WindowsAdminCenter.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">80f0b279-ffe4-4584-ac22-cb879fe49864</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Even reinstalled and that won't work. Before install June cumulative update Windows Admin Center works fine and no error happened.
How to connect from windows admin center to client using winrm with port 2828
Hi all, Due to security issues I need to configure the default port of winrm on windows from 5985 to 2828 and 2829 with https. I want to configure to connect from windows admin center to client which is windows server with winrm port 2828, what should i do. Thanks all!Failover Cluster Validation Stuck
Hello everyone, I'm having the following problem when creating a 2-node HA cluster (Server 2025) using the Windows Admin Center (Gateway). Up to the point "Validate Cluster" everything worked fine. Unfortunately, the process gets stuck at "1% Gathering data about nodes". However, I can confirm that the cluster report was successfully created on the first node without any errors. Has anyone else seen something similar and, ideally, have a solution for me? I checked the following: Permissions such as CredSSP, Remote Powershell and WinRM are correctly implemented on the WAC gateway and nodes. Manually execute the PowerShell command successfully: Test-Cluster -Node $ServerList -Include "Storage Spaces Direct", "Inventory", "System Configuration"
Can't connect to WAC Gateway server - "Requested HTTP URL was not available"
v2211 I'm setting up WAC Gateway on a WS2019 server. Seems I can connect to all servers and desktops from it, except the gateway server itself. When I do, I get this message: "Connecting to remote server <server.domain.local> failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic." FWIW, I can establish a remote PS session against the gateway server from another domain member. Ran WinRM QuickConfig against the gateway server, no change. Not sure what other information to provide, but output from winrm get winrm/config/service follows, if that's useful-- PS C:\Windows\system32> winrm get winrm/config/service Service RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD) MaxConcurrentOperations = 4294967295 MaxConcurrentOperationsPerUser = 1500 EnumerationTimeoutms = 240000 MaxConnections = 300 MaxPacketRetrievalTimeSeconds = 120 AllowUnencrypted = false Auth Basic = false Kerberos = true Negotiate = true Certificate = false CredSSP = false CbtHardeningLevel = Relaxed DefaultPorts HTTP = 5985 HTTPS = 5986 IPv4Filter = 192.168.254.1-192.168.254.254 [Source="GPO"] IPv6Filter [Source="GPO"] EnableCompatibilityHttpListener = false EnableCompatibilityHttpsListener = false CertificateThumbprint AllowRemoteAccess = true [Source="GPO"]WAC Future
I'm curious what the future of Windows Admin Center is? Looking at some of the extensions like Active Directory, DNS, and DHCP you don't get a lot of feature parity with their MMC counterparts. With Linux available in just about every environment, will there every be in the future a way to manage them inside of the admin center? Will be the best way to manage this is through Azure instead of the On-Premises Windows Admin Center. Thanks.
