Tell me about the issue and I’ll help you find the solution you need.
The "Test-OutlookConnectivity -Protocol HTTP" cmdlet fails to test the Outlook Anywhere connectivity in an Exchange Server 2010 environment
Content provided by Microsoft
Consider the following scenario:
You enable the Outlook Anywhere (known as RPC over HTTP) feature on a Microsoft Exchange Server 2010 Client Access server.
You configure only one external host name for Outlook Anywhere, Outlook Web App (OWA), Microsoft Exchange Web Service (EWS) and so on.
You run the Test-OutlookConnectivity -Protocol HTTP cmdlet in the Exchange Management Shell (EMS) to test the Outlook Anywhere connectivity.
In this scenario, the cmdlet fails. Additionally, you receive an error message that resembles the following in verbose logging:
VERBOSE: [<Time>] Test-OutlookConnectivity : Pinging RpcProxy at the following URL: http://<FQDN of the RPC proxy server>/rpc/RpcProxy.dll. VERBOSE: [<Time>] Test-OutlookConnectivity : An unexpected exception occurred while pinging RpcProxy. The most common reason for this occurring is that the IIS DefaultAppPool isn't running. Exception: The remote server returned an error: (401) Unauthorized.
This issue occurs because the Client Access server performs remote procedure call (RPC) proxy when only one external host name is used. However, RPC proxy does not support Kerberos authentication.
To resolve this issue, install the following update rollup:
2582113 Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Test-OutlookConnectivity cmdlet, visit the following Microsoft website: