Forum Discussion
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...
22 Replies
I had this problem in WAC 2511. First, took me forever to figure out that the cert had to be RSA (ECC not supported) and can't be a wildcard. Well it could be a wildcard, but also must have the FQDN of the WAC as a SAN. After issuing a new cert using RSA and with FQDN in Subject and SAN, able to start service and access web interface without error.
However, was getting the AD error when searching for servers. Found an application log that mentioned the cert couldn't be found because it was trying to search by email attribute. Our standard config is to populate email, organization, department, city, state, and CN. However, WAC needs just the CN in the Subject and the DNS in SAN. Once I issued a cert with just that, I was able to install with that cert and able to start and search AD without issue.
Application: WindowsAdminCenter.exe CoreCLR Version: 8.0.2125.47513 .NET Version: 8.0.21 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException: The requested certificate E=email address removed for privacy reasons could not be found in LocalMachine/My with AllowInvalid setting: False. at Microsoft.AspNetCore.Server.Kestrel.Https.CertificateLoader.LoadFromStoreCert(String subject, String storeName, StoreLocation storeLocation, Boolean allowInvalid) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Certificates.CertificateConfigLoader.LoadFromStoreCert(CertificateConfig certInfo) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Certificates.CertificateConfigLoader.LoadCertificate(CertificateConfig certInfo, String endpointName)I made some tests with the revised WAC version (several installs with different settings) and found that I don't need to change anything anymore after an install, so the situation has improved a lot; the only issue I had was the certificate that sometimes didn't work after some installs (the browser reported an error with missing parameters in the certificate) though I didn't change or re-issued it...
In my case, the problem was that I reused the previous certificate, from the server that was replaced!
I didn't notice that the previous server FQDN was included in the WAC certificate, and also not the new one.
So, i created a new certificate with the new server FQDN and same my other DNS-records, installed WAC again and used the new Thumbprint = Now OK!
In my case running WAC Current version: 2.4.1 on 2025-server!
And for me no need to change network service account.Same problem here. I set service run under system, restart server dont help.
Any other solution?? This new admin center is full of pain....Any resolution on this yet?
same problem
Same issue. Tried multiple installs, changing the account the service runs under from network to local, tried reseting computer password using powershell to confirm machine is trusted. Managed to get this working in our dev envirronment once, have not been able to get it setup again in dev or live. Seems like it's never been tested and we're expected to alpha test this detritis for them.
Open services, find windows admin center, go to the log on tab. It'll probably be set to network service by default, switch it to local system and restart the service.
Thanks, worked for me.
Thank you sooo much! That worked on my environment!
Thanks! Adding computers via AD works now. But changing gateway access (adding groups) still not works. Getting "Error: System.DirectoryServices.Protocols is not supported on this platform" when adding groups in format "domain\group", getting ajax error 400 when adding goups without "domain\".
Brand spanking new 2410. Ran into troubles way back in the day and never got resolved. Now... Right out of the box and can't do the simplest of tasks. Is there any QC on this stuff, or is it spaghetti against the wall time?
Same issues here
I get the same issue, I had to back out of this upgrade due to this. Been using WAC since it first came out and this install process was simultaneously the smoothest upgrade experience and the worst post upgrade experience of all.
