GSX Blog

Exchange 2010 Monitoring: Client Access (Part 3, GSX Monitor)

Posted by Carl Drechsel on Tue, Dec 06, 2011


This is the final part of a three part series on Exchange 2010 Monitoring: Client Access. Over the last couple of weeks we looked at some of the things that are important for monitoring Client Access in Exchange 2010, this week will highlight how you can use GSX Monitor and Analyzer to automate these tasks.

How can GSX help?

GSX Monitor is a powerful agentless application monitoring solution that enables administrators and IT Managers to proactively and efficiently manage and maintain their entire collaboration environment from a single user interface. When it comes to Client Access for Microsoft Exchange GSX Monitor can help ensure that users can connect to their mailbox and information is accessible and performing as expected.


To monitor the services provided by the Client Access server role GSX Monitor will test access with different scenarios, adapted to the protocols chosen, OWA (Outlook Web Access), POP3, IMAP4, Active Sync, MAPI and the address book.

To check OWA, GSX Monitor performs a test through the Client Access Server via the service protocol; it checks Autodiscover to gain access to the mailbox location. This remote connection scenario enables GSX Monitor to determine the true availability of OWA.  GSX Monitor will model the user experience and warn if the threshold is breached. In this way GSX Monitor also ensures that Autodiscover is performing as expected.

In some environments the availability of the POP3 and IMAP4 protocols are also detrimental for sending and receiving email. GSX Monitor will test these services from a user perspective and alert in case of any performance issues.

Finally, Active Sync is essential to synchronize mobility devices with an Outlook account. To simulate this GSX Monitor will model a full synchronization with a mailbox validating the connection and monitoring its performance. For each protocol tested, an alert will be sent if there is a connection failure.

Access Performance

GSX Monitor will also measure and alert for Client Access performance issues. So not only can you be sure that your users can connect to their mailbox, you can be sure that your environment is performing as expected.

In GSX Monitor you can configure thresholds for OWA performance and also determine the status of your Client Access Server Download Task. The image below shows when you can configure these thresholds and choose the appropriate alert profile.  In addition is it here where you can set the alert profile in the event that the Client Access Server fails any of the configured tests.

CAS Alert thresholds

The current information this can be viewed in the Statistics section seen below.


Hardware Performance

GSX Monitor also measures the performance of your underlying server hardware; it also takes this a step forward and makes the statistics available for reporting and trending in GSX Analyzer.

In the screen shot below you can configure alert profiles for server status and network availability.

Hardware Settings

In the statistics section you can view a time range of gathered statistics, (Current, Today, This Week or This Month)

CAS Stats

This information is shared with GSX Analyzer, which is where you can trend and report on the gathered information.


Only by monitoring and measuring performance across these three components can you be sure that your users are able to access their mailboxes and the performance is what is expected.  By deploying GSX Monitor you can quite simply configure your alert thresholds and feel secure that your solution performs as expected.

For more information regarding Monitoring Exchange 2010, please follow the link below.

describe the image

Download our FREE eBook to learn how you can manage your CAS properly

Tags: GSX Monitor, client access server, GSX Analyzer, GSX Exchange, Exchange 2010 monitoring