Can someone help me better understand how the PowerShell component of the Exchange Management Tools install connects to Exchange server 2016 please? I've deployed Exchange into a dedicated network where clients can only connect over port TCP:443. All other inbound traffic is blocked from clients. This seems to be fine for Outlook connectivity, but the Exchange PowerShell component fails to connect with the error:
Connecting to remote server hostname.domain.local failed with the following error message : WinRM cannot complete the operation.
I went as far as collecting a packet capture during the launch of the default Exchange Management Shell icon and all I saw was TCP:80 connection attempts from the client to the server. I went and tried to configure the PowerShell virtual directory to use an "https://" based URL which matches the installed certificate, but the default Exchange Management Shell install still attempts to connect to the internal FQDN of the server using port 80. What am I missing?
I'm not interested in allowing inbound PowerShell management over the public internet, this is only for internal connections from workstations that will be used by admins for Exchange management tasks.