Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-07-23

After you enable Outlook Anywhere (formerly known as RPC over HTTP) in your Microsoft Exchange Server 2010 organization, you can test for end-to-end client Outlook Anywhere connectivity in either of the following ways:

If the cmdlet test fails, the output notes the step that failed. The ExRCA also returns a detailed summary showing where the test failed and what steps you can take to fix issues. Both tests attempt to sign in to the specified user mailbox via Outlook Anywhere after obtaining server settings from the Autodiscover service.

Looking for other management tasks related to Outlook Anywhere? Check out Managing Outlook Anywhere.


  • Outlook Anywhere must be enabled on the Client Access server. For more information, see Enable Outlook Anywhere.

  • Before running the test using the cmdlet, you must create a test user using the New-TestCasConnectivityUser.ps1 script.

Use the Shell to test Outlook Anywhere connectivity

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Test Outlook Anywhere connectivity" entry in the Client Access Permissions topic.

This example tests Outlook Anywhere connectivity by setting the Protocol parameter to HTTP.

Copy Code
Test-OutlookConnectivity -Protocol:Http -GetDefaultsFromAutoDiscover:$true -verbose
The verbose parameter returns a detailed output that notes each action the cmdlet performs.

For more information about cmdlet syntax, parameters, and examples, see Test-OutlookConnectivity.

Use the ExRCA to test Outlook Anywhere connectivity

  1. From your Web browser, navigate to the Exchange Remote Connectivity Analyzer Web site.

  2. Follow the wizard instructions for testing Outlook Anywhere.

Other Tasks

After you test Outlook Anywhere connectivity, you may also want to: