Tivoli Manager for Exchange User s Guide. Version 2.0

Transcription

1 Tivoli Manager for Exchange User s Guide Version 2.0

2

3

4

5 Tivoli Manager for Exchange User s Guide (December 1999) Copyright Notice Copyright 1998, 1999 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli, Tivoli Enterprise Console, Tivoli Management Framework, and Tivoli Global Enterprise Manager. Microsoft Windows, Windows NT, and the Microsoft logo are trademarks or registered trademarks of Microsoft Corporation. Tivoli Manager for Exchange User s Guide v

6 Tivoli Manager for Exchange User s Guide (December 1999) UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York USA. vi Version 2.0

7 Contents Tivoli Manager for Exchange User s Guide (December 1999)...v Preface...xv Chapter 1 Introducing Manager for Exchange Operations Management...2 Event Management...2 Software Distribution and Installation...3 Integration with Tivoli Management Framework...3 Chapter 2 Installing Manager for Exchange Pre-Installation Considerations...8 Tivoli Management Region Configuration...8 NT Event Adapter Requirements...8 Event Server Configuration...8 UNIX Platform Requirements...9 Application Proxy Availability...9 Installation Overview...9 Installation Log Files...11 Upgrade and Migration Considerations...11 Installing the Application Proxy...12 From the Tivoli Desktop...12 Using the winstall Command...13 Installing Manager for Exchange...14 From the Tivoli Desktop...15 Using the winstall Command...18 Chapter 3 Getting Started Assigning Manager for Exchange Authorization...21 Assigning TMR Roles to a Tivoli Administrator...22 Assigning Resource Roles to a Tivoli Administrator...23 Configuring and Distributing Client File Packages...23 Tivoli Manager for Exchange User s Guide vii

8 Configuring TEC Event Handling...23 Managing Microsoft Exchange Servers...24 Creating Microsoft Exchange Server Instances...24 Determining Server Status...30 Subscribing Servers to a Profile Manager...31 Deleting a Microsoft Exchange Server...32 Chapter 4 Distributing Clients Creating File Packs...33 Distributing File Packs...37 Before and After Installation Processing...38 Chapter 5 Monitoring Exchange Servers Adding Monitors...39 Understanding the Monitors...43 Microsoft Exchange Monitoring Collections...43 Additional Microsoft Exchange-Specific Monitors...44 Available Memory...44 Database/Log Usage...44 Disk Space Available...45 Disk Space Usage...45 Event Adapter Status...45 MailPing Listener...45 Configuring and Testing the MailPing Listener Monitor...46 TivoliMailPing Service...52 Removing Test Messages...53 Performance Counters...53 Server Status...53 Predefined Monitors...53 Chapter 6 Tasks for Managing Resources Listing Tasks...55 viii Version 2.0

9 Running Tasks...56 Microsoft Exchange Server Tasks...58 Server Information Tasks...59 Display Server Status...59 Display Server Info...60 Display Exchange Info...60 Display Statistics...61 Mailbox Information Tasks...61 Mailbox Info...61 Database and Disk Utility Tasks...61 Run ISINTEG...61 Run EDBUTIL/ESEUTIL...62 Run MTACHECK...63 Diagnostic and Control Services Tasks...63 Diagnostic Logging-Set and -View...63 Start and Stop Services...64 Manager for Exchange Utility Tasks...64 Discover Exchange Servers...65 Set Icon State...66 Start Debugging...66 Stop Debugging...67 List Debug Logs...67 Remove Debug Logs...67 Migrate Exchange Servers...67 Delete Migrated Exchange Objects...69 Create Client Filepacks...69 Start Monitors...69 Stop Monitors...70 Configure MailPing Listener Monitor...70 Start_Stop MailPing Listener Monitor...70 Chapter 7 Managing Exchange Server Events Tivoli Manager for Exchange User s Guide ix

10 Configuring the Event Server...72 Configuring the Event Console...75 Configuring the NT Event Adapter...77 Starting and Stopping the NT Event Adapter...78 Monitoring the NT Event Adapter...79 Filtering Events...79 Chapter 8 Tivoli GEM Instrumentation Understanding the Tivoli GEM Server...81 Understanding the Tivoli GEM Console...82 Tivoli GEM Instrumentation Event Handling...82 Instrumentation Files, Libraries, and Profiles...82 Tasks...83 Monitors...83 Preparing to Install Tivoli GEM Instrumentation...84 Tivoli Management Regions...84 Administrators...84 Installation Prerequisites...84 Installing and Configuring Tivoli GEM Instrumentation Components...85 Copying B*DF, CDF, GDF, and Icon Files...85 Installing the Java Development Kit...86 Creating User Groups and Logon IDs for the Tivoli GEM Console...88 Windows NT...88 AIX...88 HP/UX...89 SUN Solaris...89 Setting Security for the Windows NT Operating System...89 Installing Tivoli GEM Instrumentation...90 Defects, Limitations, and Workarounds...92 Chapter 9 Initializing Tivoli GEM Instrumentation. 93 Configuring Tivoli GEM Event Handling...93 x Version 2.0

11 Configuring Microsoft Exchange Servers...95 Subscribing to and Distributing the File Packages...95 Subscribing to and Distributing the Heartbeat Monitor...96 Confirming Resource Discovery...98 Chapter 10 Instrumentation Tasks and Monitors. 99 Locating and Running Tasks...99 Tivoli GEM Instrumentation Tasks...99 Microsoft Exchange Server Tasks...99 Navigating to Microsoft Exchange Server Resources Using the Tear-Away Log Starting a Sample Task Monitors Microsoft Exchange Server Monitors Heartbeat Monitor State Monitor Manager for Exchange-Supported Monitors Monitor Operability Tasks Available for Monitors Appendix A Command Line Commands wcrtmsxchg wgetmsxchg wsetmsxchg wdel Appendix B Event Classes and Rules Manager for Exchange Event Classes Distributed Monitoring Events NT Event Adapter Events Manager for Exchange Event Rules NT Event Adapter Rules Tivoli Manager for Exchange User s Guide xi

12 Distributed Monitor Rules GEM Event Rules Appendix C Business and Component Files Installing B*DF, CDF, GDF, and Icon Files Business, Component, and Global Description Files Icon Files Appendix D GEM Task and Monitor Descriptions 125 Tasks Tasks for Monitors Manager for Exchange Monitors Supported by GEM Instrumentation Appendix E Finding and Correcting Problems Installation Questions Questions on Using Tasks and Jobs from the Tivoli Desktop Questions on Running Tasks from the Tivoli GEM Console Questions on Using Monitors Questions on Using the TEC Questions on Using the Tivoli GEM Client Questions on Turning on GEM Instrumentation Debugging Icon State Helpful Debugging Information Manager for Exchange Log Files Tivoli GEM-specific Questions and Tips Appendix F Error Messages Appendix G Performance Monitor Counters Appendix H Registry Information Appendix I IND Files xii Version 2.0

13 Glossary Index Tivoli Manager for Exchange User s Guide xiii

14 xiv Version 2.0

15 Preface This document includes information about planning for, installing, and using Tivoli Manager for Exchange (Manager for Exchange), previously TME 10 Module for Exchange. It describes using monitors and tasks with Manager for Exchange. You can optionally use Manager for Exchange with Tivoli Global Enterprise Manager (Tivoli GEM) and Tivoli GEM Instrumentation for Exchange to obtain a graphical topology display of the Microsoft Exchange Servers, their status, and a list of tasks which can be run against each Microsoft Exchange Server. Who Should Read This Document This document is for system administrators who monitor and manage Microsoft Exchange Servers. The document requires knowledge of Tivoli and Microsoft Exchange products and, optionally, the Tivoli GEM product. Prerequisite and Related Documents For hardware and software requirements, and other release information, refer to the Tivoli Manager for Exchange Release Notes. Related documents include: TME 10 Distributed Monitoring User s Guide TME 10 Enterprise Console Adapters Guide TME 10 Enterprise Console Rule Builder s Guide TME 10 Enterprise Console User s Guide Tivoli Manager for Exchange User s Guide xv

16 Preface TME 10 Framework User s Guide TME 10 Framework Planning and Installation Guide TME 10 Software Distribution User s Guide TME 10 Software Installation Service User's Guide Related documents for Tivoli Global Enterprise Manager include: Tivoli Global Enterprise Manager Installation and User s Guide Tivoli Global Enterprise Manager Instrumentation Guide Note: Tivoli is in the process of changing product names. Products referenced in this document may still be available under their old names, for example, TME 10 Enterprise Console is now referred to as Tivoli Enterprise Console; Sentry is now referred to as Distributed Monitoring. What This Document Contains The Tivoli Manager for Exchange User s Guide contains the following sections: Chapter 1. Introducing Manager for Exchange, on page 1 Introduces the features and functions of Manager for Exchange. Chapter 2. Installing Manager for Exchange, on page 5 Covers the planning for and installing of Manager for Exchange. Chapter 3. Getting Started, on page 21 Covers the configuring of Manager for Exchange. Chapter 4. Distributing Clients, on page 33 Tells you how to create and distribute Microsoft Exchange file packs to clients. Chapter 5. Monitoring Exchange Servers, on page 39 Describes how to use the performance monitors that Manager for Exchange provides. Chapter 6. Tasks for Managing Resources, on page 55 xvi Version 2.0

17 Preface Describes how to locate and use tasks provided by Manager for Exchange. Chapter 7. Managing Exchange Server Events, on page 71 Contains information on configuring and using the NT event adapter to forward Microsoft Exchange Server events to the Tivoli Enterprise Console (TEC) event server. Chapter 8. Tivoli GEM Instrumentation, on page 81 Covers the planning for and installing of Tivoli GEM instrumentation. Chapter 9. Initializing Tivoli GEM Instrumentation, on page 93 Describes configuring and using Tivoli GEM instrumentation. Chapter 10. Instrumentation Tasks and Monitors, on page 99 Describes Tivoli GEM tasks and monitors which become accessible for operational management of your Microsoft Exchange servers after the Tivoli GEM components have been successfully installed. Appendix A. Command Line Commands, on page 107 Contains a list of supported command line interface (CLI) commands you can use to create, to change, and to view the attributes of Microsoft Exchange Server instances. Appendix B. Event Classes and Rules, on page 113 Contains a list of supported event source names and a map of the labels provided by the Windows NT Event Viewer and the Tivoli event display. Appendix C. Business and Component Files, on page 121 describes the Tivoli GEM business and component description files. Appendix D. GEM Task and Monitor Descriptions, on page 125 Provides the field entries required when you run Tivoli GEM instrumentation tasks. Appendix E. Finding and Correcting Problems, on page 129 Tivoli Manager for Exchange User s Guide xvii

18 Preface Provides installation tips, help on debugging problems, and typical symptoms and solutions. Appendix F. Error Messages, on page 147 Contains a list of the messages that are generated by Manager for Exchange. Appendix G. Performance Monitor Counters, on page 161 Contains a list of the performance monitors and their respective counters that are provided by Manager for Exchange. Appendix H. Registry Information, on page 177 Contains Windows NT registry information that is used by the TivoliMailPing service. Appendix I. IND Files, on page 179 Contains a list of the IND files associated with the products and patches on the product CD-ROM. What s New for Version 2.0 of Manager for Exchange New functions provided in Manager for Exchange Version 2.0 include: Support for Microsoft Exchange Server management on endpoints. Manager for Exchange Version 2.0 does not support Microsoft Exchange Server management on managed nodes or distribution to PC managed nodes. Tasks: Migrate Exchange Servers Delete Migrated Exchange Objects List Debug Logs Remove Debug Logs Configure MailPing Listener Monitor Start-Stop MailPing Listener Monitor See Manager for Exchange Utility Tasks on page 64 for descriptions of these tasks. Support on Windows 98. xviii Version 2.0

19 Preface Typeface Conventions The document uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Lower- and mixed-case commands, keywords, authorization roles, URLs, or other information that you must use literally appear in bold. Italics Variables that you must provide appear in italics. Words and phrases that are emphasized as well as any new terms also appear in italics. Monospace Code examples, output, and system messages appear in a monospace font. Online Versions of this Document Online versions of the Tivoli Manager for Exchange User s Guide and the Tivoli Manager for Exchange Release Notes are available on the product CD-ROM and in the following directory: for UNIX: $BINDIR/../generic_unix/TME/MSExchange/doc for Windows NT: %BINDIR%\..\generic_unix\TME\MSExchange\doc Use Adobe Acrobat Reader to view or print the usergide.pdf and relnotes.pdf files located in the \DOC\pdf directory on the product CD- ROM. Use your browser to view the usergide.htm and relnotes.htm files located in the \DOC\html directory on the product CD-ROM. You can also view the Tivoli Manager for Exchange User s Guide and Tivoli Manager for Exchange Release Notes on our Web site by pointing your browser to Contacting Customer Support For support for this or any Tivoli product, you can contact Tivoli Customer Support in one of the following ways: Visit our Web site at Tivoli Manager for Exchange User s Guide xix

20 Preface Send to Customers in the United States can also call TIVOLI8 ( ). International customers should consult the Web site for customer support telephone numbers. You can also review the Customer Support Handbook, which is available on our Web site at When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. Company identification information may also be needed to access various online services available on the Web site. The Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, Redbooks, and Whitepapers. The documentation sets for some product releases are available in both PDF and HTML formats. Translated documents are also available for some product releases. You can order documentation by at swdist@tivoli.com. Please provide the part number or order number of the desired document; alternatively, you can provide the document s title, version number, and date of publication. We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways: Fill out our customer feedback survey at Send to support@tivoli.com xx Version 2.0

21 1 1.Introducing Manager for Exchange Introducing Manager for Exchange Tivoli Manager for Exchange (Manager for Exchange) provides a centralized system management tool for Microsoft Exchange servers on the Tivoli platform. Manager for Exchange facilitates the management of Microsoft Exchange Servers on endpoints and the installation of Microsoft Exchange file packs on clients. Manager for Exchange can be used with the following optional products: Tivoli Enterprise Console (TEC) Receives, filters, and forwards selected events to an event server for further processing. TEC event adapter for Windows NT (NT event adapter) Converts Microsoft Exchange events to the TEC format. Tivoli Software Distribution Used to distribute and deploy software across multi-platform networks. Tivoli Global Enterprise Manager (Tivoli GEM) and Tivoli GEM instrumentation Enables you to obtain a graphical topology display of the Microsoft Exchange Servers, their statuses, and a list of tasks that can be run against each Microsoft Exchange Server. Tivoli Manager for Exchange User s Guide 1

22 Manager for Exchange provides the following features to enable you to perform system management functions for Microsoft Exchange: Tasks to control and automate Microsoft Exchange administrative activities on endpoints A selection of monitors for key performance and availability statistics for Microsoft Exchange Servers Configuration files for the NT event adapter to receive, filter, and forward selected events to the TEC Automated Microsoft Exchange client distribution Data input to Tivoli Decision Support For information on the supported versions of Microsoft Exchange and clients (i.e: Outlook 97 and Outlook 98), refer to the Tivoli Manager for Exchange Release Notes. Operations Management This feature enables you to perform tasks such as starting and stopping servers, running utilities, and obtaining information about servers. Tasks are also provided for operating and managing endpoints running a Microsoft Exchange Server. Event Management This feature enables you to monitor and retrieve Microsoft Exchange events from Microsoft Exchange Servers. These events are converted to TEC event format and forwarded to a centralized event server for display and processing. Manager for Exchange utilizes an NT event adapter that enables you to specify events that you do not want forwarded to the event server. With this feature, you can prevent the TEC from being populated with harmless events, and focus on events of interest to your administrators. Note: The TEC product must be installed for you to take advantage of event management functions. This document treats the topic of event management assuming that TEC is installed where required. See NT Event Adapter Requirements on page 8 for more information about the TEC. 2 Version 2.0

23 Software Distribution and Installation This feature enables you to perform remote software distribution and installation of the Microsoft Exchange client product from a centralized location. Integration with Tivoli Management Framework Tivoli Management Framework provides a powerful and flexible framework for developing a comprehensive management system. Manager for Exchange integrates your Microsoft Exchange Servers into this system. Integration with the Tivoli Management Framework provides many benefits, including: Authorizations Microsoft Exchange resources are contained in a Tivoli policy region. Manager for Exchange creates two new resource roles, mex_senior and mex_admin. To execute tasks, one or both of these roles must be assigned to an administrator. In addition, the mex_senior or mex_admin role must be assigned to administrators who run tasks from the Tivoli GEM console. Enterprise consoles TECs provide consolidated event displays for Microsoft Exchange events. TECs are configurable and can be created and configured for a number of Microsoft Exchange administrators and servers. Distributed monitoring You can set up monitors to alert you about events concerning Microsoft Exchange resources. Configurable thresholds and responses enable active monitoring and automatic creation of differing severity levels of event server events. Introducing Manager for Exchange Tivoli Manager for Exchange User s Guide 3

24 4 Version 2.0

25 wa t 2 2.Installing Manager for Exchange er Managing Microsoft Exchange Servers and clients with Tivoli Manager for Exchange (Manager for Exchange) requires installation of Manager for Exchange and, optionally, Tivoli Global Enterprise Manager (Tivoli GEM) instrumentation if Tivoli GEM is installed. If Tivoli GEM is installed on your system, refer to Chapter 8. Tivoli GEM Instrumentation, on page 81 for more information regarding Tivoli GEM instrumentation. Before installing Manager for Exchange, you must prepare both your Tivoli and Microsoft Exchange installation. This chapter describes how to install Manager for Exchange and the following pre-installation tasks: fos er wadrah weivrevo noi tal lat sni rof gninnalp 1. Ensure that all prerequisite software is installed and you are running on a supported operating system. Refer to the Tivoli Manager for Exchange Release Notes for information on supported Tivoli software, prerequisite software and operating systems, and disk space requirements. 2. Install the Application Proxy as described in Installing the Application Proxy on page If you are using the Tivoli Enterprise Console (TEC), install and configure the TEC event adapter for Windows NT (NT event adapter) packaged with the TEC. See NT Event Adapter Requirements on page 8 for information about NT event adapter requirements. Installing Manager for Exchange Tivoli Manager for Exchange User s Guide 5

26 4. If you manage Microsoft Exchange resources with Tivoli GEM, see Chapter 8. Tivoli GEM Instrumentation, on page 81 for instrumentation requirements. Manager for Exchange is installed on a TMR server and on gateway(s) that manage endpoints that contain a Microsoft Exchange Server. The commands and requests for information are sent from Manager for Exchange on the TMR server to the Manager for Exchange on a gateway for execution on the endpoint(s). With the additional installation of Tivoli GEM instrumentation, Tivoli GEM-specific tasks as well as Microsoft Exchange tasks can be run 6 Version 2.0

27 from the Tivoli GEM console. The following figure shows a typical Manager for Exchange environment with Tivoli GEM instrumentation. Installing Manager for Exchange krowten elpmas Tivoli Manager for Exchange User s Guide 7

28 Pre-Installation Considerations Before installing Manager for Exchange, the following topics should be addressed: Tivoli management region configuration NT event adapter requirements Event server configuration UNIX platform requirements Application Proxy availability Tivoli Management Region Configuration Configure the TMRs to include Microsoft Exchange Servers as endpoints before installing Manager for Exchange. Note: Resources must be shared on interconnected TMRs. For more information, see the TME 10 Framework Planning and Installation Guide. NT Event Adapter Requirements Manager for Exchange provides a set of configuration files and tasks to customize the NT event adapter, TEC event server, and TEC to process Microsoft Exchange Server events. The NT event adapter is packaged with the Tivoli Enterprise Console product. It should be installed, configured, and operational on each endpoint where Microsoft Exchange Server is installed from which you want to receive events. This should be done prior to running the Manager for Exchange task to configure the NT event adapter on the server. For more information, see Chapter 7. Managing Exchange Server Events, on page 71 and the TME 10 Enterprise Console Adapter s Guide. Event Server Configuration Install Manager for Exchange on each event server where you want to view and work with Microsoft Exchange events on your TEC. 8 Version 2.0

29 You can configure an event server to automatically forward Microsoft Exchange server events to another event server. Configuring event servers in this manner enables you to manage many Microsoft Exchange server management servers from a single console, even if the management servers reside in different TMRs. For more information, see the TME 10 Enterprise Console User s Guide. UNIX Platform Requirements If the TMR server or the TEC event server are running on UNIX, create a /tmp directory if it does not exist. The installation process, as well as several tasks, write log information to files within the /tmp directory. Application Proxy Availability The Application Proxy provides a common set of services that are used by Manager for Exchange. If the Application Proxy has not been installed (as part of another Tivoli manager), it must be installed before installing Manager for Exchange. The Application Proxy is available on the Manager for Exchange CD-ROM. See Installing the Application Proxy on page 12 for installation instructions. Installing Manager for Exchange Installation Overview The install facility installs Manager for Exchange and creates a Manager for Exchange icon on the Tivoli desktop. The following table shows the location of the installed components: Installed Component Application Proxy TMR Server TEC Event Server Gateway(s) for Exchange Server Endpoints X X X 1 Endpoint with Exchange Server Tivoli Manager for Exchange User s Guide 9

30 Installed Component TMR Server TEC Event Server Gateway(s) for Exchange Server Endpoints Endpoint with Exchange Server Manager for Exchange X X X NT event adapter X 1 The managed node where the Application Proxy is installed will usually be a gateway. To install Manager for Exchange: 1. Install all prerequisite Tivoli software including gateway and endpoint configuration. 2. Ensure that the Microsoft Exchange server has been installed on the endpoints that you want to manage. 3. Backup the Tivoli database. Tivoli also recommends making a TAR or WINZIP backup of your Tivoli directory tree. 4. Install the Application Proxy and Manager for Exchange on TMR servers, the event server in your TMR, and gateway(s) with Exchange Server endpoints that you want to manage. Manager for Exchange creates an object on a managed node, where the Application Proxy resides, to manage endpoints. This managed node typically has the gateway function. Note that the object can be created on any managed node, regardless of gateway or TMR functionality. Note: You must be logged in as an administrator with at least senior and install_product authority to install Manager for Exchange. 5. Optionally, install the NT event adapter on each endpoint. This is used to forward events to the TEC from the NT event log. Note: The Adapter Configuration Facility (ACF) is required to install and distribute adapters on endpoints. See the TME 10 Enterprise Console User s Guide for more information. 10 Version 2.0

31 6. If you optionally manage Microsoft Exchange Server resources with Tivoli GEM, see Chapter 8. Tivoli GEM Instrumentation, on page 81 for installation requirements. 7. After installing Manager for Exchange, backup the Tivoli database, saving the backup file with a different name from the previous backup. Installation Log Files The install facility always writes a log file named %TMP%\msex20_init.log (on UNIX: $TMP/msex20_init.log). On Windows NT platforms, TMP is the directory pointed to by the wtemp command. When you upgrade to Tivoli Manager for Exchange 2.0 from Tivoli Module for Exchange 1.1, the log file is named msexpatch20_init.log. If the log file does not exist, a problem was initiated before invoking the install facility. In this case, after the problem has been corrected, reinstall the product from the installation media. If the log file does exist, the install facility was invoked. Review the log file to determine the cause of the problem. When the problem has been corrected, run the install facility located at %BINDIR%\..\generic_unix\TME\MSExchange\msex20.init (on UNIX: $BINDIR/../generic_unix/TME/MSExchange/msex20.init) from the command line. You do not need to restore the backup of the Tivoli database. Installing Manager for Exchange Upgrade and Migration Considerations If you are upgrading from TME 10 Module for Exchange 1.1 to Manager for Exchange 2.0, you may already have MSExchange objects defined for your managed nodes. After installing endpoints on these managed nodes, to use Manager for Exchange 2.0 to manage these endpoints you will need to migrate the managed node objects to endpoint objects. To migrate, you can either create a new MSExchange instance or migrate the old managed node MSExchange instance by using the Migrate Exchange Servers task. Tivoli Manager for Exchange User s Guide 11

32 To create a new MSExchange instance, see Creating Microsoft Exchange Server Instances on page 24 and Discover Exchange Servers on page 65. After you have created your new endpoint instances, you can delete the old instances which are on the managed nodes. The Migrate Exchange Servers task will migrate an MSExchange object for an MSExchange server on a managed node to an MSExchange object for an MSEXchange server on an endpoint. Note: To use this task, the target managed node must have been upgraded to Manager for Exchange Version 2.0 with all the prerequisites that are required for the TMR. See the Tivoli Manager for Exchange Release Notes for all TMR prerequisite software. Installing the Application Proxy If Version 1.0 of the Application Proxy is currently installed, use the Install Patch dialog from the Tivoli desktop to upgrade to Version 1.1. If the Application Proxy has not been installed (as part of another Tivoli module), it must be installed before installing Manager for Exchange. The two methods that can be used to install the Application Proxy are described below. From the Tivoli Desktop From the Tivoli desktop, follow these steps to install the Application Proxy: 1. From the menu bar, select Desktop > Install > Install Product to display the Install Product dialog. 2. Click Select Media to display the File Browser dialog. This dialog enables you to specify the path to the installation media. 3. Enter the full path to the Application Proxy installation files in the Path Name text field. This should normally be the path to the Manager for Exchange CD-ROM. 4. Click Set Path. The File Browser dialog displays the contents of the specified media in the Files scrolling list. 12 Version 2.0

33 5. Click Set Media & Close. The File Browser dialog is closed and the Install Product dialog is displayed with Tivoli Application Proxy, Version 1.1 shown in the Select Product to Install scrolling list. 6. Select Tivoli Application Proxy, Version Select a target client on which to install the Application Proxy from the Available Clients scrolling list and then click the left arrow button. The selected client is moved to the Clients to Install On scrolling list. 8. Click Install & Close. The Product Install window is displayed, listing the actions that will be taken when you continue the installation process. 9. Click Continue Install to begin the Application Proxy installation process or click Cancel to stop the process. When you elect to install, the Product Install window continues to display messages showing the progress of the installation. Successful installation is indicated by a Finished product installation message. 10. Click Close to close the Product Install window. Installing Manager for Exchange Using the winstall Command You can also install the Application Proxy with the winstall command. The syntax and parameters are shown below. winstall -c cdrom_path -s tmr_server -i APRX11.IND -n machine_name where: -c cdrom_path specifies the path name of the CD-ROM image. -s tmr_server specifies the name of the TMR server. -i specifies the index file from which the Application Proxy is to be installed. -n machine_name Tivoli Manager for Exchange User s Guide 13

34 specifies the machine name on which the Application Proxy is to be installed. This is a TMR server or gateway. The following is an example of using the winstall command to install Tivoli Manager for Exchange 2.0: > winstall -c cdrom -i APRX11.IND -n pinball See the TME 10 Framework Reference Manual for more information about the winstall command. Also see Appendix I. IND Files, on page 179 for a list of.ind file names that can be used with the -i parameter when installing other products and patches from the product CD-ROM. Installing Manager for Exchange You can install Manager for Exchange in the following ways: From the Tivoli desktop as described on page From the Tivoli Desktop on page 15. From the command line using the winstall command as described on page Using the winstall Command on page 18. Using the Tivoli Software Installation Service (SIS). See the TME10 Software Installation Service User s Guide for instructions and for the list of platforms on which SIS is supported. If Version 1.1 of TME 10 Module for Exchange is currently installed, do not install it using these methods. Instead, use the Install Patch dialog on the Tivoli desktop to upgrade to Manager for Exchange Version 2.0. See Migrate Exchange Servers on page 67 for information about the Migrate Exchange Servers task and assistance in migrating from managed nodes to endpoints. The following sections of this chapter describe the two methods that can be used to install Manager for Exchange. Each method can be used to perform the installation on the Tivoli Management Region (TMR) server and on any gateway. Note: Do not install Manager for Exchange on the endpoint that you will be managing. 14 Version 2.0

35 From the Tivoli Desktop 1. From the menu bar, select Desktop > Install > Install Product to display the Install Product dialog. 2. Click Select Media to display the File Browser dialog. This dialog enables you to specify the path to the installation media. 3. Enter the full path to the Manager for Exchange installation files in the Path Name text field. This should normally be the path to the Manager for Exchange CD-ROM. 4. Click Set Path. The File Browser dialog displays the contents of the specified media in the Files scrolling list. Installing Manager for Exchange wodniwllatsni Tivoli Manager for Exchange User s Guide 15

36 5. Click Set Media & Close. The File Browser dialog is closed and the Install Product dialog is displayed. 6. Select Tivoli Manager for Exchange Version 2.0. Note: Install Manager for Exchange before you install Tivoli GEM Instrumentation for Exchange. wodniwtcudorpllatsni 16 Version 2.0

37 7. Select a target client on which to install Manager for Exchange from the Available Clients scrolling list and then click the leftarrow button. The selected client is moved to the Clients to Install On scrolling list. 8. Click Install & Close. The Product Install window is displayed, listing the actions that will be taken when you continue the installation process. Installing Manager for Exchange 9. Click Continue Install to complete the Manager for Exchange installation OR click Cancel to stop the process. When you elect to continue, messages showing the progress of the installation are displayed in the Product Install window. Successful installation is indicated by a Finished product installation message. wodniwllatsni Tivoli Manager for Exchange User s Guide 17

38 Note: The installation process creates a Manager for Exchange policy region, MSExchange object class, tasks, jobs, and roles. 10. Click Close to close the Product Install window. 11. Refresh the Tivoli desktop by selecting View > Refresh from the menu bar. The Tivoli desktop will display the Manager for Exchange policy region icon shown below. Using the winstall Command noci noiger ycilop The following is the syntax and parameters for the winstall command: winstall -c cdrom_path -s tmr_server -i MSEX20.IND -n machine_name Where: -c cdrom_path Specifies the full path name of the CD-ROM image. -s tmr_server Specifies the name of the TMR server. -i Specifies the index file from which Manager for Exchange is to be installed. -n machine_name Specifies the machine name on which Manager for Exchange is to be installed. The following is an example of using the winstall command to install Tivoli Manager for Exchange 2.0: > winstall -c cdrom -i MSEX20.IND -n pinball Refer to the TME 10 Framework Reference Manual for more information about the winstall command. Also see Appendix I. IND Files, on page 179 for a list of IND file names that can be used with the 18 Version 2.0

39 -i parameter when installing other products (using winstall) and patches (using wpatch) from the product CD-ROM. Installing Manager for Exchange Tivoli Manager for Exchange User s Guide 19

40 20 Version 2.0

41 3 3.Getting Started This chapter describes how to configure Tivoli Manager for Exchange (Manager for Exchange), and the management tasks and procedures used to configure Tivoli for a Microsoft Exchange Server. Configuring Manager for Exchange involves the following procedures: 1. Assigning Manager for Exchange-specific authorization to one or more Tivoli administrators as described in Assigning Manager for Exchange Authorization. 2. Configuring and distributing client file packages as described in Configuring and Distributing Client File Packages on page If you are using the Tivoli Enterprise Console (TEC) product, configuring TEC event handling before using Manager for Exchange as described in Configuring TEC Event Handling on page Configuring Tivoli for a Microsoft Exchange Server as described in Managing Microsoft Exchange Servers on page 24. Getting Started Assigning Manager for Exchange Authorization roines_xme ni dma_xme selor TMR The installation of Manager for Exchange creates two resource roles named mex_senior and mex_admin. All tasks require at least one of these roles to be assigned to the Tivoli administrator invoking the task. In addition, some tasks require Tivoli Tivoli Manager for Exchange User s Guide 21

42 authority as defined by TMR roles. A Tivoli administrator must have the required authority and must have been assigned one of the Manager for Exchange resource roles to successfully run tasks and processes. A Tivoli administrator with a TMR senior role must be given the new mex_senior resource role. Tivoli administrators who do not require TMR senior and super roles should be assigned the mex_admin resource role. Tasks that require a TMR senior or mex_senior resource role include: Configure Event Server (also requires super role) Configure Event Console Configure Event Adapter Create Client Filepacks Migrate Exchange Servers to Endpoints Delete Migrated Exchange Objects Tasks that require a Tivoli administrator with the mex_admin or mex_senior resource role include: The tasks described in Microsoft Exchange Server Tasks on page 58. The tasks described in Manager for Exchange Utility Tasks on page 64, with the exception of the Create Client Filepacks task. Manager for Exchange authorization may be assigned as TMR roles or resource roles depending on local authorization requirements. Assigning TMR Roles to a Tivoli Administrator To assign the TMR mex_senior and mex_admin roles to a Tivoli administrator: 1. From the desktop, double-click on the Administrators icon to display the Administrators window. 2. Right-click on the desired Administrator icon and select Edit TMR Roles from the pop-up menu. The Set TMR Roles dialog is displayed. 3. From the Available Roles scrolling list, select either or both of the mex_senior or mex_admin roles and move them to the Current roles scrolling list by clicking the left arrow. 22 Version 2.0

43 4. Click Change and Close. 5. Exit and restart the Tivoli desktop. Assigning Resource Roles to a Tivoli Administrator To add resource roles for a specific policy region to a Tivoli administrator: 1. From the desktop, double-click on the Administrators icon to display the Administrators window. 2. Right-click on the desired Administrator icon and select Edit Resource Roles from the pop-up menu. 3. Select Manager for Exchange from the Resources scrolling list. 4. From the Available Roles scrolling list, select either or both of the mex_admin or mex_senior roles and move them to the Current roles scrolling list by clicking the left arrow. 5. Click Change and Close. 6. Exit and restart the Tivoli desktop. Configuring and Distributing Client File Packages Configure a Microsoft Exchange client file package (Tivoli software distribution file pack), and then distribute the Microsoft Exchange client. For more information, see Chapter 4. Distributing Clients, on page 33. Configuring TEC Event Handling Configuring TEC event handling involves the following procedures: 1. Configuring the event server as described in Configuring the Event Server on page Configuring the TEC as described in Configuring the Event Console on page Configuring the TEC event adapter for Windows NT (NT event adapter) as described in Configuring the NT Event Adapter on page 77. Getting Started Tivoli Manager for Exchange User s Guide 23

44 Managing Microsoft Exchange Servers The following steps describe the procedures to manage your Microsoft Exchange environment with Manager for Exchange: 1. Creating a Microsoft Exchange Server instance as described in Creating Microsoft Exchange Server Instances. 2. Determining server status as described in Determining Server Status on page Ensuring that the Microsoft Exchange Server is a subscriber to the desired profile manager lists as described in Subscribing Servers to a Profile Manager on page Selecting and changing Microsoft Exchange monitors, and then distributing the monitors to selected endpoints. For more information, see Chapter 5. Monitoring Exchange Servers, on page 39. You can then run any of the management tasks that are described in Chapter 6. Tasks for Managing Resources, on page Deleting a Microsoft Exchange Server instance as described in Deleting a Microsoft Exchange Server on page 32. Creating Microsoft Exchange Server Instances A Microsoft Exchange Server instance can be used as a task endpoint and as a subscriber to a profile manager. This is a MSExchange endpoint instance and will appear in lists where endpoints are displayed and are to be selected. For example, the new endpoint name will appear in the Available to Become Subscribers list when looking at the subscribers for a profile manager. The name of the endpoint is the name specified in the Server Alias Name field when the endpoint was created and will have the format Server Alias Name (MSExchange). When running tasks and monitors that will run against a Microsoft Exchange Server, specify targets with (MSExchange) instances. For example: assume an endpoint named RTP exists and has a Microsoft Exchange Server running on the machine. When you create an instance 24 Version 2.0

45 of the server and specify a server alias name of Raleigh, then two endpoints will exist: Raleigh (MSExchange) RTP (Endpoint) When you run a task or monitor against a server, the endpoint specified should be Raleigh (MSExchange) as it will run against the server, not the machine. If the Endpoint is RTP and the server alias name specified is also RTP, the following two endpoints will exist: RTP (MSExchange) RTP (Endpoint) Tasks and monitors run against a server should specify RTP (MSExchange) as the target endpoint. Do not add both an MSExchange endpoint and its Endpoint endpoint to the same list; this will cause the actions to be run twice. Create an instance for each Microsoft Exchange Server to be managed. An instance is represented as an icon in the Manager for Exchange policy region on the Tivoli desktop. The icon displays the status of the server and provides a list of tasks that can be performed. You can create a Microsoft Exchange Server instance in the following ways: From the Tivoli desktop. From the command line. This method can be useful when you have many servers to create and you want to specify specific information used to create the instance. See Appendix A. Command Line Commands, on page 107, for a description of the commands that you can use to create, to display, and to update Microsoft Exchange Server instances. By running the Discover Exchange Servers task. This method is useful to quickly populate the policy region with server instances. Default information obtained from the server is used. To create an instance from the Tivoli desktop, do the following: 1. Double-click on the Manager for Exchange policy region icon to display the Policy Region: Manager for Exchange window. Getting Started Tivoli Manager for Exchange User s Guide 25

46 2. From the menu bar, select Create > MSExchange to display the Create an Exchange Server dialog. 3. Complete the following text fields: Server Alias Name Name to be used for the server object and the label for the icon. The alias name does not have to match the actual server name. Valid characters for this name include letters, numbers, spaces, and underscores. Gateway Managed node (usually a gateway) where the Application Proxy and the Manager for Exchange are installed. This is where the server object is created and resides. If left blank, this will default to the gateway that manages the endpoint. Endpoint Name Name of an existing endpoint where the Microsoft Exchange Server resides. Exchange Server version revresegnahcxe na etaerc 26 Version 2.0

47 Version of Microsoft Exchange Server that this server is running. This value is used when subscribing the server to the profile manager representing that version. Subscribe to the default profile manager? Select Yes if you are planning on running Manager for Exchange monitors on this server. 4. Click OK to add the Microsoft Exchange Server instance. Creating a Microsoft Exchange Server instance produces: A server object with class MSExchange that you can use as the target when running tasks and monitors against the server. An icon for the Microsoft Exchange Server, identified by its alias name, in the Policy Region: Manager for Exchange window as shown below. ecnatsni revres The icon reflects the server instance status as Unknown. To verify the status and to reset the icon to the server s actual status, run the Properties task as described below. A pop-up menu that enables you to perform common tasks. To display the menu and select a task, right-click on the desired Microsoft Exchange Server icon and drag the cursor to the desired task name shown in the menu. If you execute a task from the menu of a Microsoft Exchange Server icon, the task executes on that server only. The tasks listed on the menu are described in the following section. The pop-up task menu for a Microsoft Exchange Server icon contains the following options: Open Displays the profiles which have been distributed to this server. Properties This task will update the state of the Microsoft Exchange server icon. It will also display the properties of the server instance including the gateway endpoint name, Getting Started Tivoli Manager for Exchange User s Guide 27

48 endpoint name, Microsoft Exchange Server version, and status. At the time of invocation, if the four main Microsoft Exchange Server services are running, the status will be set to running. The services are: MSExchangeSA (Microsoft Exchange System Attendant) MSExchangeMTA (Microsoft Exchange Message Transfer Agent) MSExchangeIS (Microsoft Exchange Information Store) MSExchangeDS (Microsoft Exchange Directory) If any of the four services are down, the status will be set to stopped. If unable to verify the state of the services, the status will be set to unknown. For more information on Microsoft Exchange services, refer to Microsoft Exchange documentation. Start Server Tries to start the four main Microsoft Exchange Server services. Will return a successful message if all four main services are running, otherwise will return an error message. The Start Services task can be run to start additional services. Stop Server Stops the MSExchangeSA service which in turn stops all the other Microsoft Exchange Server services. Returns a successful message if all four main services are stopped, otherwise will return an error message. Clear Alert Resets the icon state. If the Manager for Exchange Server Status monitor is running, the monitor will change the icon to reflect the status of the server. Clear Alert can be used to reset the icon of a stopped server to indicate a status of unknown without affecting the actual status of the server. Tasks > Display Server Info 28 Version 2.0

49 Retrieves selected Manager for Exchange data from the target server. Tasks > Display Server Status Returns the status of each of the installed Manager for Exchange services on the target server. Tasks > Run MTACHECK Runs the MTACHECK task on the target server, enabling you to check and correct the queues used by the message transfer agent. Tasks > Turn Off Diagnostic Logging Runs the Diagnostic Logging-Set task specifying that all the logging levels are to be set to None. Tasks > View Diagnostic Logging Runs the Diagnostic Logging-View task specifying that the logging levels for all of the services are to be displayed. Tasks > Start Debugging Turns debugging on at the gateway, which is where the object exists, and at the endpoint, which is where the tasks are actually run. The trace files will have the object identifier (OID), given to the object during its creation, as part of the filename to differentiate traces for individual objects. Tasks > Stop Debugging Turns debugging off at the gateway, which is where the object exists, and at the endpoint, which is where the tasks are actually run. Start Monitors Starts all the Microsoft Exchange monitors on the server. Stop Monitors Stops all the Microsoft Exchange monitors on the server. Start Event Adapter Starts the TECNTAdapter event adapter service. Stop Event Adapter Stops the TECNTAdapter event adapter service. Getting Started Tivoli Manager for Exchange User s Guide 29

50 Determining Server Status The status of the server is reflected by the state of its icon as shown in the following table: Icon State Server Status Description stniopd En tegrat stniopd En tegrat stniopd En tegrat Running Stopped Unknown Displayed when the server is active or running. The server is determined to be running if all four main Microsoft Exchange Server services are running. Displayed when the server is not running or is stopped. The server is determined to be stopped if any one of the four main services is not running. Displayed when the status is unknown. The server status is determined to be unknown if the state of the services cannot be verified and when an object is created. The server status is updated when you select Start Server, Stop Server, or Properties from the pop-up task menu of the Microsoft Exchange Server icon. The server status is also updated when you run the Server Status monitor. To ensure that your server icons reflect the current status of the servers automatically, configure and distribute the server status monitor for each server and specify that a TEC event is to be generated. The server status monitor verifies the state of the four main Microsoft Exchange services. 30 Version 2.0

51 Subscribing Servers to a Profile Manager Manager for Exchange automatically creates several profile managers to help you group servers for management. Each profile manager has a list of subscribers that enables you to run tasks and monitors against each server in that list. The following profile managers are initially created: Exchange 5.0 Servers Exchange 5.5 Servers Exchange Monitors Exchange Client Filepacks The Exchange Monitors profile manager initially has the Microsoft Exchange Server profile managers as subscribers. You can run a task against all your servers by selecting the Exchange 5.0 Servers and Exchange 5.5 Servers profile managers. You can also distribute a set of monitors to only your Version 5.0 servers by selecting the Exchange 5.0 Servers profile manager as the distribution point. Note: When you select a Microsoft Exchange Server that is to be added as a subscriber, ensure that you specify the MSExchange instance and not the Endpoint. Follow these steps to subscribe servers to a profile manager: 1. Right-click on one of the profile managers and select Subscribers from the pop-up menu. 2. Select the desired Microsoft Exchange Server instances from the Available to Become Subscribers scrolling list and move them to the Current Subscribers list by clicking the left arrow. 3. Click Set Subscriptions & Close to subscribe the Microsoft Exchange Servers to the list. 4. When you open the associated profile manager window, a Microsoft Exchange server icon is displayed for each subscribed server. The state of the icon reflects the state of the server at the time the server was subscribed to the profile manager. The icon appearance is not updated for the icons displayed within a profile manager. The tasks on menus accessed on the subscriber icons will work, but the icon appearance will remain the same as it was when the instance was added as a subscriber. Getting Started Tivoli Manager for Exchange User s Guide 31

52 Deleting a Microsoft Exchange Server Deleting a Microsoft Exchange Server instance from a Manager for Exchange policy region does not affect the server itself, but does delete the server information stored in the Tivoli database. Use the following procedure to delete a Microsoft Exchange Server from the Manager for Exchange policy region: 1. From the Policy region: Manager for Exchange window, select the desired Microsoft Exchange Server icon. 2. From the Policy region: Manager for Exchange window menu bar, select Edit > Delete to remove the selected Microsoft Exchange Server from the policy region. 32 Version 2.0

53 4 4.Distributing Clients Distributing Clients To install Microsoft Exchange clients, use Tivoli Manager for Exchange (Manager for Exchange) to build file packs to distribute the Microsoft Exchange clients to any machines running as endpoints. For information on specific supported versions of Microsoft Exchange clients, refer to the Tivoli Manager for Exchange Release Notes. Creating File Packs Creating and saving one or more file packs requires a senior or mex_senior authorization. From the Tivoli desktop, do the following: 1. Double-click on the Manager for Exchange policy region icon. 2. From the Policy Region: Manager for Exchange window, doubleclick on the Exchange Utility Tasks icon. Tivoli Manager for Exchange User s Guide 33

54 3. From the Task Library: Exchange Utility Tasks window, doubleclick on the Create Client Filepacks icon. The Execute Task dialog is displayed: 4. Select the appropriate options in the Task Options section and the task endpoint and profile manager from the respective scrolling lists in the Execution Targets section. When you click Execute or skcapelif tneilc etaerc 34 Version 2.0

55 Execute & Dismiss, the Create Client Filepacks dialog is displayed. Distributing Clients 5. Complete the following text fields: Filepack Identifier Enter an identifier for the file pack. This identifier will be displayed with the file pack icon on the Tivoli desktop. Client Version skcapelif tneilc etaerc Tivoli Manager for Exchange User s Guide 35

56 Toggle by clicking the appropriate radio button. Windows Version Toggle by clicking the appropriate radio button. Target Temp Directory Enter the name of the temporary directory where the files will be distributed. If supplied, the format is drive:\directory name. If not supplied, the default directory is C:\TMP\MEX. Source Host Enter the host name of the managed node where the files and directories referenced in the file package reside. Client Code Directory Enter the directory where the client code resides. This is the directory where the install files are located for the Microsoft Outlook client, or where the.cab files are located for the Microsoft Exchange client. (V5 Clients only) Remove Installation Files? Toggle to specify, if after a successful installation, the installation files should be removed. Removing the files will not allow the product to be uninstalled. Target Install Path Enter the directory path where the client will be installed. If supplied, the format is drive:\directory name. If not supplied, the default directory is C:\Program Files\Microsoft Office. Use User s Configuration Files? Toggle the option to use the custom.stf and.prf user configuration files found in the User s Configuration Files directory or use those created by the Install task by clicking the appropriate radio button. User s Configuration Files Directory Enter the directory where the custom configuration files reside. If using custom configuration files, you can specify the path in the Source Host field where these configuration files are located. If not supplied, the default location is the value entered in the Client Code Directory field. 36 Version 2.0

57 Exchange Server Name If you are not using the custom configuration files, enter the Microsoft Exchange Server name to connect to. CD Key If you are installing Microsoft Outlook, enter the CD key provided with your Microsoft Outlook CD-ROM. The hyphens are optional. 6. After completing all the fields, click Set & Execute to create the file pack in the Exchange Client Filepacks profile manager. Distributing Clients Distributing File Packs Two profile icons are created in the Exchange Client Filepacks profile manager for each file pack created. The profile icon labeled <file pack identifier>(client version) is the profile that you distribute to the client machine. This profile contains the Microsoft Exchange client binaries along with a nested image of the pre- and post-installation processing scripts. Always distribute this profile. The nested profile icon contains the pre- and post-installation scripts. This profile is nested in the other profile and is automatically distributed with the other profile. Never distribute the nested profile separately. Before distributing the file packs, ensure that the subscribers list for the profile manager has been updated with the clients. After you have set the subscribers for the profile manager, the file packs can be distributed. From the Exchange Client Filepacks profile manager, double-click on the profile to be distributed to display the File Package Properties dialog. Update the dialog as appropriate, and select File Package > Distribute when ready to distribute. Notes: After distribution, the client machine must be manually re-booted in order for the installed client to work properly. In order for client filepacks to distribute properly to Windows 95 and Windows 98 machines, the CONFIG.SYS file on each Windows 95 and Windows 98 machine being distributed to needs to be updated by adding the following line. Then reboot the machine. SHELL=path\COMMAND.COM /E:4096 /P Tivoli Manager for Exchange User s Guide 37

58 where: path full path name of where COMMAND.COM is installed on the machine, usually C: This is needed in addition to the required Software Distribution patch on the TMR server to distribute from. See the Tivoli Manager for Exchange Release Notes for more information about required patches. Refer to the TME 10 Software Distribution User s Guide for information about distributing file packs. Before and After Installation Processing The Tivoli software distribution process includes before-installation processing and after-installation processing. Free space checking is one of the processing features provided by the Manager for Exchange. The amount of free space required is automatically calculated by the client selected. The target system is checked for adequate free space before installation begins. When the before-installation processing is complete, the installation files are distributed and placed on the target (client) machine in the directory specified in the Target Temp Directory field. After-installation processing runs a script that invokes the setup command to install the client software. When custom.stf and.prf files are specified when the file pack is created, these files will be used during the installation process to further customize the client software. The installation files are not removed from the temporary directory. 38 Version 2.0

59 5 5.Monitoring Exchange Servers This chapter explains how to use and customize Microsoft Exchange monitors. The Tivoli Manager for Exchange (Manager for Exchange) provides several monitor collections to enable remote monitoring of Microsoft Exchange services Performance statistics Overall performance of Microsoft Exchange Due to the differences in the performance data between the versions of the Microsoft Exchange Server application, a separate monitor collection is provided for each version of Microsoft Exchange that the Manager for Exchange supports. You should ONLY run the performance monitors from a collection against servers running the same version of Microsoft Exchange Server, otherwise the monitors may fail to run properly. For example, monitors from the MSExchangeV5 collection should only be run against servers running Microsoft Exchange Server 5.0. Like any Tivoli Distributed Monitoring monitor, these Microsoft Exchange-specific monitors can be customized. For example, you may want to set the severity or threshold of the monitors. Additionally, you may want to add more monitors to the default set. For additional information, see the TME 10 Distributed Monitoring User s Guide. Monitoring Exchange Servers Adding Monitors To add a monitor to those already provided by Microsoft Exchange, do the following: Tivoli Manager for Exchange User s Guide 39

60 1. From the Tivoli desktop, double-click the Manager for Exchange icon. The Policy Region: Manager for Exchange window is displayed: 2. Double-click on the Exchange Monitors icon. The Profile Manager window is displayed. 3. In the Profiles section of the window, double-click on the icon for your release of Microsoft Exchange. The TME 10 Distributed Monitoring Profile Properties window is displayed: wodniw seitreporp eliforp yrtnes 40 Version 2.0

61 4. Click Add Monitor to display the Add Monitor to TME 10 Distributed Monitoring Profile window. Monitoring Exchange Servers wodniw eliforp yrtnes/ilovit ot rotinom dda 5. Select the monitoring collection for which you want to display the available monitors by selecting a collection name such as MSExchangeV5 in the Monitoring Collections scrolling list. Select the monitor you want to add, such as Disk space available, in the Monitoring Sources scrolling list. The selected monitor Tivoli Manager for Exchange User s Guide 41

62 arguments are displayed in the Monitor Arguments area of the dialog. 6. When the selected monitor requires an argument, a text field is displayed in the Monitor Arguments box of the window. The argument can be entered either directly into the text field from the keyboard or by selecting it from a list of arguments that is displayed by clicking on the button to the right of the text field. Note: When entering arguments, keep in mind that they are both case and space sensitive. If a monitor fails due to an argument that is not valid, the only way to determine that it failed is to examine the debug log for that monitor. 7. Click Add Empty to add the selected monitoring source. The figure below is the result of clicking Add Empty for the Disk Space Available monitor. 8. Enter the information in the Edit Monitor dialog s text fields, and then click Change & Close. The monitor is added and the TME 10 Distributed Monitoring Profile Properties dialog is displayed. wodniw rotinom yrtnes tide 42 Version 2.0

63 9. To add another monitor, repeat steps 4 through 7. To close the TME 10 Distributed Monitoring Profile Properties dialog, select Profile > Close from the menu bar and then click Save & Exit in the displayed Confirm dialog. 10. After you have added and edited the desired monitors, you must distribute the profiles to start monitoring. You can drag and drop the monitor profile onto the desired subscriber in the profile manager to distribute the monitor profile. See the TME 10 Distributed Monitoring User s Guide for more information. Understanding the Monitors The Microsoft Exchange monitors supported by Manager for Exchange are categorized as: Microsoft Exchange Monitoring Collections Additional Microsoft Exchange-specific monitors Predefined Monitors Monitoring Exchange Servers Microsoft Exchange Monitoring Collections The Manager for Exchange supports all the performance counters that Microsoft Exchange Server provides. This enables you to monitor any of the performance counters available. For each of the monitoring sources (Microsoft Exchange services) listed below, you can select specific counters from a provided list. Some of the sources may also have an instance argument that you can input or select from a list. The values for the performance monitors are retrieved from the NT performance database. The Manager for Exchange does not calculate these values. For many Exchange metrics, it is difficult to provide default thresholds and actions because every implementation is unique. For these statistics, Tivoli recommends that customers baseline their environment for 2-4 weeks to determine Average, Low, and High values. Based on this information, Tivoli Manager for Exchange monitors can be configured for the environment. Tivoli Manager for Exchange User s Guide 43

64 Manager for Exchange provides performance monitors and counters for the Microsoft Exchange Version 5.0 and 5.5 monitoring sources listed below. See Appendix G. Performance Monitor Counters, on page 161 for the counters associated with each of the performance monitors. MSExchangeDB (Version 5.0 only) MSExchangeDS MSExchangeIMC MSExchangeIS MSExchangeIS Private MSExchangeIS Public MSExchangeMSMI MSExchangeMTA MSExchangeMTA Connections MSExchangePCMTA MSExchangeCCMC MSExchange Internet Protocols Additional monitoring sources for Microsoft Exchange Version 5.5 include: MSDatabase MSExchangeES Additional Microsoft Exchange-Specific Monitors The other Microsoft Exchange-specific monitors are: Available Memory Returns the amount of virtual free memory in megabytes. Database/Log Usage Returns the number of megabytes used by database or log file directories. You specify which database or directory should be checked by selecting from a list. Note that there may be some overlap. For example, the Message Transfer Agent (MTA), the MTADB database, and the MTARUN temporary running directory may use the same directory to store information. 44 Version 2.0

65 Disk Space Available Returns the amount of available space in megabytes on the disk where the Microsoft Exchange server is installed. Disk Space Usage Returns the number of megabytes used for a Microsoft Exchange server directory or file. Event Adapter Status Returns up if the NT event adapter service, TECNTAdapter, is running, otherwise returns down. MailPing Listener This monitor returns the amount of time, in seconds, it takes for a mail message to be sent and the acknowledgment to be returned. MailPing Listener tests the entire system and verifies that users are getting adequate response times. MailPing Listener listens on an asynchronous channel for mail ping results from the TivoliMailPing service. This is the actual response time monitor. Mail response thresholds are set on this monitor. Any thresholds set against the MailPing Listener monitor should be set in seconds. The TivoliMailPing service requires that a TivoliMailPing profile exists on the endpoint where this service will be created. This profile should be configured with the name of the sending Exchange server and the sending mailbox. When thresholds are the same for multiple mailping services, they can share a listener, otherwise create a new listener. For example, if Server A and Server B are expected to have the same response time and the thresholds are the same, these servers can share a listener (named mailping in the figure below). If Server C is on a slow link and the Monitoring Exchange Servers Tivoli Manager for Exchange User s Guide 45

66 expected results would be much slower, then create a new listener for Server C (mailpingc in the figure below). In the figure above, the MailPing Listener monitor has been configured on Exchange servers A, B, and C. A MailPing Listener monitor with a Listener Name set to mailping is distributed to servers A and B. A MailPing Listener monitor with a Listener Name set to mailpingc is distributed to server C. Test mail will be sent from servers A and B to user Recv PingD on server D; and from server C to Recv PingE on server E. The listener mailping, on servers A and B, is listening for a response from Recv PingD on server D. The listener mailpingc is listening for a response from Recv PingE on server E. Configuring and Testing the MailPing Listener Monitor Before configuring the MailPing Listener monitor, verify that mailboxes exist on the sending and receiving machines. Verify that mail sent from the sender appears in the receiver s mailbox. Configuring and testing the Manager for Exchange MailPing Listener monitor involves the following steps: 1. Running the Configure MailPing Listener Monitor task rotinom renetsilgnipliam erugifnoc 46 Version 2.0

67 2. Configuring TivoliMailPing service context 3. Creating a TivoliMailPing profile 4. Adding/setting Tivoli administrator login 5. Creating and deploying a MailPing Listener monitor instance 6. Starting the MailPing Listener monitor Each of these steps is discussed below. 1. Running the Configure MailPing Listener Monitor Task This task installs an NT service named TivoliMailPing on the endpoint. The task also makes changes to the Windows NT registry for use by the monitor (see Appendix H. Registry Information, on page 177). The Configure MailPing Listener Monitor task should be run against the Microsoft Exchange server endpoint that will be sending the test message. Follow these steps to run this task: a. From the Manager for Exchange utilities task library, doubleclick the Configure MailPing Listener Monitor task icon to display the Execute Task dialog. b. After completing the fields in this dialog, click Execute to display the Configure MailPing Listener Monitor dialog. Monitoring Exchange Servers rotinom renetsilgnipliam erugifnoc c. Fill in the task arguments as follows: Tivoli Manager for Exchange User s Guide 47

68 Mailbox where test message will be sent: ID where the test message should be delivered Polling Interval (minutes): How often in minutes the monitor should fire. The default value is 30. Listener Name: Name of the MailPing Listener that will receive the results of the TivoliMailPing service operation. The default value is mailping. 2. Configuring TivoliMailPing Service Context Perform the following steps: a. Login to the endpoint where the service was installed (task execution endpoint) as an administrator and set up the context in which the monitor will operate. b. From the Start menu icon on the NT desktop, select Settings > Control Panel.. From the Control Panel window, doubleclick the Services icon and then double-click the TivoliMailPing service icon in the displayed list. c. Click This account, and then enter the User Name and Password of the user you would like the service to run under. You can enter userids in the normal Universal Naming Convention (UNC) format (DOMAIN\userid). This user will send the mail. 48 Version 2.0

69 The user must have the Logon as a service NT user right. When you enter the user name and password, NT automatically grants this right. 3. Creating a TivoliMailPing Profile The MailPing Listener monitor uses a profile named TivoliMailPing that must be set up on the sending Exchange server machine. Follow these steps to set up the profile: a. Logon to the NT Server with the same account you specified as the account under which to run the TivoliMailPing service; that is, use the same account you specified when setting up the context of the TivoliMailPing service. b. Select Control Panel > Mail & Fax. c. Select Show Profiles. d. Select an existing profile such as Microsoft Outlook, and then select Copy. e. In the New Profile Name box enter TivoliMailPing (no spaces) xxx Monitoring Exchange Servers Tivoli Manager for Exchange User s Guide 49

70 f. Click OK. xxx g. Select Properties for the TivoliMailPing profile. h. Select Properties for Microsoft Exchange Server. i. In the Microsoft Exchange Server field, specify the Exchange server name on that machine. j. In the Mailbox field, enter a user mailbox on the server you specified in the previous step. The MailPing service uses this mailbox as the originator of the test message (the From field). Select the Check Name box to verify it is a valid mailbox. 50 Version 2.0

71 k. Click OK, OK again, and then Close. xxx 4. Adding/Setting Tivoli Administrator Login Assign to a TME Administrator login list the login for the userid you specified in step 2 on page 48 (also see Chapter 3 in the Tivoli Framework User s Guide). Note: The TME administrator must have at least the admin role. Minimally, you can create a new administrator with only the mailping logins and the admin role. 5. Creating and Deploying a MailPing Listener Monitor Instance MailPing Listener monitor instances are defined in a Distributed Monitoring profile. You can create one or more instances of the MailPing Listener in the same profile as your other Exchange monitors (technically, you can create this monitor in any Distributed Monitoring profile). Follow these steps to create an instance: a. Create an instance of the MailPing Listener monitor specifying a listener name. This name should match the name you Monitoring Exchange Servers Tivoli Manager for Exchange User s Guide 51

72 specified in the Listener Name field when you ran the Configure MailPing Listener Monitor task. b. Set the thresholds for the monitor to trigger. The response level can be set to always when testing to insure the monitor has been set up correctly. The monitor returns a -1 value when anything pertaining to MailPing monitor operations fails. This value should be set as an error threshold on the MailPing Listener monitor. The monitor also returns a -1 value if any message takes longer than 20 minutes to be delivered. The monitoring schedule is set with the polling interval specified in the Configure MailPing Listener Monitor task. Thus this option will not appear on Edit Monitor dialog. c. Deploy the monitor by distributing the Distributed Monitoring profile to the endpoints that will be sending the messages. These are the same endpoints where you configured the monitor. 6. Starting the MailPing Listener Monitor After distributing the monitor, run the Start_Stop MailPing Listener Monitor task to start the monitor. This task will start the TivoliMailPing service which then sends messages at the specified interval to the designated receiver. The service is set to start automatically when the machine starts up. After a reboot and any restart of the TivoliMailPing service, MailPing Listener monitor execution is delayed for 5 minutes. This delay allows time for the Microsoft Exchange Server to start. Thus, the MailPing Listener monitor will not fail because the Microsoft Exchange Server is in the process of starting. After 5 minutes, mail should appear in the receiver s mailbox. Depending on how you have set the monitor s triggers, you may see a response at the TMR. TivoliMailPing Service The TivoliMailPing service is created by the Configure MailPing Listener Monitor task. This NT service performs the actual mail ping operation. That is, this service sends the test messages, and then collects the response information. The service then sends the results of the 52 Version 2.0

73 operation to Distributed Monitoring by means of the asynchronous MailPing Listener monitor. The TivoliMailPing service reads the NT registry to obtain start-up information. See Appendix H. Registry Information, on page 177 for a list of the registry information. Removing Test Messages The messages will have a subject line of Test - Delete. Test messages can be automatically deleted by using the Inbox Assistant tool available with the Microsoft Exchange client. With this tool you can set up rules to automatically remove test messages. Performance Counters Enables you to monitor any Microsoft Exchange performance counter by specifying the object, counter, and optionally, instance for the performance counter. Note: Specify arguments exactly as they are defined including capitalization and spacing. Server Status Checks the status of the key services that comprise a Microsoft Exchange Server. Returns up if all four of the services are running, otherwise returns down. The services are: MSExchangeSA: Microsoft Exchange System Attendant MSExchangeMTA: Microsoft Exchange Message Transfer Agent MSExchangeIS: Microsoft Exchange Information Store MSExchangeDS: Microsoft Exchange Directory To ensure that the server icons reflect the current status of the servers, select the Send Enterprise Console event response on the Edit Sentry Monitor dialog for the trigger conditions you desire. A TEC rule has been defined to update the icon state based on the results of this monitor. Monitoring Exchange Servers Predefined Monitors During installation, both for a new install and an upgrade, Manager for Exchange provides the Server Status predefined monitor. This monitor Tivoli Manager for Exchange User s Guide 53

74 returns a string value (up, down) indicating whether the 4 core Exchange services (System Attendant, Directory Service, Information Store, and MSExchange MTA) are running. The monitor is added to the Microsoft;Exchange;5.5 or Microsoft;Exchange;5.0 distributed monitoring profile. The table below shows the properties of this monitor. Use the values in the table as an example of how you can set up a monitor. Arguments Response Level Trigger When Threshold Default Actions Frequency (minutes) None Fatal Becomes unavailable 1. Send Notice 2. Change Icon 5 None Critical Is down or unavailable 1. Change Icon 5 None Warning Becomes available 1. Send Notice 5 2. Change Icon None Always Sentry Graphable Event 5 54 Version 2.0

75 t l 6 6.Tasks for Managing Resources gni s i weivr evo sksat tnmeeganma Tivoli Manager for Exchange (Manager for Exchange) includes a collection of tasks to help you perform functions related to managing Microsoft Exchange resources. Server tasks are contained within the server task library in the Manager for Exchange policy region and are described in Microsoft Exchange Server Tasks on page 58. Utility tasks can be executed from the utility task library and are described in Manager for Exchange Utility Tasks on page 64. See Chapter 7. Managing Exchange Server Events, on page 71 for a discussion of the tasks contained in the Tivoli Enterprise Console (TEC) task library. Jobs are provided for many of the tasks. A job is a task with the endpoints already defined. Jobs for the tasks defined in this chapter are set up to execute against all Manager for Exchange profile managers. When you start a task, you can specify the servers or other endpoints on which to run the task. Some tasks are provided on the pop-up menu for each server icon. Right-click on a server icon to display the icon's popup menu. For more information, see page 27. Select Task Description from the pop-up menu to view information about the window s text fields. For complete instructions on how to use tasks and jobs, refer to the TME 10 Framework User s Guide. Tasks for Managing Resources Listing Tasks To list tasks provided by Manager for Exchange: Tivoli Manager for Exchange User s Guide 55

76 1. From the Tivoli desktop, double-click on the Module for Exchange icon to display the Policy Region: Manager for Exchange window. 2. To display the available server tasks, double-click on the Exchange Server Tasks icon. The Task Library: Exchange Server Tasks window is displayed. Running Tasks To run a task: yalpsid sksat eht gnidnapxe 56 Version 2.0

77 1. Double-click on the task icon and complete the displayed Execute Task dialog. 2. Click Execute & Dismiss to start the task. A Configure Task Arguments dialog, shown in the following figure, may display so that you can provide more information for the task. Not all tasks present this dialog. When a Configure Task Arguments dialog is xobgolaid ksat etucexe EMT Tasks for Managing Resources Tivoli Manager for Exchange User s Guide 57

78 presented, enter the information and then click Set & Execute to start the task. Microsoft Exchange Server Tasks Manager for Exchange provides the following types of tasks for the Microsoft Exchange Server: xobgolaid stnemugra ksat erugifnoc 58 Version 2.0

79 Type of Task Tasks TMR Role Target Server Information Display Server Status Display Server Info mex_admin or mex_senior MSExchang e endpoint Display Exchange Info Display Statistics Mailbox Information Mailbox Info mex_admin or mex_senior MSExchang e endpoint Database and Disk Utility Run ISINTEG Run EDBUTIL/ESEUT IL mex_admin or mex_senior MSExchang e endpoint Run MTACHECK Diagnostic and Control Services Server Information Tasks Diagnostic Logging-Set Diagnostic Logging-View Start Services Stop Services Tasks that provide server information include: mex_admin or mex_senior MSExchang e endpoint Tasks for Managing Resources Display Server Status This task returns the status of each of the installed Microsoft Exchange services on the target server. Some possible status values are running and stopped. Tivoli Manager for Exchange User s Guide 59

80 Display Server Info This task returns server information for the target server such as Microsoft Exchange Server version and site, and environment information such as the Windows NT version and domain name. Display Exchange Info This task displays the list of sites or mailboxes for a server. You must choose either the Mailbox or Site information type from the displayed dialog. If the task runs successfully, but there is no data that met the criteria, an empty list will be displayed. Note: The Display Exchange Info and Mailbox Info tasks must be run in the context of a domain administrator. Both of these tasks call the admin Exchange utility which must be run in the context of an Exchange administrator. The domain administrator is automatically mapped to an Exchange administrator. By default, Manager for Exchange runs tasks as $root_user which, on NT, maps to the local administrator. On PDCs and BDCs, the local administrator maps to the domain administrator and thus, for these two types of servers, the tasks run successfully. To run the tasks on servers that are not PDCs or BDCs, you will need to manually change the execution context of the two tasks. You can do this by performing the following steps: 1. From the Policy Region: Manager for Exchange window, select Properties > Managed Resource Policies. 2. In the displayed Managed Resource Policies dialog, ensure that BasicTaskLibrary is set as the value in the Validation Policy text field. 3. Remove the check from the Validation Enabled checkbox. Click Set. 4. From the Policy Region: Manager for Exchange window, double-click on the Exchange Server Tasks icon. 5. While holding down the right mouse button on the Display Exchange Info task icon, select Edit Task from the pull-down menu. 60 Version 2.0

81 Display Statistics 6. In the User Name text field of the Edit Task dialog, replace $root_user with the domain administrator account (domain_name\administrator) and click Change & Close. 7. Repeat steps 5 through 6 for the Mailbox Info task. 8. Enable the Validation Policy by checking the Validation Enabled checkbox in the Managed Resource Policies dialog. Click Set & Close. This task displays the list of performance counters and their current values for a server. You can select the performance objects for which statistics will be gathered. Note: Mailbox Information Tasks Depending on the objects selected, the task can take a long time to run. Ensure that the timeout execution parameter for the task is set to at least several minutes. Tasks that provide mailbox information include: Mailbox Info This task returns mailbox information, including alias name, addresses, and other information available in the mailbox objects for the server. The note in the Display Exchange Info section above also applies to this task. Database and Disk Utility Tasks Database and disk utility tasks include: Tasks for Managing Resources Run ISINTEG This task runs on the target server, finding and eliminating common errors from the Microsoft Exchange Server public and private information store databases. Tivoli Manager for Exchange User s Guide 61

82 Note: This task stops the MSExchangeIS service before it runs the Run ISINTEG utility and starts the MSExchangeIS service after the utility is complete. This task also restarts any other Microsoft Exchange Server service that was stopped along with MSExchangeIS. You can run this task in browse, fix, dump, or patch mode: In browse mode, Run ISINTEG searches the information store databases for table errors, incorrect reference counts, and unreferenced objects. It can just browse the database and display the results. In fix mode, Run ISINTEG searches the information store databases for table errors, incorrect reference counts, and unreferenced objects. It corrects the errors it finds, and displays the results. In dump mode, the utility dumps the store data. In patch mode, the utility repairs the information store that results from an off-line backup. A dialog is presented where you can select specific options for the command. Run EDBUTIL/ESEUTIL This task runs the EDBUTIL or ESEUTIL utilities on the target server, providing disk defragmentation and consistency checking. These utilities can check the Private, Public, or Directory databases. A dialog is presented where you can select specific options for the task. Notes: The EDBUTIL utility has been replaced by the ESEUTIL utility in version 5.5 of the Microsoft Exchange Server application. This task stops the MSExchangeIS service before it runs the utility and starts the MSExchangeIS service after the utility is complete. If the Directory database is specified, the task will also stop the MSExchangeDS service before it runs the utility and will start the MSExchangeDS service after the utility is complete. 62 Version 2.0

83 Any dependent service that is stopped as a result of this task will be restarted. Run MTACHECK This task runs the MTACHECK utility on the target server, enabling you to check and correct the queues used by the message transfer agent. A dialog is presented where you can select specific options for the task. Notes: This task stops the MSExchangeMTA service before it runs the Run MTACHECK utility and starts the MSExchangeMTA service after the utility is complete. This task also restarts any other Microsoft Exchange Server service that was stopped along with MSExchangeMTA. Diagnostic and Control Services Tasks Tasks that control services include: Diagnostic Logging-Set and -View The Diagnostic Logging-Set and Diagnostic Logging-View tasks enable you to set and view the diagnostic logging levels for Microsoft Exchange services as follows: The Diagnostic Logging-Set task enables you to set the diagnostic logging level for a service. There are five choices for logging levels: No Change, None, Low, Medium, and High. If No Change is specified, then the current logging level is not changed. Note: The logging level for all categories for a service will be set. The Diagnostic Logging-View task displays the current Microsoft Exchange diagnostics logging level for each category within a service. Tasks for Managing Resources Tivoli Manager for Exchange User s Guide 63

84 Start and Stop Services The Start Services and Stop Services tasks update the server icon status (for more information, see Determining Server Status on page 30), and start and stop the services that comprise a Microsoft Exchange Server as follows: Start Services This task starts one or more services that comprise a Microsoft Exchange Server. A dialog is presented to you to select the services to start. Selecting a service to start may start more than one service because of dependencies between services. For example, starting MSExchangeIS also starts MSExchangeSA. Stop Services This task stops one or more services that comprise a Microsoft Exchange Server. A dialog is presented to you to select the services to stop. Selecting a service to stop may stop more than one service because of dependencies between services. For example, stopping MSExchangeSA will also stop all other Microsoft Exchange services. Manager for Exchange Utility Tasks Manager for Exchange provides utility tasks to help you manage Microsoft Exchange servers running on your endpoints. A resource role of mex_admin or mex_senior is required to perform these tasks. Tasks Discover Exchange Servers Set Icon State Start Debugging Stop Debugging List Debug Logs Remove Debug Logs Target Exchange Server (endpoint) MSExchange endpoint MSExchange endpoint MSExchange endpoint MSExchange endpoint MSExchange endpoint 64 Version 2.0

85 Tasks Migrate Exchange Servers Delete Migrated Exchange Objects Create Client Filepacks Start Monitors Stop Monitors Configure MailPing Listener Monitor Start-Stop MailPing Listener Monitor Target MSExchange managed nodes TMR server TMR server MSExchange endpoint MSExchange endpoint Exchange Server (endpoint) MSExchange endpoint All of these tasks can be executed from the utility task library in the Manager for Exchange policy region on the Tivoli desktop. Discover Exchange Servers This task automatically discovers and creates a Microsoft Exchange Server instance for each endpoint it is run against where Microsoft Exchange Server is installed. It will do the following: Retrieve the Microsoft Exchange Server name and version. Create a Microsoft Exchange Server instance using the server name as the server alias name. If you have specified that the instance should be automatically subscribed to the default profile manager, it will add the subscription to the profile manager for that version. Create an icon for the server, identified by its alias name, in the Policy Region: Manager for Exchange window. The icon reflects the current status of the server. If you have specified that the instance should be automatically subscribed to the default profile manager, it will add the subscription to the profile manager for that version. This task is useful for initially populating the Manager for Exchange policy region with server instances and can be run periodically to add Tasks for Managing Resources Tivoli Manager for Exchange User s Guide 65

86 Set Icon State new servers. For more information, see Creating Microsoft Exchange Server Instances on page 24. Notes: When this task is run, the Execution Mode field should be set to serial. When running this task against more than one endpoint, the Timeout field should be increased to 600. Execution Mode is set in the Execute Task dialog. This task will set or change the state of a Microsoft Exchange Server icon in the Manager for Exchange policy region. This task changes only the icon; it does not affect the operation of the server. A dialog is presented which enables you to select a state for the icon. Note: Start Debugging This task is used by a rule provided with the Manager for Exchange to update the icons representing Microsoft Exchange Servers. You can use this task from the user interface if you think that the icon does not properly represent the server's status. You can also use it in rules that you create. This task does not change the state of the icons in the profile manager windows. These reflect the icon at the time of the subscription. This task Turns on debug tracing at the endpoint for all the tasks and monitors shipped with Manager for Exchange Helps to resolve problems if a task or monitor is not running properly Displays endpoint environment variables on the Tivoli desktop A separate log file is written on the endpoint to a directory (%LCF_DATDIR%) for each task or monitor that is run while debug tracing is on. 66 Version 2.0

87 Stop Debugging This task turns off debug tracing on endpoints for all the tasks and monitors shipped with Manager for Exchange. List Debug Logs This task lists the current debug mode setting and a list of debug logs on the endpoint. You can check the option to display the contents of the debug logs. Remove Debug Logs This task lists the current debug mode setting and removes all the debug logs on the endpoint. Migrate Exchange Servers If you have upgraded from TME 10 Module for Exchange 1.1 to Manager for Exchange 2.0, you may already have MSExchange objects defined for your managed nodes. After installing endpoints on these managed nodes, to use Manager for Exchange 2.0 to manage these endpoints you will need to migrate the managed node objects to endpoint objects. To migrate, you can either create a new MSExchange instance or migrate the old managed node MSExchange instance by using the Migrate Exchange Servers task. To create a new MSExchange instance, see Creating Microsoft Exchange Server Instances on page 24 and Discover Exchange Servers on page 65. The Migrate Exchange Servers task will migrate an MSExchange object for an MSExchange server on a managed node to an MSExchange object for an MSEXchange server on an endpoint. Note: To use this task, the target managed node must have been upgraded to Manager for Exchange Version 2.0 with all the prerequisites that are required for the TMR. See the Tivoli Manager for Exchange Release Notes for all TMR prerequisite software. Tasks for Managing Resources Tivoli Manager for Exchange User s Guide 67

88 This task is run against the MSExchange managed node instance. Only version 5.0 and 5.5 MSExchange servers can be migrated. MSExchange 4.0 servers must first be upgraded to version 5.0 or 5.5. This task will: Create a new MSExchange server object for the endpoint Rename the old MSExchange object with the suffix _old Place the renamed object into a subpolicy region Subscribe the newly created object to the profile managers to which the old MSExchange object was subscribed To migrate, perform the following steps: 1. Double-click on the Manager for Exchange Policy Region icon to display the Policy Region: Manager for Exchange window. 2. Double-click on the Exchange Utility Tasks task library icon to display the utility tasks. 3. Double-click on the Migrate Exchange Servers task icon and fill in the Execute Task window. 4. When you click Execute, the Migrate Exchange Servers input dialog will be displayed. golaidstnemugra ksat srevres egnahcxeetargim 5. Complete the following text fields: New Alias Name The name for the MSExchange object and label for the icon. If left blank, this defaults to the current name of the 68 Version 2.0

89 MSExchange object. The old object will be renamed by adding the suffix _old. If you are running the task against multiple nodes, you must use the default for the alias name, otherwise the task will fail because you will be trying to create instances with duplicate names. Gateway The Gateway where the MSExchange object is created. If left blank, it will default to the name of the endpoint s gateway. Subscribe to the default profile manager? Choose whether or not to subscribe to the default profile manager. Delete Migrated Exchange Objects This task is used to remove migrated Exchange objects in the Migrated Exchange Objects subpolicy region. This task should be used only if the new Exchange objects created with the Migrate Exchange Servers task are verified and operational. This task will delete all Exchange objects in the Migrated Exchange Objects subpolicy region. This task is run against the TMR server. Create Client Filepacks Start Monitors This task creates and saves file packs used in distributing Microsoft Exchange client software. For more information, see Creating File Packs on page 33. This task starts all the monitors (except the MailPing Listener monitor) from the MSExchangeV5 and MSExchangeV55 collections that have been distributed to the server. The task will start only the monitor instances from these collections; other monitor instances on the server will not be started. This task can be used to quickly restart all of the MSExchange monitors after they have been stopped. Note: This task does not change the status settings for the monitors at the TMR. Tasks for Managing Resources Tivoli Manager for Exchange User s Guide 69

90 Stop Monitors This task stops all the monitors (except the MailPing Listener monitor) from the MSExchangeV5 and MSExchangeV55 collections that have been distributed to the server. The task will stop only the monitor instances from these collections; other monitor instances on the server will not be stopped. This task can be used to quickly stop all of the MSExchange monitors when a server is down. Note: This task does not change the status settings for the monitors at the TMR. Configure MailPing Listener Monitor This task configures the MailPing Listener monitor to run on a specified endpoint. It will install a new service on the endpoint called TivoliMailPing. It will then write information to the registry that the MailPing Service will use during start-up. See Configuring and Testing the MailPing Listener Monitor on page 46 for more information about this task. Start_Stop MailPing Listener Monitor This task will start or stop the MailPing Listener monitor depending on which radio button is selected. 70 Version 2.0

91 7 7.Managing Exchange Server Events Managing Exchange Server Events The Microsoft Exchange server application issues event notifications to describe events affecting Microsoft Exchange resources. Tivoli Manager for Exchange (Manager for Exchange) utilizes the Tivoli Enterprise Console event adapter for Windows NT (NT event adapter) to convert Microsoft Exchange events to the Tivoli Enterprise Console (TEC) format, and provides a set of event classes that enable you to view and work with these events at your TEC. This chapter describes how to manage Microsoft Exchange events using tasks contained in the TEC task library. The following table lists the context and target node for the tasks: Task Target TMR Roles Configure Event Server Event server senior or mex_senior Configure Event Console Event server senior or mex_senior Configure Event Adapter Exchange server (endpoint) senior or mex_senior Start Event Adapter MSExchange endpoint mex_senior or mex_admin Tivoli Manager for Exchange User s Guide 71

92 Task Target TMR Roles Stop Event Adapter MSExchange endpoint mex_senior or mex_admin To work with Microsoft Exchange events at your TEC, you must configure both ends of the connections and configure the TEC: 1. Configure the event server to recognize Microsoft Exchange events and the process rules concerning the events. Run the Configure Event Server task against the event server to be configured. 2. Configure an event console. Run the Configure Event Console task to assign the newly created event group to the appropriate event console. For more information, see Configuring the Event Console on page Run the Configure Event Adapter task to configure the NT event adapter for each endpoint where the NT event adapter has been installed. For more information, see Configuring the NT Event Adapter on page 77. Configuring the Event Server The Configure Event Server task configures an event server for Manager for Exchange. The task performs the following: Imports Manager for Exchange event classes Imports the Tivoli Distributed Monitoring event classes if they are not already present Imports the Manager for Exchange rule set that provides automated responses to many events Compiles the rule base to incorporate new classes and rules Loads the new rule base Creates an event source (MSEXCHANGE) for Manager for Exchange events Creates a new event group called MSExchange Event Group 72 Version 2.0

93 Updates the forwarding server location, if specified Stops and restarts the event server to incorporate these changes You can configure more than one event server for a Tivoli Management Region (TMR). When you have multiple TMRs, you must configure at least one event server. The Manager for Exchange includes a set of event classes and rules specific to Microsoft Exchange. Events received from NT event adapters are included in the MSExchange Event Group. To create this group and set up your event server to process Microsoft Exchange events, do the following: 1. From the Tivoli desktop, double-click on the Manager for Exchange icon to display the Policy Region:Manager for Exchange window. 2. Double-click on the Exchange TEC Tasks icon to display the Task Library: Exchange TEC Tasks window. 3. Double-click on the Configure Event Server task icon and complete the displayed Execute Task dialog. 4. Click Execute & Dismiss to display the Configure Event Server dialog. Managing Exchange Server Events xob golaid revrestneve erugifnoc Tivoli Manager for Exchange User s Guide 73

94 5. Enter the name for the new or existing rule base in the New (or existing) Rule Base Name field. The default name is MSExchange. Note: You should not modify the default rule base, therefore do not enter default in this field. 6. Enter the rule base to clone in the Rule Base to clone (if new) field. If you are not creating a new rule base, leave this field blank. If you are creating a new rule base and you want to retain the current information, enter the current rule base name. The default value for this field is default. 7. Enter the path for the new rule base in the Path for new Rule Base (if new) field. The default value for this field is /usr/tec_rules/msexchange. If you are not creating a new rule base, leave this field blank. Note: Currently, TEC does not allow blanks in the path name. 8. When you want to forward Microsoft Exchange event messages to another TEC, enter the name of the managed node to which events should be forwarded in the Managed Node to Forward Events (Optional) field. To use this option, you will also need a TEC rule to forward the events. The TME 10 Enterprise Console Rule Builder s Guide describes the steps for building and modifying rules. 9. Click Set and Execute to execute the task. The Configure Event Server Output dialog displays the job status after the task is completed. The Configure Event Server task always writes a log file named %TMP%\mex_config_evtsvr.log (on UNIX: $TMP/mex_config_evtsvr.log). On Windows NT platforms, TMP is the directory pointed to by the wtemp command. If any problems are encountered when running this task, review the log to help determine the problem. This task can be run more than once without having to restore the Tivoli database. Therefore, if you encounter a problem, rerun the task. If you specify a rulebase name that exists, then it will be updated. If the Manager for Exchange baroc files and rules have been loaded, the Configure Event Server task will delete and reload them to pick up any changes. 74 Version 2.0

95 Configuring the Event Console The Configure Event Console task adds filters to the event console and assigns groups. This task is run against the TMR server and should be run only after running the Configure Event Server task. Perform the following steps to configure an event console: 1. From the Tivoli desktop, double-click on the Manager for Exchange icon to display the Policy Region:Manager for Exchange window. 2. Double-click on the Exchange TEC Tasks icon to display the Task Library: Exchange TEC Tasks window. 3. Double-click on the Configure Event Console task icon and complete the displayed Execute Task dialog. 4. Click Execute & Dismiss to display the Configure Event Console dialog. 5. Enter the name of the event console to be configured. The name is the same name as the event console that already exists on the administrator s desktop. 6. Click Set and Execute to execute the task. The Configure Event Console Output dialog displays the job status after the task is completed. After running the Configure Event Console task, start the TEC by double-clicking on the TEC icon on the desktop. A pair of TME 10 Managing Exchange Server Events Tivoli Manager for Exchange User s Guide 75

96 Enterprise Console windows appear showing the newly added event group and event source. puorg tneve 76 Version 2.0

97 Managing Exchange Server Events If the Configure Event Console task was not run against the TEC event server, the following error message will be displayed: > /tmp/taskaaaa21183.bat[3]: wlsassigneg: not found > + diagmsg Failed to assign MSExchange Event Group to... Rerun the task against the TEC event server. Configuring the NT Event Adapter To receive Microsoft Exchange events, ensure that the NT event adapter is installed and operational on each endpoint where the Microsoft Exchange Server application is running. Complete the installation of the adapter before running the task to configure the NT event adapter. The NT event adapter is packaged with the TEC product and requires the TEC Adapter Configuration Facility (ACF). secruos tneve Tivoli Manager for Exchange User s Guide 77

98 Note: The TEC Adapter Configuration Facility is a prerequisite for installing the NT event adapter. See the Tivoli Manager for Exchange Release Notes for the most current information regarding prerequisite software. To configure the NT event adapter, run the Configure Event Adapter task for the endpoints where the NT event adapter has been installed. This enables the NT event adapter for each Microsoft Exchange Server to receive Microsoft Exchange events, convert them to a TEC format, and send them to the event server. Running this task: Merges the Exchange event format file definitions with the existing NT event adapter format file. This is the file that defines the event format, event class, and the slot name and slot value pairs for each valid event. The Exchange event format file contains the definitions for the Microsoft Exchange events. The file name is mex_events.fmt. Stops and restarts the NT event adapter to incorporate the changes. See the Tivoli Enterprise Console Adapters Guide for more information about the NT event adapter. Perform the following steps to configure the NT event adapter: 1. From the Tivoli desktop, double-click on the Manager for Exchange icon to display the Policy Region:Manager for Exchange window. 2. Double-click on the Exchange TEC Tasks icon to display the Task Library: Exchange TEC Tasks window. 3. Double-click on the Configure Event Adapter task icon and complete the displayed Execute Task dialog. 4. Click Execute & Dismiss to run the task. Starting and Stopping the NT Event Adapter Manager for Exchange supplies tasks to stop and start NT event adapters on the endpoint as follows: Start Event Adapter Starts the NT event adapter service, TECNTAdapter, on the node. 78 Version 2.0

99 Stop Event Adapter Stops the NT event adapter service, TECNTAdapter, on the node. Monitoring the NT Event Adapter Manager for Exchange provides the event adapter status monitor to monitor the status of the NT event log adapter. For more information, see Event Adapter Status on page 45. Managing Exchange Server Events Filtering Events There may be certain types of Microsoft Exchange events that you do not want to appear on your TEC, because you regard them as harmless or unlikely to require action. The Tivoli Management Framework provides the following methods for you to filter out events that you do not want to see: You can specify that the event is not to be forwarded from the managed node to the event server. In this case, you specify filter criteria in the NT event adapter configuration file. The filter criteria include information about which events should or should not be sent to the event server. Depending on the frequency of the harmless events, this option can save you some network traffic. The use of this file is described in the TME 10 Enterprise Console Adapters Guide. You can create new rules to exclude the event. When you do this, the event will be forwarded to the event server but will be eliminated by the rules engine. The TME 10 Enterprise Console Rule Builder s Guide describes the steps for building and modifying rules. You can exclude classes of events using the event console s user interface. Refer to the TME 10 Enterprise Console User s Guide for information. Tivoli Manager for Exchange User s Guide 79

100 80 Version 2.0

101 8 8.Tivoli GEM Instrumentation To manage Microsoft Exchange servers from the Tivoli Global Enterprise Manager (Tivoli GEM) console, you must install: Tivoli Manager for Exchange Tivoli GEM Instrumentation for Exchange This chapter provides an overview of Tivoli GEM Instrumentation for Exchange. It also describes the installation prerequisites and the steps to install Tivoli GEM Instrumentation for Exchange. Tivoli GEM defines the concept of a business system to organize related applications. Tivoli GEM consists of a Tivoli GEM server that runs as an application on a managed node and a Tivoli GEM console running as a Java-based client. Tivoli GEM uses application instrumentation to get the necessary data to display and manipulate business systems such as Microsoft Exchange. Tivoli GEM Instrumentation Understanding the Tivoli GEM Server The Tivoli GEM server interacts with instrumented applications such as Tivoli Manager for Exchange (Manager for Exchange) to provide information for display on the Tivoli GEM console. The Tivoli GEM server is the recipient of heartbeat events from instrumented application components and determines the business system to which a component belongs. The Tivoli GEM server also queries instrumented applications for related components and the status of their monitors. This information creates and maintains a view of each business system s configuration and its availability. The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable against a component. These tasks appear in context-sensitive menus on the Tivoli Manager for Exchange User s Guide 81

102 Tivoli GEM console. The Tivoli GEM server also stores files on behalf of the Tivoli GEM console, including icons, backgrounds, help files, log files, customization views, and settings. Understanding the Tivoli GEM Console The Tivoli GEM console graphically displays the business system information from the Tivoli GEM server. The Tivoli GEM console displays each component as a separate icon, draws lines between icons to denote links, and uses color to indicate the status of each component and the status of the entire business system. As the Tivoli GEM server receives status updates pertaining to the business systems, it updates the Tivoli GEM console, enabling the Tivoli GEM console to display the real-time status of the business system. Tivoli GEM also supports manual aggregation from the Tivoli GEM console which allows users to drag and drop icons into aggregates that they define. Tivoli GEM Instrumentation Event Handling Tivoli GEM Event Enablement must be installed and configured on the event server in order for Tivoli GEM events to be supported by TEC. The Tivoli GEM Event Enablement configuration includes defining the APM_HEARTBEAT and APM_THRESHOLD event classes to TEC and defining the Tivoli GEM server(s) to which the Tivoli GEM events will be forwarded. Tivoli GEM Instrumentation for Exchange also includes TEC rules, in the form gemmsexchange_*, that forward all Manager for Exchange monitor events to the Tivoli GEM server. These rules must be defined in the current rule base. The Configure Event Server task can be used to add the gemmsexchange_* rules to the current rule base. See GEM Event Rules on page 117 for more information about event classes and rules. The Tivoli GEM server discovers the Microsoft Exchange components upon receipt of heartbeat events. As the Tivoli GEM server receives monitor and status updates for the Microsoft Exchange business system, it updates the Tivoli GEM console. Instrumentation Files, Libraries, and Profiles Successful installation of Tivoli GEM Instrumentation for Exchange creates task libraries, monitor collections, and file packages. The following is an overview of the resulting desktop structure (indentation conveys the nesting structure): 82 Version 2.0

103 Top-Level Policy Region: Applications_hostname-region Policy Region: PR_Exchange20GEM_Default_hostname-region Task Libraries: TL_Exchange20GEM_2.0._Default_Exchg50Microsoft_5.0._ho stname-region Profile Managers: PM_Exchg50Microsoft_5.0._Endpoint File Packages (containing instrumentation code): FP_Microsoft Exchange_2.0._Default_Microsoft Exchange_2.0._hostname-region The file packages must be distributed to Tivoli endpoints on which the Microsoft Exchange resources exist in order to have the instrumentation code available for local execution. Tasks The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable against a component. The task menu appears on the console when a component icon is highlighted and the right-mouse button is clicked. The tasks enable Tivoli GEM users to perform actions on the component instance and have the task results returned to the Tivoli GEM console. The tasks that are supported for each component are defined in business system mapping and software component definition files that reside on the Tivoli GEM server. The installation of the Tivoli GEM Instrumentation for Exchange creates a task library for the Microsoft Exchange Server instrumented components. Each task library contains the tasks that are supported from Tivoli GEM for that component. See Microsoft Exchange Server Tasks on page 99 for a list of Tivoli GEM instrumentation tasks. Tivoli GEM Instrumentation Monitors The Tivoli GEM console displays an icon for each monitor instance that is supported. If a monitor supports multiple arguments, then each argument (or combination of arguments) defines an instance. The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable to monitors. The task menu appears on the console when a monitor icon is highlighted and the right-mouse button is clicked. The tasks enable Tivoli GEM users to perform monitor actions from the Tivoli GEM console. Tivoli Manager for Exchange User s Guide 83

104 The tasks that are supported for the monitors are defined in software component definition files that reside on the Tivoli GEM server. See Monitors on page 104 for a list of supported monitors. Preparing to Install Tivoli GEM Instrumentation Consider the topics in the following sections before installing Tivoli GEM Instrumentation for Exchange. Tivoli Management Regions The Tivoli Management Regions (TMRs) should be properly configured before installing Tivoli GEM Instrumentation for Exchange. Ensure that the TMR is configured to contain the Tivoli GEM server. On interconnected TMRs, ensure that these TMRs have exchanged resource information. Administrators Tivoli administrators need the following authorization roles: To install Tivoli GEM Instrumentation for Exchange, at least install_product authority is required. To execute tasks from the Tivoli GEM console, mex_admin or mex_senior authority is required for the user ID that you use to log on to the Tivoli GEM console. Installation Prerequisites 1. Ensure that all prerequisite software is installed and that you are running on a supported operating system. See the Tivoli Global Enterprise Manager Release Notes for details about supported hardware and operating systems, prerequisite software, and disk space requirements. Also see the Tivoli GEM Instrumentation for Exchange Release Notes section in the Tivoli Manager for Exchange Release Notes. 2. Manager for Exchange and the TEC must be installed and configured before installing Tivoli GEM Instrumentation for Exchange. See Chapter 2. Installing Manager for Exchange, on page Version 2.0

105 3. Install the Tivoli GEM server. 4. Install and configure Tivoli GEM Event Enablement on the event server so that events will be forwarded to the Tivoli GEM server. 5. Install the Tivoli GEM console. Installing and Configuring Tivoli GEM Instrumentation Components The following table shows the location of the components: Component Java Development Kit (JDK) x Java Development Kit (JDK) 1.1.7b or x Tivoli GEM Server Target Nodes TMR Server X Endpoints X Tivoli GEM Console X Tivoli GEM Instrumentation Instrumentation B*DF, CDF, GDF, and icon files X Instrumentation task libraries, monitor collections X Instrumentation file packages X To install Tivoli GEM Instrumentation for Exchange, follow the steps in the remaining sections of this chapter. Copying B*DF, CDF, GDF, and Icon Files Copy the Tivoli GEM business description files (B*DFs), component description files (CDFs), global description file (GDF), and icon files from the Manager for Exchange CD-ROM to the Tivoli GEM server. Tivoli Manager for Exchange User s Guide 85

106 For more information on these files and their destination directories, see Appendix C. Business and Component Files, on page 121. Installing the Java Development Kit Install the Java Development Kit (JDK), at a minimum, on the TMR server and all endpoints where Tivoli GEM instrumentation will be used. Do not install the Java Runtime Environment. To install the JDK, perform the following steps: 1. Back up the Tivoli database. Tivoli also recommends making a TAR or WINZIP backup of your Tivoli directory tree. 2. Obtain the JDK version that you need. For information about where to get JDK, refer to the Tivoli Manager for Exchange Release Notes. 3. Read all of the following before proceeding. a. The GEM Instrumentation must use JDK Note: Tivoli GEM Instrumentation for Exchange 2.0 is associated with endpoints only; there are no managed nodes for Exchange servers ). Change the environment variables as follows: (1) Add jdk1.2.2/bin to PATH. (2) Create CLASSPATH if it doesn't exist. If you have to create CLASSPATH use: CLASSPATH. Note: JDK doesn't need CLASSPATH, but your classes and Tivoli's classes will be appended onto CLASSPATH. b. The Tivoli GEM Console must use JDK 1.1.7b or JDK Change the environment variables as follows: (1) Add jdk1.1.7b\bin or jdk1.1.8\bin to PATH. (2) Add \jdk1.1.7b\lib\classes.zip or \jdk1.1.8\lib\classes.zip to CLASSPATH. c. If Tivoli GEM instrumentation is not installed on the Tivoli GEM Console node, then everything is fine. d. If Tivoli GEM instrumentation is installed on the GEM Console node, then there is a conflict because Tivoli GEM instrumentation needs JDK and the Tivoli GEM Console needs JDK 1.1.7b or JDK Tivoli GEM 86 Version 2.0

107 instrumentation provides the solution via the set_java.sh file. Define the java path for Tivoli GEM instrumentation by creating a file called $BINDIR/../generic_unix/set_java.sh as follows for NT: #!/bin/sh PATH=drivename:/jdk1.2.2/bin;$PATH This will create the correct PATH and CLASSPATH each time Tivoli GEM instrumentation runs. e. If you installed both JDK and JDK 1.1.7b or JDK and JDK on the same node and still get the swing error in the $DBDIR/tmp/GemConsole_nodename.log after having done the above, then rename the java.exe in %SystemRoot%\system32 to something like javanot.exe. This will force the search for the java.exe in the path you specify. For this to take effect, you must reboot the computer. f. The swing error occurs because the swing class is not used in JDK but is used in the Tivoli GEM Console The error looks as follows: java.lang.noclassdeffounderror: com/sun/java/swing/jframe at java.lang.classloader.defineclass0 (Native Method) at java.lang.classloader.defineclass (ClassLoader.java:442) at java.security.secureclassloader.defineclass (SecureClassLoader.java:101) at java.net.urlclassloader.defineclass (URLClassLoader.java:248) at java.net.urlclassloader.access$1 (URLClassLoader.java:216) at java.net.urlclassloader$1.run (URLClassLoader.java:197) at java.security.accesscontroller.doprivileged (Native Method) at java.net.urlclassloader.findclass (URLClassLoader.java:191) Tivoli GEM Instrumentation Tivoli Manager for Exchange User s Guide 87

108 at java.lang.classloader.loadclass (ClassLoader.java, Compiled Code) at sun.misc.launcher$appclassloader.loadclass (Launcher.java:275) at java.lang.classloader.loadclass (ClassLoader.java:247) Exception in thread "main" 4. For more information about access to JDK and instructions about running the jdk*_win32.exe install package from SUN, read the release notes on the Java url. 5. Stop and restart the Tivoli GEM server to incorporate the changes. See the Tivoli Manager for Exchange Release Notes for more information about supported levels of JDK and the URLs where they may be found for installation. Creating User Groups and Logon IDs for the Tivoli GEM Console To log on to the Tivoli GEM Console, the user ID and password must be defined on the managed node where the Tivoli GEM server is running. The Tivoli GEM Console logon ID will be rejected unless it belongs to either the tsadmn (administrator) or tsuser (user) groups. If the ID belongs to the administrator group, you can log on with administrator access. If the ID belongs to the user group, you cannot log on with administrator access. Add security authorizations to the ID that will be used to start the Tivoli GEM server as described in Setting Security for the Windows NT Operating System on page 89. Windows NT Use the User Manager applet to create the group or groups, then add the logon ID or IDs that will be used to sign on. AIX Add the logon ID or IDs to the appropriate group or groups using SMIT > Security & Users > Groups > Change/Show Characteristics of a Group. 88 Version 2.0

109 HP/UX Add the logon ID or IDs to the appropriate group or groups using sam > Accounts for Users and Groups SUN Solaris Use the admintool command to add the logon ID or IDs that will be used to sign onto the server. Setting Security for the Windows NT Operating System If you are using Windows NT, additional security configuration steps are required; no additional security configuration is required for UNIX platforms. Add the following user rights to the user ID under which the Tivoli GEM server will run so that it will do the following: Act as part of the operating system. Replace a process level token. Logon as a service. This is optional and only needs to be set if the Tivoli GEM server is run as an NT service. Follow these instructions to set user rights: 1. Log on to an ID with administrator authority. 2. Click Start > Programs > Administrative Tools > User Manager (or User Manager for Domains for NT servers). 3. Click Policies > User Rights. 4. Check the Show Advanced User Rights check box. 5. Scroll through the Right list and select Act as part of the operating system. 6. The Grant to list displays groups and users that are currently granted this right. If your target user ID is not listed, click Add. 7. Click Show Users. 8. Select the target user ID under which the Tivoli GEM server will run and click Add. 9. Repeat this process for Replace a process level token. 10. If the Tivoli GEM server is going to be run as a service, repeat this process for Log on as a service. Tivoli GEM Instrumentation Tivoli Manager for Exchange User s Guide 89

110 11. Log off and log back on as the target ID for the user rights to take effect. Installing Tivoli GEM Instrumentation Tivoli GEM Instrumentation for Exchange is installed in the PR_Microsoft Exchange_Default_hostname-region policy region which is within the Applications_hostname-region policy region on the Tivoli desktop. Install Tivoli GEM Instrumentation for Exchange (task libraries and monitor collections) on the TMR server and on all the Tivoli endpoints running Microsoft Exchange Servers. Follow these steps for the installation: 1. Back up the Tivoli database. Tivoli also recommends making a TAR or WINZIP backup of your Tivoli directory tree. 2. From the desktop menu bar, click Install > Install Product to display the Install Product dialog. 3. Click Select Media to display the File Browser dialog. 4. Enter the path to the Tivoli GEM Instrumentation for Exchange installation files in the Path Name text field. This should normally be the path to the Manager for Exchange CD-ROM. 90 Version 2.0

111 5. Click Set Media & Close. The File Browser dialog is closed and the Install Product dialog is displayed. Tivoli GEM Instrumentation 6. Select the version of Tivoli GEM Instrumentation for Microsoft Exchange that you want to install from the Select Product to Install scrolling list. wodniwllatsni Tivoli Manager for Exchange User s Guide 91

112 7. Click the targets on which to install from the Available Clients scrolling list and click the left arrow button. The selections are moved to the Clients to Install On scrolling list. 8. Click Install & Close. The Product Install window is displayed, listing the actions that will be taken when you complete the installation process. 9. Click Continue Install on the Product Install window to complete the Tivoli GEM Instrumentation for Exchange installation. The window displays messages showing the progress of the installation and a completion message when the installation is finished. 10. Click Close. 11. After installing Tivoli GEM Instrumentation for Exchange, backup the Tivoli database. Defects, Limitations, and Workarounds If a Tivoli GEM Instrumentation for Exchange module fails to install on a Tivoli endpoint, view the %TMP%\install.log (on UNIX: $TMP/install.log) file for additional information about the cause of the installation failure. On Windows NT, TMP is the directory pointed to by the wtemp command. 92 Version 2.0

113 9 9.Initializing Tivoli GEM Instrumentation This chapter describes the following steps that you must perform before you can use Tivoli GEM Instrumentation for Exchange: 1. Configure the Tivoli Enterprise Console (TEC) event server to forward Tivoli GEM instrumentation events to the Tivoli GEM server as described in Configuring Tivoli GEM Event Handling. 2. Distribute the Tivoli GEM Instrumentation for Exchange file packages as described on page Subscribing to and Distributing the File Packages on page To discover Microsoft Exchange server resources on the Tivoli GEM console, distribute the heartbeat monitors to the Tivoli endpoints on which the Microsoft Exchange resources exist. See Subscribing to and Distributing the Heartbeat Monitor on page Ensure that administrators are assigned the appropriate authorization roles. This chapter also describes how to confirm Tivoli GEM discovery of Microsoft Exchange servers. Initializing Tivoli GEM Instrumentation Configuring Tivoli GEM Event Handling The Tivoli GEM instrumentation rule base must be defined to the TEC event server to enable Tivoli GEM monitor threshold events to be Tivoli Manager for Exchange User s Guide 93

114 created and forwarded to the Tivoli GEM server. This enables status for specific Microsoft Exchange Servers to be displayed on the Tivoli GEM console. To configure Tivoli GEM event handling, do the following: 1. Enter the following command to find out the name of the active rule base: wlscurrb 2. Verify that the APM_HEARTBEAT and the APM_THRESHOLD event classes are defined for the active rule base. Enter the following command to list the defined event classes: wlsrbclass active_rulebase Replace active_rulebase with the name of the active rule base. 3. Verify that the interapp.rls rule base is installed. Enter the following command to list the rules that are installed: wlsrbrules active_rulebase 4. From the Manager for Exchange policy region, run the Configure Event Server task in the Exchange TEC Tasks library. This task installs the gemexchg.rls rule base on the TEC event server. This rule base filters Tivoli GEM-supported Manager for Exchange monitor events and from them creates APM_THRESHOLD events. Ensure that the name of the rule base that is entered in the Rule Base To Clone (If New) field on the Configure Event Server dialog contains the classes and rules defined in step 5.. Do not use Default as the value in this field or transmission of Tivoli GEM events to the Tivoli GEM server will fail. 5. IF APM_HEARTBEAT, APM_THRESHOLD, and interapp.rls are installed, continue to the next step. If APM_HEARTBEAT, APM_THRESHOLD, and interapp.rls are not installed, you have not configured Tivoli GEM Event Enablement. Configure Tivoli GEM Event Enablement before continuing with this procedure. Go to directory %BINDIR%\TDS\Eventservice and run ihsttec.sh. Put in the hostname of your Tivoli GEM server and make sure you answer yes to Forwarding events from 94 Version 2.0

115 TEC to the GEM server and yes to Do you want to enable GEM to send events to TEC. Finding and correcting problems of not getting events forwarded: File ihsttec.cfg has the name of the Tivoli GEM server that TEC will forward to. This must be a name recognized by the TEC server. You may want to put in the TEC server's hosts file. File ihsttec.out has the last event that TEC recognized to be forwarded. For more information, refer to the TME 10 Global Enterprise Manager Installation and User s Guide. Configuring Microsoft Exchange Servers Before doing Tivoli GEM instrumentation activities, create at least one Microsoft Exchange server instance. See Creating Microsoft Exchange Server Instances on page 24 for more information. Subscribing to and Distributing the File Packages Distribute the Tivoli GEM instrumentation file package to the Tivoliendpoints on which the Microsoft Exchange resources exist in order to have the instrumentation code available for local execution. Note: Never distribute Tivoli GEM Instrumentation filepacks for Microsoft Exchange 5.0 and 5.5 on the same endpoint. Do the following: 1. From the Tivoli desktop, double-click the Applications_hostname-region icon to display the Policy Region: Applications_hostname-region window. 2. Double-click on the PR_Exchange20GEM_Default_hostnameregion icon to display the Policy Region: PR_Exchange20GEM_Default_hostname-region window. Initializing Tivoli GEM Instrumentation Tivoli Manager for Exchange User s Guide 95

116 3. Double-click on the PM_Exchg50Microsoft_5.0_Endpoint icon to display the Profile Manager window. 4. To distribute the Tivoli GEM instrumentation file package to the Microsoft Exchange endpoints, double-click on the FP_Exchange20GEM_2.0_Default_Exchg50Microsoft_5.0_ hostname-region_endpoint icon. Subscribing to and Distributing the Heartbeat Monitor After you install Tivoli GEM instrumentation, distribute the heartbeat monitor and other monitors to all endpoints running Microsoft Exchange server. If Microsoft Exchange server resources run on the TMR server, then distribute the heartbeat monitor to the TMR server. Tivoli GEM receives monitor status through TEC events that are forwarded to the Tivoli GEM server. A heartbeat event is only sent for active Microsoft Exchange servers. wodniwreganameliforp 96 Version 2.0

117 The heartbeat monitor is added to the Microsoft;Exchange;5.0 and Microsoft;Exchange;5.5 monitor profiles. To enable a heartbeat monitor for each Microsoft Exchange server, distribute the profiles listed above to the TMR server and the endpoints running an Microsoft Exchange server. To subscribe and distribute the Microsoft Exchange server profiles to the machine on which the TMR server runs and to all endpoints, do the following: 1. From the Tivoli desktop, double-click on the Manager for Exchange icon to display the Policy Region: Manager for Exchange window. Double-click on the Exchange Monitors icon to display the Profile Manager dialog: Initializing Tivoli GEM Instrumentation wodniw reganam eliforp Tivoli Manager for Exchange User s Guide 97

118 a. From the Profile Manager window s pull-down menu, select Subscribers. b. Ensure that your endpoints, and the TMR server, are in the Current Subscribers list. Otherwise, select your target instances from the Available to become Subscribers scrolling list and transfer the entries to the Current Subscribers list. c. Click Set Subscriptions & Close. 2. To distribute the profile from the Profile Manager menu, select Distribute. 3. Select Distribute Now from the pop-up menu. The profile is distributed. Confirming Resource Discovery Observe the active Tivoli GEM console to ensure that the Microsoft Exchange Server icon is displayed as it is discovered. The heartbeat monitor for Microsoft Exchange Servers sends a heartbeat event for each Microsoft Exchange Server resource at an interval specified by the previously distributed heartbeat monitor. When the event server receives a heartbeat event, it forwards the event to the Tivoli GEM server and an icon is displayed on the Tivoli GEM console. 98 Version 2.0

119 t Instrumentation Tasks and Monitors Instrumentation Tasks and Monitors pots t rats After you have successfully installed Tivoli GEM Instrumentation for Exchange, you can use tasks and monitors to manage your Microsoft Exchange Servers from the Tivoli GEM console. This chapter describes Tivoli GEM instrumentation tasks and monitors. Locating and Running Tasks sdlohserht tes lavretni gni l lop Tivoli GEM instrumentation tasks, in addition to Tivoli Manager for Exchange (Manager for Exchange) tasks, are contained in the PR_Exchange20GEM_Default_hostname-region described in Instrumentation Files, Libraries, and Profiles on page 82. On the Tivoli GEM console, you can run instrumented tasks from the Microsoft Exchange Server icon's pop-up menu. Tivoli GEM Instrumentation Tasks tes seulav yr euq sdlohserht yreuq etat s yr euq noi atnmeur tsni GEM i lovit sksat It is recommended that the Tivoli GEM instrumentation tasks be run from the Tivoli GEM console. Microsoft Exchange Server Tasks Tivoli GEM instrumentation provides Manager for Exchange with tasks on the pop-up menu available from each Microsoft Exchange Server Tivoli Manager for Exchange User s Guide 99

120 icon on the Tivoli GEM console. Manager for Exchange also provides additional configuration tasks that are not accessible from the Tivoli GEM console, but are accessible from the Tivoli desktop: Query State Returns UP or DOWN indicating whether the Microsoft Exchange Server is running. If the four key services (MSExchangeSA, MSExchangeDS, MSExchangeIS, and MSExchangeMTA) are running, the task will return UP. Start Starts the Microsoft Exchange Server. This task tries to start the four key Microsoft Exchange services. The task is considered successful when the four key services are started successfully. Stop Stops the Microsoft Exchange Server. The task stops the MSExchangeSA service that in turn stops all the other Microsoft Exchange services. The task is considered successful when the four key services are stopped successfully. The following subset of Manager for Exchange tasks are also supported by Tivoli GEM Instrumentation for the Microsoft Exchange Server component: Display Exchange Info Display Server Info Diagnostic Logging-Set Diagnostic Logging-View Display Server Status Display Statistics Mailbox Info Run EDBUTIL/ESEUTIL Run ISINTEG Run MTACHECK Stop Services Start Services Start Debugging Stop Debugging Start Monitors Stop Monitors See Chapter 6. Tasks for Managing Resources, on page 55 for more information about these tasks. 100 Version 2.0

121 Navigating to Microsoft Exchange Server Resources You can view the Microsoft Exchange Server icons from the Tivoli GEM console. Right-click individual Microsoft Exchange Server resources to access the pop-up menu from which you can select tasks and monitors. To locate a specific Microsoft Exchange Server resource: 1. From the tree view of Tivoli GEM resources, double-click the Applications icon. The displayed Applications tree view contains Application icons as shown below. Instrumentation Tasks and Monitors If the view is empty, ensure that you have distributed a profile containing the heartbeat monitor to Microsoft Exchange Server resources and that the Microsoft Exchange Server is running. For more information on distributing the heartbeat monitor, see Subscribing to and Distributing the Heartbeat Monitor on page 96. noci noitagergga Tivoli Manager for Exchange User s Guide 101

122 2. Double-click on the Aggregation icon to display individual Microsoft Exchange server icons. 3. Right-click on a server icon to display a list of tasks that can be run. snoci revres egnahcxe tfosorcim 102 Version 2.0

123 4. Double-click on a server icon to display the monitors associated with the server. Instrumentation Tasks and Monitors snocirotinom 5. From the menu bar, select View Ó Show as Details Using the Tear-Away Log Before starting a task, open the tear-away log provided by the Tivoli GEM console. The log provides current messages that show the progress of tasks you run. Do the following: 1. From the Tivoli GEM console menu bar, select Options. 2. Click the Tear Away Log button. Starting a Sample Task Before you start a task, open a tear-away log. To perform a task such as starting a queue manager: 1. Right-click an Microsoft Exchange Server icon. On the pop-up menu, select Start. Tivoli Manager for Exchange User s Guide 103

124 2. The GEM Log window provides a progress report listing of Microsoft Exchange Server operations as they complete. In this example, the messages indicate that the Microsoft Exchange Server has started. Monitors Tivoli GEM Instrumentation provides support for Microsoft Exchange Server monitors. Microsoft Exchange Server Monitors Tivoli GEM Instrumentation installs a new monitor collection (Microsoft Exchange) and provides the heartbeat monitor, as well as support for all Manager for Exchange-specific monitors. For more information on Microsoft Exchange Server monitors, see Chapter 5. Monitoring Exchange Servers, on page 39. Topology views on the Tivoli GEM console display status for the following events: Tivoli GEM-specific TEC events, such as a heartbeat event Threshold events showing status, such as the Microsoft Exchange Server Status monitor event sent by Manager for Exchangespecific monitors yalpsidgol MEG 104 Version 2.0