Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2012-07-23
You can use the Shell to diagnose Availability service issues in Exchange Server 2010, as follows:
- For an individual user
- On a Client Access server
- Across different sites
The Autodiscover service provides Microsoft Office Outlook 2007 with configuration information that's needed to connect to Exchange. The Test-OutlookWebServices cmdlet verifies whether the Autodiscover service and the Availability service are correctly configured and can service Outlook client requests.
Before you perform these procedures, consider trying to diagnose your Availability service issues using Event Viewer. Specifically, search Event Viewer on your Client Access server for event logs that contain the event source "MSExchange Availability".
Looking for other management tasks related to managing the Availability service? See Managing the Availability Service.
Prerequisites
You must create a test account before you can diagnose Availability service issues using the Test-OutlookWebServices cmdlet. To create the test mailbox, log on to the Exchange Server 2007 or Exchange 2010 Mailbox server. Open the Shell, and then locate the Scripts directory under the installation path on the Exchange server. For Exchange 2007, the folder is located at C:\Program Files\Microsoft\Exchange Server\Scripts, where C:\ is the directory to which you installed Exchange. For Exchange 2010, the folder is located at C:\Program Files\Microsoft\ExchangeServer\V14\Scripts, where C:\ is the directory to which you installed Exchange 2010. Run the script New-TestCasConnectivityUser.ps1. Repeat this process on each Exchange 2007 or Exchange 2010 Mailbox server that is to be tested.
Use the Shell to diagnose Availability service issues for an individual user
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Availability service permissions" entry in the Client Access Permissions topic.
This example tests access to the Availability service for user User1@Contoso.com.
 Copy Code |
|
|---|---|
Test-OutlookWebServices -Identity: User1@Contoso.com |
|
Use the Shell to diagnose Availability service issues for a Client Access server
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Availability service permissions" entry in the Client Access Permissions topic.
This example tests user access to the Availability service on the Client Access server ClientAccessServer01.
| Copy Code |
|
|---|---|
Test-OutlookWebServices -ClientAccessServer ClientAccessServer01 |
|
Use the Shell to diagnose Availability service issues across different sites
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Availability service permissions" entry in the Client Access Permissions topic.
This example tests Availability service connectivity between users in two different Active Directory sites.
| Copy Code |
|
|---|---|
Test-OutlookWebServices -Identity User1@Site1.Contoso.com -TargetAddress User2@Site2.Fabrikam.com |
|
For information about syntax and parameters, see Test-OutlookWebServices.
Other Tasks
After you diagnose Availability service issues, you may also want to: