Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • DownloadDownload
  • PrintPrint
Share this Page URL
Help

Chapter 28. Troubleshooting with the Tes... > Using Test Cmdlets for the Client Ac...

Using Test Cmdlets for the Client Access Server Role

Several important Test cmdlets are also available for testing Client Access Servers. As shown in the following table, these cmdlets can test client connectivity to the Client Access Server, Exchange services status on the Client Access Server, whether the PowerShell remoting capability is functioning correctly, and so on.

Use the following script to create the required user for the test:

PS C:\Program Files\Microsoft\
Exchange Server\V14\Scripts>
.\New-TestCasConnectivityUser.ps1

Then run the cmdlet:

PS C:\Users\Administrator>
Test-WebServicesConnectivity

Tip

Before executing the Test-WebServicesConnectivity cmdlet, run the script New-TestCasConnectivityUser.ps1 to create a user that the cmdlet uses to test connectivity.

Tests the functionality of Exchange Web Services (EWS) on a server that has the Client Access Server role installed.

Note

Exchange Web Services replaces many of the features found in WebDAV, CDOEX, and ExOLEDB, thus potentially reducing problems with applications requiring these earlier APIs.

PS C:\Users\Administrator>
Test-WebServicesConnectivity
-AllowUnsecureAccess

Tests Exchange Web Services on the local Client Access Server, but uses an unsecured connection that doesn’t require SSL.
PS C:\Users\Administrator>
Get-ClientAccessServer |
Test-MRSHealth

Tests the health of an instance of the Mailbox Replication service on one or more Client Access Servers. In the example, you test all Client Access Servers.
PS C:\Users\Administrator>
Test-PowerShellConnectivity
-ClientAccessServer Romac-EX2
-VirtualDirectoryName "PowerShell
(Default Web Site)"
-TrustAnySSLCertificate

Tests whether Windows PowerShell remoting on a Client Access Server is functioning correctly.

Note

This example tests the PowerShell (Default Web Site) virtual directory on the specified server. The switch -TrustAnySSLCertificate is used to skip the certificate check during connection.

Tip

This cmdlet uses the same user account created when you ran the script New-TestCasConnectivityUser.ps1 previously.

PS C:\Users\Administrator>
Test-OutlookWebServices
-Identity:Maureen@romacsign.com

Tests for a connection to each service (note that quite a few are tested). It also submits a request to the Availability service for the specified user to determine whether the user’s free/busy information is being returned correctly from the Client Access Server to the Outlook client.



  

You are currently reading a PREVIEW of this book.

                                                                                        

Get instant access to over
$1 million worth of books and videos.

  

Start a Free Trial