Forum Widgets
Latest Discussions
Windows Admin Center.exe exception (0xe0434352)
I have installed an Azure Local 23H2 one-noded stack and enabled Windows Admin Center (Preview) extension via Azure portal. Solution version: 10.2503.0.13 Node OS Build: 25398.1486 Node Azure Arc Agent version: 1.46.02809.1841 however the WindowsAdminCenter service on the node will not start: Extension Message: Executing Enable operation, SettingDnsRecords: Creating/updating DNS records, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, GettingWacPort: Getting Windows Admin Centers configured port, GettingCSPFrameAncestors: Getting Windows Admin Center configured CSP frame ancestors, UpdatingWindowsAdminCenterConfiguration: Updating Windows Admin Center Configuration, StoppingWindowsAdminCenterService: Stopping Windows Admin Center service, UpdatingInstallationTypeSettings: Updating Installation type for Windows Admin Center, UpdatingCSPSettings: Updating CSP Frame Ancestors for Windows Admin Center, UpdatingCORSSettings: Updating CORS origins for Windows Admin Center, UpdatingPort: Updating port for Windows Admin Center, UpdatingWebSocketValidationOverride: Updating WebSocket validation override settings, UpdatingTokenAuthenticationEnabled: Updating token authentication setting, UpdatingAutoUpdate: Updating auto update setting, SettingProxy: Updating proxy for Windows Admin Center, GettingWacPort: Getting Windows Admin Centers configured port, UpdatingWindowsAdminCenterConfiguration: Updating Windows Admin Center Configuration, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, TestWACAppServiceReachability: Testing reachability of Application Web Service of Windows Admin Center, GetAccessTokenForArc: Getting access token from Azure Arc's identity endpoint, GetDataFromMetadataService: Getting data from Azure metadata service, GetInstanceMetadataForArc: Retrieving the virtual machine instance metadata information, WriteCertificateThumbprint: Storing certificate thumbprint for future reference., RetrieveCertificate: Retrieving certificate from key vault using app service, ImportingCertificate: Importing Certificate to Certificate Store, StoppingWindowsAdminCenterService: Stopping Windows Admin Center service, UpdatingSubjectName: Updating WAC certificate subject name, UpdatingCertificateACL: Updating WAC certificate ACL, UpdatingServicesEndpoints: Updating WAC endpoint FQDN, StartingWindowsAdminCenterService: Failed to start Windows Admin Center service In Event viewer (system) I can see that the service starts and then stops again right after with the following error: Windows Admin Center.exe exception (0xe0434352) I have tried to reboot node and remove and reinstall extension. But the error persists. I know it is in preview but I would like to get it to work. Any suggestions?
Windows Admin Center Credential Issue
Hi, I am using Windows Admin Centre installed on Windows 11 to connect (manage) a Windows 2025 server. Both machines are not in Active Directory so workgroup mode. So I need to connect as a specific user. The issue is the credentials are not saved so it reverts back to the credentials of the gateway machine (Windows 11). Is there a way I can get it to remember the credentials after I exit Admin Center? Thanks WardExtended Network Extension it is not available in Windows Admin Center
According to this documentation https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/azure-extended-network I would like to use Extended Network Extension but it is not available in Windows Admin Center that I installed on Windows 2022. Any idea? Special version of Windows Admin Center?
Seeking Help: MS Entra ID Authentication Issue in Windows Admin Center
Hello everyone, We are looking to use the new MS Windows Admin Center for our monthly tasks, such as updating our server landscape. However, we have encountered a problem: In the new MS Windows Admin Center, form-based authentication is required, which necessitates the use of the SAM Account Name. When we switch the gateway access to MS Entra ID, access to the Windows Admin Center Gateway is no longer possible. This worked seamlessly in older versions of the Windows Admin Center. The registration as an MS Entra Application works flawlessly, but after enabling authentication via MS Entra ID, logging into the gateway fails. Has anyone experienced similar issues or found a solution to this problem? Thank you in advance for your support!
SMS WinRM DNS error
Hi, I started the cutover, old server was renamed with a new IP, new server was renamed to the OG server with IP it is now frozen at 69% due to WINrm failing due to being unable to resolve the name of the destination server. SVGB-TEST1 —> SVGB-TEST2 SVGB-TEST1(OLD) —> SVGB-TEST1 Failed cannot resolve SVGB-TEST2 (It has been renamed?) Any help appreciated.
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"
Inconsistent WinRM Connections
Hi, I've deployed version WAC 2.4.1 (v2) in the past week and have found connections to servers outside the local subnet very inconsistent. The comms side of things have been checked and we have no issues with firewalls or ACL's, and our servers are properly setup to allow WinRM connections from nodes in other subnets (Windows Firewall is also configured accordingly). The connections from our gateway server to other servers (in different subnets) do work, but when we first logon to the gateway server each day I can connect to the servers on the same subnet as the gateway without issue, but then get WinRM connection issues for the other servers. However, if I then leave it for a couple of minutes and try again, I can get connected to the servers in the other subnets without issue and get no WinRM error messages. It's a very strange issue, and all the servers concerned are on Windows 2022. Has anyone else experienced this? Thanks, Kenny
