WAC opens but will not connect to any servers

Copper Contributor

I installed WAC into a Win2k19 server, with all the defaults except WinRM was set up as https, not the default. I can add servers, but not connect to any of them. All the servers I put in have PS 5.x and WinRM enabled.

I get the following not-so-helpful messages:

To perform a single sign-in using your Windows account, you might need to set up Kerberos constrained delegation. -- the above command is supposed to do this, admin center is logged in as essexarc\administrator
The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".

I tried this:

Set-ADComputer -Identity (Get-ADComputer dc1) -PrincipalsAllowedToDelegateToAccount (Get-ADComputer ac1) where ac1 is the WAC server, dc1 is a server I want to manage.

Haven't found anything on the interwebs. :cry:

Thank you, Tom


3 Replies

@tlyczko2I'm facing the same.

Have several Servers from 2012 R2 to 2019 I can handle with RSAT and Powershell but WAC fails with the very same things you describe. Did not found anything yet. :(





I discovered the problem. It is a design flaw in Windows Admin Center. Here is a User Voice ticket that describes the problem and work-around.

Simply put, I'm giving FQDN server identifiers to WAC on my domain-joined laptop. It confirms that the server exists and that I've provided the correct credentials. Then it stores the server connection using the hostname of the server instead of the FQDN. Unfortunately, the cloud-based servers I'm targeting are not on my own domain - or any domain at all. So the hostname does not resolve.

The solution is for me to put the hostname into my HOSTS file with explicit IP addresses. Very obnoxious, since the cloud-servers have dynamic IP's!

@tlyczko2 The PS line you mentioned is to enable constrained delegation or single sign on. My suggestion is to install WAC on your laptop and try to connect to a server, if you can't install locally spin lup a Win10 VM and install it there. This will take credentials out of the issue so you can see what the connection issue actually is. If you can do enter-pssession to a target server then WAC should work as well.