MICROSOFT EXCHANGE MAIN CHALLENGES IT MANAGER HAVE TO FACE GSX SOLUTIONS

Transcription

1 White paper September 2011 GSX SOLUTIONS MICROSOFT EXCHANGE MAIN CHALLENGES IT MANAGER HAVE TO FACE Project: Exchange 2010 Monitoring an reporting Targeted Product: GSX Monitor [ A d r e s s e d e l a s o c i é t é ] Page 0

2 Summary Executive Summary: GSX Solutions in a Nutshell / Challenge 1: How to manage User Connectivity?... 4 Monitoring the Client Access (CAS) role... 4 Monitor the accessibility of your DB Store / Challenge 2: How to manage High availability? Myths Principle Main view Replication tests Summary view DAG How to calculate your SLAs / Challenge 3: How to manage Performance? Improve the response delay in case of incidents Customer experience measurement Check your performance indicators: long term statistics / Challenge 4: How to manage Storage Capacity? Disk management DB Stores Management Conclusion Your Next Action Figure summary North America: / Europe:

3 Executive Summary: GSX Solutions in a Nutshell GSX Solutions is the global leader in proactive, consolidated monitoring and analysis of enterprise collaboration environments including Microsoft Exchange, Microsoft Sharepoint and Blackberry Enterprise Server, as well as LDAP and SMTP ports, and any URL. Based in Switzerland, GSX Solution is specialized in agentless solutions which enable administrators and IT managers to: - Control and secure the health of their collaborative environment - Analyze the performance of the environment as experienced by the end users - Produce technical and management level reports regarding SLA s and their key performance indicators GSX Solutions flagship product, GSX Monitor and Analyzer, gives customers insight into what s happening inside their collaboration environment. Using the data created in GSX Monitor and Analyzer allows organizations to improve the performance of the environment and deliver business value. This includes Increasing control through a visual dashboard of the current status of all the SharePoint servers and services in your environment. Underperforming servers are clearly flagged for immediate attention. Reducing cost by targeting specific areas for corrective action, and by highlighting problems that need attention before they stop business people from working. Ensuring performance of the SharePoint SLA, through correlating input factors with the overall SLA. Troublesome areas are highlighted for quick resolution. Read this white paper to learn how GSX Solutions resolves the 4 main challenges that Administrators and IT Managers have to face and how it adds business value for the entire organizations. Monitoring the collaborative environment is not limited to Microsoft Exchange. With only one solution, no agent and no matter which type of server you work with, GSX Monitor enables you to supervise your Exchange 2003, Exchange 2007, Exchange 2010 whatever role they have SharePoint 2007 and 2010, your critical websites, Active Directory availability and your Blackberry Enterprise servers. North America: / Europe:

4 Thus, Figure 2 shows you how GSX can give you the real time status of your entire environment. Figure 1 GSX Monitor Main view Let s see now how GSX can provide a solution for each of the four big challenges every Exchange administrator and IT Manager face: User connectivity, High availability, User experience Infrastructure capacity North America: / Europe:

5 1/ Challenge 1: How to manage User Connectivity? User Connectivity is one of the main challenge IT has to manage Using client Access role and DB Stores Monitoring the Client Access (CAS) role The CAS provides user connectivity and is fundamental in order to enable users to connect to their mailbox regardless of the method: Outlook Web Access, POP3 and IMAP4 protocol or Active Sync. Similarly, critical services like AutoDiscover, the Offline Address Book or DB Store must be accessible for the user to get to their or their address book. These services are crucial and that is why GSX Monitor performs a battery of tests in order to alert you in case of problems. In the Server Settings section of GSX Monitor, we are going to specify what tests GSX Monitor will perform against servers and services and what the alerts settings will be. In the 4 th figure, there is an example of Exchange 2010 CAS server monitoring. North America: / Europe:

6 Figure 2 Client Access Server role monitoring settings The column on the left gives you a quick view of the different environments you are monitoring: here we see BlackBerry, URL, Active Directory, Exchange and SharePoint. The main window shows the monitoring settings for the chosen server type. The first columns are configured properly for GSX to connect to the servers. The Advanced column enables you to set the Windows services previously discussed. You will then indicate the version of your Exchange servers: 2003, 2007 and Below will see here how you configure monitoring for a 2010 server. The Roles column: for the selected server (blue line), you can see there are 3 roles selected. The roles this particular server hosts are Mailbox, CAS and HUB. For each of these roles, GSX will perform a series of tests to make sure everything working as expected. To monitor the services provided by the client access role on the server, the next column proposes different options. GSX Monitor will test the CAS server with different scenarios, adapted to the protocols we want to check, OWA (Outlook Web Access), POP3, IMAP4 and Active Sync. OWA for Exchange 2010 is very commonly deployed. A degradation of performance of this service can have a large impact on users. North America: / Europe:

7 To check OWA, GSX performs a test through the Client Access Server via this protocol; it performs an AutoDiscovery 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. On top of that, GSX Monitor will ensure that the Autodiscover service (automatic settings of the users profiles) is performing as expected on the client access servers. Any disruption of this service can be detrimental to customer connectivity. The availability of the POP3 and IMAP4 protocols are also detrimental for sending and receiving for some Outlook users. 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 every mobile device with an Outlook account. To monitor it GSX Monitor will model a full synchronization with a mailbox. Once again, this simulation is crucial to know if the Active Sync service is performing as expected. For each protocol, an alert will be set off if the test fails. Alert profiles will be discussed in greater detail later in this document. In the next column CAS ALERTS, administrators can configure alert profiles for specific issues with the CAS. This CAS ALERTS column opens the tool box located in the center of the figure 5: North America: / Europe:

8 Figure 3 CAS alerts settings Monitoring these three types of Alert (CAS down, OWA task Queue and CAS Task Queue) provides a very good indicator on the performance of the offline address book or the calendar synchronization tasks. Each of these alerts is sent to a profile which can be configured to alert in a variety of ways ( , pager, popup, sound, program, trap SNMP or direct SMS). Finally, GSX performs a MAPI connectivity test (figure 4) to a specified mailbox in order to verify that users can reach their mailboxes on this server and through the Client Access Server. These tests verify customer connectivity end to end by checking client access mailbox server availability and the health of the mailbox database. North America: / Europe:

9 Monitor the accessibility of your DB Store Mailbox availability is dependent on the availability of the database store. Therefore GSX Monitor ensures the DB Stores are present on servers and accessible to the user: in doing so we validate the availability of the Mailbox role. Several solutions are possible here: The Main View of GSX Monitor allows for a quick status check on the essential functions of the Mailbox server role. Figure 6 displays the information below: Figure 4 Main View of the Client Access role and Mailbox roles GSX Monitor will alert when problems occur with the Microsoft Exchange services, the DB Store, mail routing and queue thresholds. When you have DB Store in a failed state on the server GSX Monitor will update the main view. The LED turns red and an alert is sent. Another way to check the health of the DB Store is to open the consolidated view in the Statistics tab. North America: / Europe:

10 Figure 5 consolidated statistics view for Mailbox server The left column displays all servers in the Exchange environment classified by roles. Under the information heading we can see that this server hosts both the Client Access and Mailbox roles. The CPU and RAM availability are displayed next to each other. Under the CAS heading we see the status of the CAS connectivity test, with the selected protocols and real time statistics about the OWA response delay, number of current connected users and the task queues corresponding to the Offline Address Book Synchronization. Under the Mailbox heading the following mailbox role information is displayed: Was the MAPI connectivity test a success? How many DB Store on the server? What is their state? (Fail, healthy ) How many active connections? Number of users on the server? Database size Below in the DB Store list, we see at a glance their current status, the status of the Content Index, size, white space as well as the last log inspection and the last backup. GSX Monitor gives you a real time every indicator enabling you to be certain that your service functions, your users can connect the service and send and receive . If any one of these tests fail you will be alerted. North America: / Europe:

11 2/ Challenge 2: How to manage High availability? Knowing that your users can connect and use the messaging services is not enough, you need to monitor and ensure high availability. To ensure availability of the messaging service and guarantee the level of SLA agreed with your customers the implementation of a highly available and redundant infrastructure is simply, not enough. To start with, from a technical point of view it is not uncommon after an implementation of HA platform to realize that there still exists a number of Single Point of Failure which could, under certain circumstances, result in service interruptions. Your team must be able to anticipate problems and incidents at the DAG level, the Exchange 2010 High Availability service. GSX Monitor enables you to reduce the overhead cost when monitoring your Exchange 2010 infrastructure and during maintenance Myths Myth: Thanks to High Availability I reduce maintenance costs Many people believe that a highly available solution will reduce maintenance costs and help prevent breakdowns. The reality is that by the HA, the number of components to be managed is at least doubled and must now also be monitored and maintained with patches, updates etc. Myth: High Availability With no more breakdowns! Redundant solutions avoid interruption of service in case of failure but does not resolve the cause of the outage. If repaid incident respond and repair steps are not taken the service can be interrupted due to failures. Resulting in downtime for your customers and a negative impact on their business HA allows IT to sleep better at night as long as the solution is monitored properly. Indeed, it is not enough to ensure that the server is up but that every element from start to end which allows access to the service works. Your server may be up and running, but is it delivering the service that it is suppose to? In the case of failure it must enable identification and a rapid response on the impacted component(s) to ensure the continuation of a highly available system. It is therefore necessary to analyze the infrastructure proactively and perform required maintenance before the blackout occurs. North America: / Europe:

12 Principle High availability in Exchange 2010 occurs at different levels: At the Client Access level, with a Client Access array performing load balancing. The DAG which manages high availability at the DB Store level. Let s focus right now on the database and high availability of the mailbox. To be sure your DAG is performing as expected, two majors factors have to be taken in consideration, one operational, the other functional. Thus, is database replication occurring as expected? Does each DB Store have at least one passive copy in good condition? Checking these elements reports two types of events: errors of inaccessibility and warning. Errors of inaccessibility jeopardize high availability functionalities and can have a direct impact on business. A warning will be returned when soft fail occurs for proactivity to avoid a direct impact on user activity. GSX Monitor will differentiate between these two possibilities and will warn you to prevent an impact on the customer experience. Main view Let s return to the Main View and study a DAG case with two mailbox servers, each of them containing active and passive copies. North America: / Europe:

13 Figure 6 Main view: LED related to the DAG As we have seen before, GSX Monitor first displays the Exchange services status, then the availability of CAS role if it is present on the server, and finally the status of the DAG on the third LED. This LED is split into two parts. The left part is dedicated to the overall DAG status. If each active copy has at least one functional passive copy within the DAG, then the DAG is considered as operational and the left half of LED is displayed green. If an active copy does not have a healthy passive copy then high availability is not assured. In this case the half LED becomes red. In our example of a DAG with two mailbox servers we now look at the right half of the LED. If for this server all of the DB store tests are successful the right half of the LED will be green, if one of the DB store tests fails the right half of the LED will turn red. For server one all database copies are healthy. For server two there one database copy is in a failed status. Thus, in this example, for at least one of the DB Stores there is no healthy passive copy. High availability is not available for all the DB Stores in this DAG. The left half of the LED will be red. North America: / Europe:

14 For interpretation we read: Server 1: The DAG is down but all the DB Store on the server are OK Server 2: The DAG is down and one DB Store has failed on the server If the DAG had 3 servers and there were at least one healthy passive copy for the server 1, then we would have a green DAG LED (Left) overall with a half a red LED on the second server which has a failed DB Store copy status. In this case GSX Monitor would have displayed a warning and not an error. We have seen that the Main View gives information in real time for the high availability status of your Exchange 2010 architecture. Let s see now how the tests are performed. Replication tests To check if the DAG is fully operational, the functional approach is not enough. You have to perform more technical tests to check that the DB Stores are not only healthy but also perfectly replicated to the copies within the DAG. With GSX Monitor you can set specific alerts in the Replication Health Alerts section under the Server Setting tab. Figure 7 Warning Alert and error activation This screenshot shows how GSX Monitor manages the pending and dead mail queue thresholds as well as the Replication Health Alerts for the DAG. It is here that GSX Monitor will perform dozens of tests that are executed line to line from a remote session. The tests performed will determine that replication between the databases is performing as expected. North America: / Europe:

15 If one of these tests error, replication is not functioning properly and a DAG Down alert is sent, the Main View LED will be red. If one of these tests returns a warning (working in degraded mode) GSX Monitor will display a warning for the DAG. Replication is working but there may be potential issues. GSX Monitor will send a warning when replication is too slow, if failover ability is impacted, if the quorum is not available (but not necessarily corrupted), or if there is an issue with file share availability of the quorum. Here are the items that are tested by GSX Monitor: Cluster service: check that the cluster service is available on the DAG or local server Replay service: check that the replication service is available and functional Active manager: check that the Active Manager is in a valid role (primary, secondary, stand-alone) Task RPC Listener: check the availability of the RPC task TPC listener: check the availability of the TCP log copy task Member Status : check that the DAG members are all available Cluster Network: check the availability of the cluster network Quorum Group: check that the quorum group is online and available File Share Witness: check that the witness server (and the witness directory and share) of the DAG is reachable High availability validation: check that there are at least 2 healthy copies if only one exists. North America: / Europe:

16 Summary view DAG To provide all information on DB Store status, as well as copies present on the servers, their size, etc. GSX presents a summary view of your DAG in the Statistics section. Figure 8 DAG view / Stats This view gives essential information to follow your DAG. In the first board, you can find the DAG servers and their role status. This view gives crucial information on the status of each DAG. In the first dashboard, you can find the servers belonging to the DAG and the role status. Below, for each server there is a view of the status for each of the DB Stores per server containing the number of copies of the DB Store in the DAG, the name of the server where the active copy is, the list of the servers with healthy copies as well as the list of the servers a copy in error. For each DB Store, we display information on size, the date of the last Log inspection and the date of the last full backup. This view enables you see in real time critical information related to the DAG displaying the overall health of your DAG. North America: / Europe:

17 How to calculate your SLAs GSX Monitor provides information in real time about the availability of your DAG. You can have this displayed graphically across your servers in a 3 days arrangement in the Graph section of GSX Monitor studied in the next section. It can be crucial to be able to calculate the availability of your DAG during longer periods, several days, weeks or months to provide SLAs reporting to your management or your customers. GSX Analyzer collects all data on DAG availability and enables you to graph it on demand or to deliver automatic customizable reports that can be directly sent to the people you choose, according to a calendar you can define. Figure 9 DAG Exchange cluster availability during one week Green graph: Cluster Up 24H without maintenance Brown graph: Cluster down 24H without maintenance North America: / Europe:

18 To know that high availability is functional is a critical point. You can rest assured that the services are available and as we have seen before, the customer can connect to the data. The development of high-availability messaging and reporting solutions has become vital for all size of businesses since messaging is now business critical. High availability also brings new challenges but is only part of the solutions that will allow you to commit and deliver on service levels to your users / customers. The implementation of monitoring and analysis tools is required to ensure timely and focused action issues that could potentially impact on service and validate changes that are required to be made in this type of high availability infrastructure. The question is how long does it take? What is the performance of Exchange as delivered to your customers? If you have an internal SLA, the measure of the performance is as important as the service availability. North America: / Europe:

19 3/ Challenge 3: How to manage Performance? Performance management involves several aspects. It is critical to have the calculation of service performance and the means to analyze failures while responding quickly to the issues at hand. Improve the response delay in case of incidents In order to determine if the service you offer is performing as expected or not, you need to be able to measure it through simulating user activity and collecting appropriate statistics. GSX Monitor tests your servers in the different ways. As we have seen before, it performs some tests and designs scenarios utilizing PowerShell, executed on the server remotely from the workstation our tool is installed. These scenarios allow you to measure the time of response of your Microsoft Exchange environment for particular events. The accurate measure of the performance depends on the frequency with which you will scan your servers. Figure 10 shows where the parameter is defined. Figure Microsoft Exchange Server Setting North America: / Europe:

20 All platforms that GSX Monitor monitors work exactly the same way for setting the scanning configuration. A scan frequency is defined, then a retry frequency in case of an issue. We then set the waiting threshold before which GSX Monitor sends an alert to your administration teams and/or support teams during the working hours or during the non-working hours. We will see how to define the alert sending profiles later on. These parameters will have an impact on the frequency with which the system will detect an error as well as when the alert is sent. If you set the frequency too short you may receive insignificant alerts while setting too much time between scans can cause a response delay when an incident occurs. Each environment is different. If an event occurs, GSX Monitor makes available several tools which enable you to look into them causes of errors and make decisions to resolve them immediately. When you right-click on the Main View any Microsoft Exchange Server, you can open the Exchange Manager. Exchange Manager has a few functions we are going to look here. The first window is for mail queue management. North America: / Europe:

21 Figure 11 Exchange Manager Mail Queue From this toolbox you can manage all of the mail queues. They appear in the upper window when you click on Refresh. For each of the queues, you can Show mail, Resume Queue or Suspend Queue if there is an issue. Show Mail will display all in the queue and it will enable you to take action on them. You will be able to Resume Mail, Suspend Mail, Remove Mail with NDR or simply Remove Mail. Thus, if a specific mail is stuck in the queue, you will be able to take the necessary action to restore the service. Another function of the Exchange Manager is the Server Health check. North America: / Europe:

22 Figure 12 Exchange Manager Server Health Check Here, GSX Monitor performs a number of tests on the server which are complementary to the tests performed in the Best Practices Analyzer by Exchange. These checks are very intensive and should be used primarily in the debug phases of major problem. The checks performed are thorough and complete (services, Autodiscovery, certificates, etc.). It is a powerful way for your team to find faults within the systems and to respond to it quickly. In order to quickly determine where issues have and are occurring, GSX Monitor provides very detailed graphs. Here is an Access Time graph on a Microsoft Exchange 2010 server: North America: / Europe:

23 Figure 13 Access Time Exchange 2010 These are real time graphs. Each scan registers a point on the graph. You can see the last 3000 scans on a whole series of system, performance, volume and usage statistics. A list of measured statistics is provided in the appendix. Finally, another way to optimize your performance and your incident response is to be able to compare your servers against another for given performance stats in order to get insight into their respective performance related to typical performance and to the published SLA. Here you have the overall status of the reporting application (GSX Analyzer) installed with GSX Monitor. Figure 14 Overall status GSX Analyzer The orange line corresponds here to your contractual value; the purple line indicates your current average and the bars represent the value, for a given statistic reached by one of your North America: / Europe:

24 servers. It is very easy to directly target the resources you need to focus on to improve the general state of the service you offer. Working on the performance is a mix between reactive and proactive actions. Managing the perceived performance of your service involves measuring it from an external point of view executed automatically as a recurrent task (sending and receiving mails). This is accomplished in the Mail Routing component. Customer experience measurement Among the multiple ways that we measure the customer experience, one of the simplest and the most powerful is the automatic mail routing check. Figure 15 Exchange mail routing North America: / Europe:

25 In this section you can set scenarios to check all of the routes in the Exchange system. You just have to set a cycle and define a mailbox which sends an . The can be sent on another mailbox of your infrastructure, on an echo website (which automatically sends you the mail back) or directly to a BlackBerry device which would then send a you a delivery status notification (we will see that in the BlackBerry section). GSX Monitor gives you the ability to test sending internally, externally and to mobile devices in order to check the availability of all layers of the messaging infrastructure. it is possible to test for example all SMTP traffic and to have performance statistics for with or without attachments (to test how the volume of actual messages impact the systems performance). All these statistics are displayed in real time: Figure 16 Mail Routing Statistics This view gives a good insight of the accessibility of the platform. GSX Monitor presents a true global view of the performance of your messaging environment. All of these statistics can be graphed and analyzed in the Reporting section. North America: / Europe:

26 Check your performance indicators: long term statistics Having a real time view of your performance is essential. Being able to compare the indicators in the correct time line, between the servers is very useful too. We have seen that GSX Analyzer gives you the possibility to compare your servers according to a given statistic calculating the average and automatically displaying the healthy and the not healthy servers. You can also use the reporting functionality to graph the evolution of the systems performance indicators and the mail routing indicators over long periods. We can see in the last part of this document how automatic reporting works. These long-term reports enable you to follow the improvement or the deterioration of one or several servers performance over a week, month or yearly period. The reports are available in GSX Analyzer or automatically sent to the people or groups you choose. Figure 17 CPU performance graph from GSX Analyzer Managing the capacity of your environment is critical to the long term performance of your messaging systems. Is there enough disk space on the Exchange server? Is the CPU at capacity? Is there high memory utilization? All of these questions can be answered using the statistics you can find in the graphing or reporting section we are going to see. One topic we will look into is storage capacity. North America: / Europe:

27 4/ Challenge 4: How to manage Storage Capacity? Managing storage capacity depends on a great number of parameters. In GSX Monitor and Analyzer we efficiently control and alert in case of threshold crossing. First of all, let s start with the basics: disk capacity management. Disk management GSX Monitor warns you when there are disk capacity issues through several methods. First method: the Main View Figure 18 Main View Disk Space Alert In the Main View, we know that the first left LED gives visual representation of the availability of Exchange services on the server. This LED can also be a source of vital information when a disk capacity problem occurs. In figure 17, the LED is split. The right half corresponds to the disk alert threshold and informs that an alert has been sent to the appropriate teams. How do we set the threshold? To answer this question all you need is to get into settings by double clicking on the server in question. North America: / Europe:

28 Figure 19 Exchange Disk Space Setting For each server, threshold alerts can be defined both in megabytes and in the remaining percentage of space for all of the disks or for a selection of disks you want to monitor giving them different thresholds in megabytes or in remaining percentage. If the threshold is crossed, an alert is sent and the Main View half LED will change color. Second method: Real Time Disk Space Graphs North America: / Europe:

29 Figure 19 Disk Space Graph Here we display real time monitored disk status, utilized and remaining space, as well as the alert threshold you have set. Managing your disk capacity requires alerting in case of crossing the threshold in order to be reactive when a failure occurs, graphs to understand the load balance of storage between different disks and also middle and long term trending to anticipate purchasing needs and new storage arrays to implement. GSX Analyzer consolidates its reporting and enables you to track your disk usage trends. This functionality is available directly on the website or automatically through an exportable in PDF format. These reports will allow you to have precise insight into capacity trends. North America: / Europe:

30 Figure 20 Disk Space Reporting You can consult daily, weekly or monthly reports that display essential statistics to succeed in managing disk capacity. While disk capacity is the visible side of the iceberg for they often cause significant failures Database stores shouldn t be forgotten. DB Stores Management GSX Monitor provides several ways to manage database stores. We have already seen how to ensure availability and the health of high availability, let s see now how to manage database store sizes to optimize the infrastructure. For each server that hosts database stores you can set alerts in case of a predefined threshold. As we can see in Figure 21, we can also define an alert for white space in order to be alerted when database compression is needed. In this way, you are alerted when action is needed for the optimization of your messaging infrastructure. North America: / Europe:

31 Figure 21 Database store alerting You can find the data for database statistics displayed here Figure 22 Consolidated statistics view for database stores Figure 23 Consolidated statistics view for database stores For each mail server we have the database store list and for each list, its size, the white space available, the number of mailboxes and their average size in real time. The average size of the mailboxes is coupled with a GSX monitoring function which enables database stores and mailboxes quota management. You can use the Exchange Manager to get this function (Main View, Right Click on an Exchange Server). North America: / Europe:

32 Figure 23 Database store and mailbox quota management This dialog box enables you, in the upper portion, to view all of the database stores of a mail server and to manage the quotas with the Change Quotas function. If you click on Show Mailboxes it will display all of the database store mailboxes and you will be able to take a couple of actions: change a mailbox from a database store to another or change a mailbox quota. These actions enable you to directly manage your mailboxes, to be alerted in case of failure, to optimize your database store sizes and to manage capacity issues. We have seen how GSX gives you the opportunity to monitor all Exchange 2010 specific services and to take action to optimize your infrastructure as well as guarantee the quality of service you offer to your users through real time information management on your environment, the connectivity, availability, performance and capacity management. GSX goes even further though, thanks to capacity alerting, reporting and integration with your global operations center, our tool allows you to organize, in an intuitive fashion, the administration of your entire collaborative infrastructure administration. North America: / Europe:

33 Conclusion In this White Paper, we have looked at the how GSX Monitor to resolve the 4 big challenges that IT department has to face everyday and the business value of GSX Monitor and Analyzer for organizations using Microsoft Exchange GSX Monitor and Analyzer enables IT departments to reduce the risks and issues associated with Microsoft Exchange, and delivers business value in different key areas. Your Next Action Ask for a live demo of our GSX Monitor solution and fill out the form at or Contact us at sales@gsx.com North America: / Europe:

34 Figure summary Figure 1 GSX Monitor Main view... 3 Figure 2 Client Access Server role monitoring settings... 5 Figure 3 CAS alerts settings... 7 Figure 4 Main View of the Client Access role and Mailbox roles... 8 Figure 5 consolidated statistics view for Mailbox server... 9 Figure 6 Main view: LED related to the DAG Figure 9 DAG Exchange cluster availability during one week Figure 11 Exchange Manager Mail Queue Figure 12 Exchange Manager Server Health Check Figure 13 Access Time Exchange Figure 14 Overall status GSX Analyzer Figure 15 Exchange mail routing Figure 16 Mail Routing Statistics Figure 17 CPU performance graph from GSX Analyzer Figure 18 Main View Disk Space Alert Figure 19 Disk Space Graph Figure 20 Disk Space Reporting Figure 21 Database store alerting Figure 23 Database store and mailbox quota management North America: / Europe:

35 GSX Solutions 36 Boulevard Helvétique 1207 Genève Switzerland Tel: Fax: North America: / Europe: