Test-WebServicesConnectivity (RTM)

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007

The Test-WebServicesConnectivity cmdlet performs basic operations to verify the functionality of Outlook Anywhere on a Microsoft Exchange Server 2007 computer that has the Client Access server role installed.

Syntax

Test-WebServicesConnectivity [-ClientAccessServer <ServerIdParameter>] [-AllowUnsecureAccess <SwitchParameter>] [-DomainController <Fqdn>] [-MailboxCredential <PSCredential>] [-MailboxServer <ServerIdParameter>] [-MonitoringContext <SwitchParameter>] [-ResetTestAccountCredentials <SwitchParameter>] [-TrustAnySSLCertificate <SwitchParameter>] [-UseAutodiscoverForClientAccessServer <SwitchParameter>]

Detailed Description

The Test-WebServicesConnectivity cmdlet lets you test the functionality of Exchange Web Services. The Test-WebServicesConnectivity cmdlet performs basic operations to verify the functionality of Outlook Anywhere. If the test fails, a message is displayed in the Exchange Management Shell.

To run the Test-WebServicesConnectivity cmdlet, the account you use must be delegated the following:

  • Exchange Server Administrator role and 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.

Parameters

Parameter Required Type Description

AllowUnsecureAccess

Optional

System.Management.Automation.SwitchParameter

This parameter enables the Test-WebServicesConnectivity cmdlet to continue to run over an unsecured channel that does not require Secure Sockets Layer (SSL).

ClientAccessServer

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

This parameter specifies the Client Access server to use when the Test-WebServicesConnectivity cmdlet is run.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the domain controller to use to write this configuration change to the Active Directory directory service. Use the fully qualified domain name (FQDN) of the domain controller that you want to use.

MailboxCredential

Optional

System.Management.Automation.PSCredential

This parameter specifies the mailbox to use when the Test-WebServicesConnectivity cmdlet is run.

MailboxServer

Optional

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter

This parameter specifies the identity of the Exchange 2007 Mailbox server on which the test will be run.

MonitoringContext

Optional

System.Management.Automation.SwitchParameter

This parameter specifies whether the test result is passed to Microsoft Operations Manager (MOM). If this parameter is set to $true, the test result is passed to MOM. If this parameter is set to $false, the test result appears only in the command line.

ResetTestAccountCredentials

Optional

System.Management.Automation.SwitchParameter

The ResetTestAccountCredentials parameter resets the password for the test account used to perform this command. The password for the test account is typically reset every seven days if you're using Microsoft System Center Operations Manager to manage your Exchange environment. Use of this flag forces a password reset at any time if it's required for security reasons.

TrustAnySSLCertificate

Optional

System.Management.Automation.SwitchParameter

This parameter allows the test to use any SSL certificate that is available.

UseAutodiscoverForClientAccessServer

Optional

System.Management.Automation.SwitchParameter

This parameter specifies whether the test should use the Autodiscover service to locate the Client Access server.

Input Types

Return Types

Errors

Error Description

 

 

Exceptions

Exceptions Description

 

 

Example

The following code example tests the Exchange Web Services on the local Client Access server and allows the test to use an unsecured connection that does not require SSL. A default test account will be used.

Test-WebServicesConnectivity -AllowUnsecureAccess