Forum Widgets
Latest Discussions
Issues with server on domain
So we are having an odd problem with intermittent connectivity on Windows server 2022 install. It's a repository server, that is also used for dev work so at any one time we have users connected to it from different groups in the US, as well as outside the US (India & Australia). It is located on on our US domain, and users connect using their AD credentials. The problem we are seeing is that users outside the US can't connect to the system randomly, but most of the time users in the US can. However occasionally they have issues too so it's random. So far we have tried the following to address it, but are still seeing problems: - We've tried removing and rejoining the domain. - DNS settings are correct, and are the same as other WS2022 (and 2016 servers) that are also on the domain. - We are using a corporate NTP server, which is also used by the corporate DC's. - Firewalls aren't blocking traffic. - Most recently about 3 weeks ago I did see some GPO errors, so did do a GPO update. This seemed to help until this past Friday when the issue occurred. - We are fairly thorough with maintenance as we have a monthly window after MS patch Thursday to update and reboot the system at least once a month. We have a secondary site where this system is replicated, and both of of the vm's were made from the same template...but this system doesn't have the same issues. Any ideas on what we could be missing or what to look at next?
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?[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 version
Windows Server 2019 Administrator access gone
I recently was using Windows Server 2019 Evaluation version, everything working great. Then purchased full license and upgraded it with the license. Now I am unable to do anything because the Administrator account is inaccessible. I can't even restart the server without having to power off. Any help would be appreciated.Windows 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 do I create a new certificate for Windows Admin Center??
I just now observed that our internal WAC certificate was only two months old and it's already expired. Can I simply create and use our own self-signed certificate and use it?? Do I install it like normal certificates within the Certificates MMC and WAC will automagically use it?? Thank you, Tomwinpty error accessing powershell tab
WAC Ver: 2.4.1 running on Windows Server 2022 I can access and perform all other WAC functions on the remote connected server (Win 2022) but when I try to access the powershell tab and click 'connect' I am met with a "Session End: click 'Connect' to reconnect." error. Clicking 'Connect' just cycles the same error. The windows event log error is as follows: Category: Microsoft.WindowsAdminCenter.Common.ServiceLog EventId: 414 SpanId: d138bcb891359bec TraceId: f373ad4711a131524c5c01e8b6a2e591 ParentId: bb6d22e32ab6da73 ConnectionId: 0HND3HPV5LDCV RequestId: 0HND3HPV5LDCV:00000001 RequestPath: /api/PseudoConsole/nodes/fakeservername.com/powershellconsole ActionId: b3f1dbd0-b87e-49e5-a13d-ba66e8d18af1 ActionName: Microsoft.WindowsAdminCenter.Controllers.PseudoConsole.PseudoConsoleController.PowerShellConsole (Microsoft.WindowsAdminCenter.Controllers.PseudoConsole) Failed to open winpty (8), Columns=194, Rows=44 The internal windows firewall is turned off completely, and outside of WAC, initiating a "Enter-PSSession -ComputerName" command in powershell verison 7.5.1 works fine, I can run commands on the remote server from there. Any ideas?
Windows Admin Center 2410: cannot add computers
After a fresh installation of Windows Admin Center 2410, I cannot add any servers, clusters, PCs etc. WAC gives me "You can add this computer to your list of connections, but we can't confirm it's available" when I enter a computer name (either of FQDN or computer name alone). When I change to the Search Active Directory tab, I get: "We can’t search Active Directory because the Windows Admin Center computer isn’t joined to an Active Directory domain. It’s also possible that your account doesn’t have permission to read from Active Directory." The account I use is a domain admin, and the server running WAC is definitely joined to the AD DS. The server had the previous version of WAC installed where everything worked. Now, with the new version, that's no longer the case...
