The Test-OwaConnectivity cmdlet can be used to test the connectivity of all Exchange 2007 Outlook Web Access virtual directories on a Client Access server or to test connectivity of a single Exchange 2007 Outlook Web Access URL.
To test all Exchange 2007 Outlook Web Access virtual directories on a Client Access server, there must be a test Active Directory account. There must also be a test mailbox on each Exchange 2007 server that has the Mailbox server role installed that can be accessed through the virtual directories that are being tested. You can create the test accounts and test mailboxes during a step in the Mailbox server setup. If the test environment was not created during the Mailbox server setup, you will be prompted to run the script that creates the test mailboxes and test users when you run the Test-OwaConnectivity cmdlet.
If the server that is hosting the test mailbox is not available, the Test-OWAConnectivity cmdlet will return an error that might not clearly identify the problem. To avoid this, check that the server that hosts the test mailbox is running and that the mailbox is available before you run the Test-OWAConnectivity cmdlet.
If you run the Test-OwaConnectivity cmdlet on a Client Access server without using either the ClientAccessServer parameter or the URL parameter, the cmdlet will test the server on which you run the cmdlet. To test a specific Client Access server, use the ClientAccessServer parameter.
To run the Test-OwaConnectivity cmdlet to test Outlook Web Access connectivity for all Exchange 2007 virtual directories on a Client Access server, the account you use must be delegated the Exchange Server Administrator role and membership in the local Administrators group for the target server.
For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.
To test a single URL, run Test-OwaConnectivity with the URL parameter and credentials for an existing Exchange 2007 mailbox. If the URL is behind a load balancer, you cannot predict which Client Access server the cmdlet will test. Because credentials are required as part of the parameters when you use the URL parameter, you can use any account to run Test-OwaConnectivity when you use the URL parameter.
If the cmdlet encounters a virtual directory that does not require Secure Sockets Layer (SSL), it will skip that directory unless the AllowUnsecureAccess parameter is used. If the AllowUnsecureAccess parameter is used, communications between servers will be sent in clear text for purposes of the test.
The Test-OwaConnectivity cmdlet can be run as a one-time interactive task or as a scheduled task under Microsoft Operations Manager (MOM) control. To run Test-OwaConnectivity as a MOM task, the Client Access test environment must be available on the Mailbox servers that the cmdlet will test against.