MicrosoftHello, I'm excited to start using this tool to manage (and delegate management) of our windows 2019 AD servers. I have it set up on a lab where there are 4 systems, a 2019 gateway server, and 3 2019 servers running active directory. 2DC's are core and 1DC is desktop experience, the gateway is desktop experience and that is where I'm running my browser to connect from. I'm seeing the same problem with connecting to any of the servers. From the start I have received the same error message when trying to connect to one of the systems i've added to manage. Note that remote powershell is working between the nodes, they are all able to be managed through a server manager group in the server manager console, and I've run winrm quickconfig on all nodes. The install msi I used to install WAC on the gateway host is WindowsAdminCenter1910.2. The error message being thrown no matter what I do when attempting to connect with WAC is:
Connection error Connecting to remote server w2k19-1.example.com failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
For the last 10 days I've been working on getting the actual connection to a host to work, I have read a large number of blogs and postings trying to get things to work, including stepping through the about_Remote_Troubleshooting and enabling the group policies indicated for the service, access, firewall, etc. As I have progressed through the troubleshooting I've also applied the indicated kerberos constrained delegation discussed in the user access sect of the documentation of the following in powershell: Set-ADComputer -Identity (Get-ADComputer w2k19-1) -PrincipalsAllowedToDelegateToAccount (
Get-ADComputer w2k19-gw)
I've repeated that for each node (-2 and -3).
The Gateway node is in the same subnet as the hosts I'm trying to manage. The one esoteric thing is these are on a /27 subnet, but I cant imagine that would be a problem as all networking is functining and all the domain controllers are replicating properly between each other, and powershell remote is working between all nodes. I'm using chrome on the windows 2019 gateway because MS Edge does not work on 2019 based on the documentation.
All the nodes are joined to the domain. They all have proper CA issued certificates installed and working, the Gateway is running WAC on HTTPS using the installed CA issued cert. Everything has been rebooted. I have no idea where to go next to isolate why things are failing... thanks in advance for any pointers.
