-
Title
Error: "Unable to connect to Exchange host <ServerName> using remote PowerShell." -
Description
When tying to gather information from an Exchange 2010 Server you get an error message indicating a failure to connect to Remote Powershell.
Example Error Message:
Failed to remotely gather the database copy status using Powershell.
Unable to connect to Exchange host <ServerName> using remote PowerShell.
Ensure that the task credentials have sufficient permissions to connect to the Exchange host using PowerShell.
Ensure that the Exchange server and network are functional. Failed to connect to remote Power Shell server <ServerName>.
Exception: Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.
This is usually returned by a HTTP server that does not support the WS-Management protocol.
For more information, see the about_Remote_Troubleshooting Help topic. -
Cause
Remote PowerShell requires port 80 (HTTP) be open on the Exchange 2010 Server.
-
Resolution
Allow port 80 through the firewall on the Exchange 2010 Server
or
If Host Headers are used in IIS on your Exchange 2010 Servers ad the NetBios name of your Exchange 2010 Server to the bindings of the Default Web Site in IIS Manager.
To Modify your Host Header in Server 2008.
Go to Start | Administrative Tools | Internet Information Services.
Expand your Server | Sites and select your "Default Web Site"
In the right "Action" pane click Bindings.
If the entry for port 80 has a value for the "Host Name" field you can either edit the entry and remove the value for the "Host Name" field or create a new entry for Port 80 using the Netbios name of the Exchange 2010 server as the value for the "Host Name" field.