Configuring and Monitoring Exchange 2007/2010 Servers

Transcription

1 Configuring and Monitoring Exchange 2007/2010 Servers eg Enterprise v5.6

2 Restricted Rights Legend The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eg Innovations, Inc. eg Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Trademarks Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Copyright 2012 eg Innovations, Inc. All rights reserved.

3 Table of Contents CONFIGURING AN EXCHANGE 2007/2010 SERVER/SERVER ROLE FOR MONITORING BY EG ENTERPRISE...1 CONFIGURING AND MONITORING AN EXCHANGE CLIENT ACCESS SERVER ADMINISTERING THE EG MANAGER TO MONITOR A EXCHANGE CLIENT ACCESS SERVER MONITORING THE EXCHANGE CLIENT ACCESS SERVER...8 CONFIGURING AND MONITORING AN EXCHANGE MAILBOX SERVER ADMINISTERING THE EG MANAGER TO MONITOR A EXCHANGE MAILBOX SERVER MONITORING THE EXCHANGE MAILBOX SERVER...10 CONFIGURING AND MONITORING AN EXCHANGE HUB TRANSPORT SERVER ADMINISTERING THE EG MANAGER TO MONITOR A EXCHANGE HUB TRANSPORT SERVER MONITORING THE EXCHANGE HUB TRANSPORT SERVER...13 CONFIGURING AND MONITORING AN EXCHANGE EDGE TRANSPORT SERVER ADMINISTERING THE EG MANAGER TO MONITOR A EXCHANGE EDGE TRANSPORT SERVER MONITORING THE EXCHANGE EDGETRANSPORT SERVER...16 CONFIGURING AND MONITORING AN EXCHANGE 2007/2010 SERVER ADMINISTERING THE EG MANAGER TO MONITOR A EXCHANGE 2007/2010 SERVER MONITORING THE EXCHANGE 2007/2010 SERVER...18 CONCLUSION...19

4 Table of Figures Figure 1.1: Selecting the Properties option from the shortcut menu...2 Figure 1.2: The Properties dialog box...3 Figure 1.3: The Log On tab page...4 Figure 1.4: Specifying the name of the Exchange Administrator...4 Figure 1.5: The exchange server name and administrator name displayed against This account...5 Figure 2.1: Adding an Exchange Client Access server...6 Figure 2.2: The list of unconfigured tests for the Exchange Client Access server...7 Figure 2.3: Configuring the Exchange OWA Connectivity test...7 Figure 3.1: Adding an Exchange Mailbox server...9 Figure 3.2: List of Unconfigured tests for the server...10 Figure 3.3:Configuring the Exchange Traffic test...10 Figure 4.1: Adding an Exchange Hub Transport server...11 Figure 4.2: The list of Unconfigured tests for the Exchange Hub Transport...12 Figure 4.3: Configuring the Exchange Messages test...12 Figure 5.1: Adding an Exchange Edge Transport server...14 Figure 5.2: The list of Unconfigured tests for the Exchange Edge Transport...15 Figure 5.3: Configuring the Exchange Messages test for the Exchange Hub Transport...15 Figure 6.1: Adding an Exchange 2007/2010 server...17

5 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise Chapter 1 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise eg Enterprise adopts an agent-based approach to monitoring the Exchange 2007/2010 model and also those models that correspond to each of the Exchange 2007/2010 server roles. The agent-based approach requires that you install and configure the eg agent on the Exchange 2007/2010 host (if the Exchange 2007/2010 server is to be monitored as a whole) or on the host on which the server role to be monitored exists. This internal agent, once started, periodically runs a wide variety of tests on the Exchange 2007/2010 server/server role to extract useful performance data. Some of these tests, namely the Exchang boxStatus test, the ExchangeStorageGroup test, and the ExchangeQueueStats test require Exchange Administrator privileges to execute. Therefore, prior to monitoring an Exchange 2007 server/server role using eg Enterprise, make sure that you configure the eg agent to run with the privileges of an Exchange Administrator. To achieve this, do the following: 1. Login to the Exchange 2007/2010 server or the host on which the server role to be monitored operates. 2. Open the Services window by following the menu sequence, Start -> Run, and typing services.msc in the text box that appears. 3. Locate the egurkhaagent service in the list of services displayed in the Services window. 4. Stop the service, if it is currently running. 5. Then, right-click on the egurkhaagent service, and select the Properties option from the shortcut menu that appears (see Figure 1.1). 1

6 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise Figure 1.1: Selecting the Properties option from the shortcut menu 6. Switch to the Log On tab page of the Properties dialog box that appears, by clicking on that tab page. 2

7 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise Figure 1.2: The Properties dialog box 7. Select the This account option in the Log On tab page. To specify the account using which the chosen service should run, use the Browse button in Figure

8 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise Figure 1.3: The Log On tab page 8. Figure 1.4 then appears. Ensure that the From this location box displays the name of the Exchange 2007 server being monitored. You can use the Locations button in Figure 1.4 to change this specification. Then, enter the name of the Exchange administrator in the Enter the object name to select text box. Finally, click the OK button in Figure 1.4 Figure 1.4: Specifying the name of the Exchange Administrator 9. The specified user name and location will then be displayed against This account in Figure

9 Configuring an Exchange 2007/2010 Server/Server Role for Monitoring by eg Enterprise Figure 1.5: The exchange server name and administrator name displayed against This account 10. Finally, click on the Apply and OK buttons in Figure 1.5. Once this is done, you can proceed to manage and monitor the Exchange 2007/2010 server as a whole, or each of its server roles using the procedures discussed in the sections that will follow. 5

10 Configuring and Monitoring an Exchange Client Access Server Chapter 2 Configuring and Monitoring an Exchange Client Access Server In this chapter, we will be looking at how to manage and monitor the performance of the Client Access Server role of the Exchange server. 2.1 Administering the eg Manager to monitor a Exchange Client Access Server 1. Log into the eg administrative interface. 2. eg Enterprise cannot automatically discover Exchange Client Access server. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 2.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically. Figure 2.1: Adding an Exchange Client Access server 3. Next, sign out of the eg administrative interface. Figure 2.2 then appears, listing the unconfigured tests for the Client Access server. 6

11 Configuring and Monitoring an Exchange Client Access Server Figure 2.2: The list of unconfigured tests for the Exchange Client Access server 4. Click on the Exchange OWA Xonnectivity test to configure it. Figure 2.3: Configuring the Exchange OWA Connectivity test 5. In Figure 2.3 that appears, specify the following: TESTPERIOD - Indicates how often this test needs to be executed. HOST - Indicates the IP address of the Client Access server. PORT - The port number of the client access server. By default, this is 110. XCHGEXTENSIONSHELLPATH - Specify the full path to the Exchange management shell in the XCHGEXTENSIONSHELLPATH text box. CLIENT ACCESS SERVER Specify the complete qualified hostname of the client access server in the CLIENT ACCESS SERVER text box. OUTLOOKD WEB APP URL Specify the website URL in the OUTLOOK WEB APP URL text box. By Default none will be provided. 6. Finally, click the Update button in Figure 2.3 and signout of the eg administrative interface. 7

12 Configuring and Monitoring an Exchange Client Access Server 2.2 Monitoring the Exchange Client Access Server To monitor the Exchange Client Access server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. In the COMPONENT LIST page, click on the Exchange Client Access for which you wish to view measurements. 8

13 Configuring and Monitoring an Exchange Mailbox Server Chapter 3 Configuring and Monitoring an Exchange Mailbox Server 3.1 Administering the eg Manager to monitor a Exchange Mailbox Server 1. Log into the eg administrative interface. 2. eg Enterprise cannot automatically discover Exchange Mailbox server. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 3.1) that appears when the Infrastructure -> Components -> Add/Modify Servers menu sequence is followed. Remember that components manually added are managed automatically. Figure 3.1: Adding an Exchange Mailbox server 3. When you attempt to sign out, a list of unconfigured tests appears. 9

14 Configuring and Monitoring an Exchange Mailbox Server Figure 3.2: List of Unconfigured tests for the server 4. Click on the ExchangeTraffic test to configure it. Figure 3.3:Configuring the Exchange Traffic test 5. To configure the test, specify the following in Figure 3.3. TEST PERIOD - How often should the test be executed HOST - The host for which the test is to be configured PORT - The port number at which the specified HOST listens. XCHGEXTENSIONSHELLPATH - Specify the full path to the Exchange management shell. 6. Then, click the Update button in Figure 3.3, to save the changes. 7. Next sign out of the administrative interface. 3.2 Monitoring the Exchange MailBox Server To monitor the Exchange MailBox server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. From the COMPONENT LIST page, click on the Exchange Mailbox for which you wish to view measurements. 10

15 Configuring and Monitoring an Exchange Hub Transport Server Chapter 4 Configuring and Monitoring an Exchange Hub Transport Server In this chapter, we will be looking at how to manage and monitor the performance of the Exchange 2007 Hub Transport Server role of the Exchange 2007 server. 4.1 Administering the eg Manager to monitor a Exchange Hub Transport Server 1. Log into the eg administrative interface. 2. eg Enterprise cannot automatically discover Exchange Hub Transport server. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 4.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically. Figure 4.1: Adding an Exchange Hub Transport server 3. A list of Unconfigured tests will appear as shown in Figure

16 Configuring and Monitoring an Exchange Hub Transport Server Figure 4.2: The list of Unconfigured tests for the Exchange Hub Transport 4. Now click on the Exchange Messages test to configure it. Upon doing so, Figure 4.3 will appear. Figure 4.3: Configuring the Exchange Messages test 5. Specify the following in Figure 4.3 to configure the test. TEST PERIOD - How often should the test be executed HOST Indicates the IP address of the Mailbox server. PORT The port number through which the Mailbox server communicates. By default, this is 691. ALLEVENTS By default, this flag is set to false, indicating that this test will report metrics for only the following event types by default: SEND, RECEIVE, SUBMIT,FAIL, POISON. If you want the test to additionally report metrics across all event types i.e., support an additional All descriptor, which will report the total number of s handled by the server and their total size then, set this flag to true. DD FOR RECEIVEMESSAGE In large, highly active Exchange environments, hundreds of s may be received by the Exchange server within a short period of time. In such environments, the frequent collection of detailed diagnosis of the received s may increase the processing overheads of the eg agent, and may even choke the eg database. To avoid this, the DD FOR RECEIVEMESSAGE flag is set to false by default; this implies that the test will not provide the detailed diagnosis for the RECEIVE descriptor i.e., for the received messages by default. To view detailed diagnosis for these messages as well, set this flag to true. DD FOR SENDMESSAGE - In large, highly active Exchange environments, hundreds of s may be sent by the Exchange server within a short period of time. In such environments, the frequent collection of detailed diagnosis information related to the sent s may increase the processing overheads of the eg agent, and may even 12

17 Configuring and Monitoring an Exchange Hub Transport Server choke the eg database. To avoid this, the DD FOR SENTMESSAGE flag is set to false by default; this implies that the test will not provide the detailed diagnosis for the SEND descriptor i.e., for the sent messages by default. To view detailed diagnosis for these messages as well, set this flag to true. DD FOR SUBMITMESSAGE - In large, highly active Exchange environments, hundreds of s may be submitted to the transport pipeline within a short period of time. In such environments, the frequent collection of detailed diagnosis information related to the submitted s may increase the processing overheads of the eg agent, and may even choke the eg database. To avoid this, the DD FOR SUBMITMESSAGE flag is set to false by default; this implies that the test will not provide the detailed diagnosis for the SUBMIT descriptor i.e., for the sent messages by default. To view detailed diagnosis for these messages as well, set this flag to true. XCHGEXTENSIONSHELLPATH - Specify the full path to the Exchange management shell. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o o The eg manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be Now, click on the Update button in Figure 4.3 and sign out of the eg administrative interface. 4.2 Monitoring the Exchange Hub Transport Server To monitor the Exchange Hub Transport server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. In the COMPONENT LIST page, click on the Exchange Hub Transport for which you wish to view measurements. 13

18 Configuring and Monitoring an Exchange Edge Transport Server Chapter 5 Configuring and Monitoring an Exchange Edge Transport Server The chapter that follow will discuss how to administer and monitor an Exchange Edge Transport Server. 5.1 Administering the eg Manager to monitor a Exchange Edge Transport Server 1. Log into the eg administrative interface. 2. eg Enterprise cannot automatically discover Exchange Edge Transport server. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 5.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically. Figure 5.1: Adding an Exchange Edge Transport server 3. A list of Unconfigured tests will appear as shown in Figure

19 Configuring and Monitoring an Exchange Edge Transport Server Figure 5.2: The list of Unconfigured tests for the Exchange Edge Transport 4. Now click on the Exchange Messages test to configure it. Upon doing so, Figure 5.3 will appear. Figure 5.3: Configuring the Exchange Messages test for the Exchange Hub Transport 5. Specify the following in Figure 5.3 to configure the test. TEST PERIOD - How often should the test be executed HOST Indicates the IP address of the Mailbox server. PORT The port number through which the Mailbox server communicates. By default, this is 691. ALLEVENTS By default, this flag is set to false, indicating that this test will report metrics for only the following event types by default: SEND, RECEIVE, SUBMIT,FAIL, POISON. If you want the test to additionally report metrics across all event types i.e., support an additional All descriptor, which will report the total number of s handled by the server and their total size then, set this flag to true. DD FOR RECEIVEMESSAGE In large, highly active Exchange environments, hundreds of s may be received by the Exchange server within a short period of time. In such environments, the frequent collection of detailed diagnosis of the received s may increase the processing overheads of the eg agent, and may even choke the eg database. To avoid this, the DD FOR RECEIVEMESSAGE flag is set to false by default; this implies that the test will not provide the detailed diagnosis for the RECEIVE descriptor i.e., for the received messages by default. To view detailed diagnosis for these messages as well, set this flag to true. DD FOR SENDMESSAGE - In large, highly active Exchange environments, hundreds of s may be sent by the Exchange server within a short period of time. In such environments, the frequent collection of detailed diagnosis information related to the sent s may increase the processing overheads of the eg agent, and may even choke the eg database. To avoid this, the DD FOR SENTMESSAGE flag is set to false 15

20 Configuring and Monitoring an Exchange Edge Transport Server by default; this implies that the test will not provide the detailed diagnosis for the SEND descriptor i.e., for the sent messages by default. To view detailed diagnosis for these messages as well, set this flag to true. DD FOR SUBMITMESSAGE - In large, highly active Exchange environments, hundreds of s may be submitted to the transport pipeline within a short period of time. In such environments, the frequent collection of detailed diagnosis information related to the submitted s may increase the processing overheads of the eg agent, and may even choke the eg database. To avoid this, the DD FOR SUBMITMESSAGE flag is set to false by default; this implies that the test will not provide the detailed diagnosis for the SUBMIT descriptor i.e., for the sent messages by default. To view detailed diagnosis for these messages as well, set this flag to true. XCHGEXTENSIONSHELLPATH - Specify the full path to the Exchange management shell. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eg Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eg agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: o o The eg manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be Now, click on the Update button in Figure 5.3 and sign out of the eg administrative interface. 5.2 Monitoring the Exchange EdgeTransport Server To monitor the Exchange EdgeTransport server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. In the COMPONENT LIST page, click on the Exchange Edge Transport for which you wish to view measurements. 16

21 Configuring and Monitoring an Exchange 2007/2010 Server Chapter 6 Configuring and Monitoring an Exchange 2007/2010 Server The sections that follow will discuss how to administer and monitor an Exchange 2007 server. 6.1 Administering the eg Manager to monitor a Exchange 2007/2010 Server 1. Log into the eg administrative interface. 2. eg Enterprise cannot automatically discover Exchange 2007/2010 server. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 6.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically. Figure 6.1: Adding an Exchange 2007/2010 server 3. Next, try to sign out of the eg administrative interface. You will be prompted to configure the Exchange2007MailService and ExchangeTraffic test. This test monitors the availability and performance of a Microsoft Exchange 2007/2010 mail server from an external perspective. The test mimics a mail client activity by using the Exchange Web Service for sending and receiving mails. For this test to execute smoothly, the external agent executing the test should be in the same domain as the Exchange 2007/2010 server. Configure the test in the manner discussed in Section 2.1 of this document. 17

22 Configuring and Monitoring an Exchange 2007/2010 Server 4. Finally, sign out of the eg administrative interface. 6.2 Monitoring the Exchange 2007/2010 Server To monitor the Exchange 2007/2010 server, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the components option in the menu bar, and select the Servers option from the components menu. 3. From the component list page, click on the Exchange 2007/2010 for which you wish to view measurements. 18

23 Conclusion Chapter 7 Conclusion This document has described in detail the steps for configuring and monitoring the Exchange Servers. For details of how to administer and use the eg Enterprise suite of products, refer to the user manuals. We will be adding new measurement capabilities into the future versions of the eg Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eg Enterprise suite of products, please contact support@eginnovations.com. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eg Enterprise suite can be forwarded to feedback@eginnovations.com. 19