Installation Guide. NetIQ AppManager. Version 5.0.1

Transcription

1 Installation Guide NetIQ AppManager Version 5.0.1

2 Legal Notice THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time. Copyright NetIQ Corporation, all rights reserved. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non- DOD acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement. ActiveAgent, ActiveAnalytics, ActiveKnowledge, ActiveReporting, ADcheck, AppAnalyzer, Application Scanner, AppManager, AuditTrack, AutoSync, Chariot, ClusterTrends, CommerceTrends, Configuration Assessor, ConfigurationManager, the cube logo design, DBTrends, DiagnosticManager, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, End2End, Exchange Administrator, Exchange Migrator, Extended Management Pack, FastTrends, File Security Administrator, Firewall Appliance Analyzer, Firewall Reporting Center, Firewall Suite, Ganymede, the Ganymede logo, Ganymede Software, Group Policy Administrator, Intergreat, Knowledge Scripts, Log Analyzer, Migrate.Monitor.Manage, Mission Critical Software, Mission Critical Software for E-Business, the Mission Critical Software logo, MP3check, NetIQ, the NetIQ logo, the NetIQ Partner Network design, NetWare Migrator, OnePoint, the OnePoint logo, Operations Manager, Qcheck, RecoveryManager, Security Analyzer, Security Manager, Server Consolidator, SQLcheck, VigilEnt, Visitor Mean Business, Visitor Relationship Management, Vivinet, W logo, WebTrends, WebTrends Analysis Suite, WebTrends Data Collection Server, WebTrends for Content Management Systems, WebTrends Intelligence Suite, WebTrends Live, WebTrends Network, WebTrends OLAP Manager, WebTrends Report Designer, WebTrends Reporting Center, WebTrends Warehouse, Work Smarter, WWWorld, and XMP are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.

3 Contents About this guide 7 Intended audience What s changed?... 8 Usingthisguide... 8 Conventionsusedinthisguide Usingonlinehelp Wheretogoformoreinformation Learning more about other NetIQ products Questions or suggestions? Contact us Chapter 1 About AppManager 15 What are the AppManager components? Understanding communication between components.. 19 Understanding reporting in AppManager Whatistheimpactonplanningandconfiguration? Chapter 2 Planning the installation 27 How much planning is required? Assemblingaprojectteam Defining project phases Evaluatingtheenvironmenttobemonitored Reviewingyournetworkconfiguration Planning management sites Planning system resources for AppManager

4 Sizing the AppManager repository Planning security Planning your management strategy Planning a staged deployment Documentingyourdecisionsandpolicies Chapter 3 Performing a pre-install check 53 Selectyourconfiguration Review system requirements Check account information Test network connections Checkdatabasecommunication Generateanencryptedkeyfile Runthepre-installationcheck Review the pre-installation report Avoidingcommoninstallationproblems Chapter 4 Starting installation 79 Gettingapreviewoftheinstallation Installing components in order Starting the AppManager setup program Specialinstallationscenarios Chapter 5 Installing the repository 87 Review the requirements for the repository Start the AppManager setup program Select the AppManager repository Create the repository database and database owner Installation Guide

5 Configure the repository data and log devices Completetheinstallation Installing the repository on a cluster Chapter 6 Installing the management server 101 Start the AppManager setup program Select AppManager management server Configure the connection to the repository Specify an account for the service to use Selectthesecuritylevel Configuretheportstouse Completetheinstallation Installing the management server on a cluster Chapter 7 Installing console programs 119 Starting the AppManager setup program Select the AppManager console Completetheinstallation Chapter 8 Installing AppManager agents 125 Installing agents in a Windows environment Installing agents locally using the setup program Installing agents from a centralized location Configuring agents for working in a cluster Installing agents on UNIX computers Contents 3

6 Chapter 9 Installing the Web management server 171 Starting the AppManager setup program Selectthewebmanagementserver Completetheinstallation ConfiguringWebservicesecurity AccessingchartsfromtheOperatorWebConsole Chapter 10 Configuring access after installing 177 GrantingusersaccesstoAppManager Configurationformonitoringhardware ConfigurationforsendingMAPImailasanaction Using the Security Manager to update information Working with AppManager connectors Chapter 11 Staging the deployment 199 Installinginalabenvironment Preparing to install the pilot group Running the recommended core Knowledge Scripts Adjustingthresholdsandintervals Moving to the next stage of deployment Expanding the scope of your deployment Reviewing and refining the deployment Moving beyond deployment to extend AppManager Roadmap for a staged deployment Installation Guide

7 Appendix A Updating license information 219 About AppManager license keys What if you don t know your license key number? Viewinglicenseinformation StartingLicenseManager Updatinganexpiredlicense Addingalicensekey Requestinglicensinginformation Importinglicensekeysfromafile Running a license report Appendix B Performing a silent installation 227 Understanding silent installation Creatingtheinstallationfile Copyingtheinstallationfiletoadirectory Running the setup program with the installation file Sampleinstallationfile Creating an installation file manually Performing a silent installation of the UNIX agent Appendix C Uninstalling AppManager 243 Deciding to uninstall AppManager Before uninstalling AppManager UsingAdd/RemoveProgramstouninstall Uninstalling AppManager on a remote computer Uninstalling the UNIX agent Contents 5

8 Appendix D Pre-installation requirements 249 General requirements for all components AppManager console AppManager management server AppManager repository AppManager Web management server AppManager Operator Web Console AppManager agent for Windows AppManager agent for UNIX Index Installation Guide

9 About this guide The NetIQ AppManager Suite (or AppManager) is a comprehensive solution for managing and monitoring the performance, availability, and server health for a broad spectrum of operating environments, applications, and server hardware. AppManager enables system administrators to view all of their servers and workstations from a central, easy-to-use console, providing complete visibility of critical server and application resources across the enterprise. With AppManager, administrative staffs can monitor computer and application resources, check for potential problems, initiate responsive actions, and gather performance data for real-time and historical reporting and analysis. Intended audience This Installation Guide provides information to ensure a successful installation of NetIQ AppManager components. This guide is intended for system administrators and users responsible for installing all or part of the AppManager Suite software. For information about working with AppManager, see the User Guide. For information about configuring and maintaining an AppManager site, see the Administrator Guide. For information about customizing AppManager Knowledge Scripts, see Developing Custom Knowledge Scripts. 7

10 What s changed? This release of AppManager includes many enhancements to the Operator Console, standard reporting, and documentation and extended support for monitoring new applications and UNIX computers. To learn more about what s new and for other late breaking information, see the Release Notes on the AppManager CD-ROM. Once the CD-ROM is inserted, an autorun program opens your default Web browser to the AppManager page. Click Release Notes for an overview of what s new in this release. For information about using new features, see the User Guide. Using this guide NetIQ recommends all users read all or part of the first eight chapters of this guide. Depending on your environment, you may want to read other portions of this installation guide selectively. Chapter 1, About AppManager, provides an overview of the AppManager components and their communication requirements. Chapter 2, Planning the installation, suggests what you should consider in planning your AppManager implementation. If you are planning an enterprise-wide deployment, it is recommended you review this chapter. Chapter 3, Performing a pre-install check, reviews key system, account and communication information you should check before you install and how to run the pre-installation check program to verify the configuration of your systems. Chapter 4, Starting installation, provides an overview of the installation process and the steps for starting the setup program. Chapter 5, Installing the repository, provides step-by-step instructions for installing the AppManager repository and discusses any special configuration issues that affect the repository installation, such as installing on a cluster. 8 Installation Guide

11 Chapter 6, Installing the management server, provides step-by-step instructions for installing the AppManager management server and discusses any special configuration issues that affect installation, such as installing on a cluster. Chapter 7, Installing console programs, provides step-by-step instructions for installing AppManager console programs. Chapter 8, Installing AppManager agents, provides step-by-step instructions for installing and configuring AppManager agents on your managed clients. Chapter 9, Installing the Web management server, provides step-by-step instructions for installing the AppManager Web management server. Chapter 10, Configuring access after installing, discusses final configuration instructions to ensure proper and efficient monitoring of your environment. Chapter 11, Staging the deployment, describes what to expect in a staged roll-out of AppManager, including a brief highlight of the key tasks undertaken in each stage. Appendix A, Updating license information, describes how to view and update AppManager license information. Appendix B, Performing a silent installation, describes how to create and use a silent installation file for installing AppManager components without user intervention. Appendix C, Uninstalling AppManager, describes how to remove AppManager programs and how to use the AppManagerUninstall Knowledge Script. Appendix D, Pre-installation requirements, summarizes the system requirements for AppManager. For application-specific installation and configuration issues, see the appmanager\documentation\supplements directory on the AppManager CD-ROM. About this guide 9

12 Conventions used in this guide The following conventions are used in this guide: Fixed-width font is used to highlight source code, program names or output, file names, and commands that you enter. An italicized fixed-width font is used to indicate variables. Bold text is used to emphasize commands, buttons, or user interface text, and to introduce new terms. Italics are used for book titles. Using online help AppManager provides task-based, reference, and context-sensitive online help. To access task-based online help or search for help topics, click Help Topics on the Help menu. To view context-sensitive help within dialog boxes, click the Help button or press F1. (Field-level or What s This help is not provided for individual dialog box controls.) You can get help on individual Knowledge Scripts while viewing the Values tab in the Properties dialog box by clicking Help or pressing F1, or by highlighting a Knowledge Script in the Knowledge Script pane and pressing F1. Online help is not provided for contributed, unsupported, or custom Knowledge Scripts. All AppManager documentation, including this guide, is available online in searchable Acrobat PDF files. 10 Installation Guide

13 Where to go for more information The AppManager documentation set includes several sources of information. Depending on your interests, you may want to explore some or all of these sources further: Upgrade and Migration Guide for complete information on how to upgrade from a previous version of AppManager. User Guide for complete information about running jobs, responding to events, creating reports, and working with AppManager console programs. Administrator Guide for information about maintaining an AppManager site, managing security, using command line options to handle AppManager tasks, and other advanced operations. Knowledge Script Guide for a brief description of what each Knowledge Script does. Developing Custom Knowledge Scripts for an introduction to writing your own custom Knowledge Scripts. Managed Objects Reference Guide for technical information about the most commonly used AppManager managed objects. (This guide does not document all AppManager managed objects.) The AppManager documentation set is available in Adobe Acrobat (PDF) format on the AppManager CD-ROM. Additionally, some application-specific installation and configuration information can be found in the appmanager\documentation\supplements folder on the CD-ROM and many resources are available on the NetIQ Online Support and Extended Support Web sites. For example: NetIQ Work Smarter guides provide tips, advice, and recommendations on monitoring specific applications or on special topics. You may want to occasionally check the NetIQ Online Support site for updated and new NetIQ Work Smarter guides. About this guide 11

14 Up-to-date information regarding the versions of products that AppManager supports can be found on the NetIQ Online Support Web site. Note You can access NetIQ Support without a password or registration. To access the Extended Support site, however, you must be a registered AppManager customer. In addition to the AppManager documentation, you may want to consult the documentation for your Windows or UNIX operating system, or other application- or system-specific documentation for reference and conceptual information. This background information can help you get the most out of your AppManager installation. Learning more about other NetIQ products NetIQ Corporation is a leading provider of intelligent e-business management software solutions for all components of your corporate infrastructure. These components include servers, networks, directories, Web servers, and various applications. NetIQ Corporation provides integrated products that simplify and unify directory, security, operations, and network performance management in your extended enterprise. NetIQ Corporation provides the following categories of products: Windows and Exchange Management The NetIQ Windows and Exchange Management products provide tools for managing, migrating, administering and analyzing your Windows and Exchange environments. These products include tools for setting and enforcing policies that govern user accounts, groups, resources, services, events, files, and folders, and products that automate time-consuming administration tasks. 12 Installation Guide

15 Performance and Availability Monitoring The NetIQ Performance and Availability products provide control and automation for monitoring the performance and service availability for your critical servers, applications, and devices, and extensive network monitoring capabilities to provide a complete, end-to-end management solution for e-business infrastructures. These products enable you to pinpoint existing and potential server and network problems and resolve those problems quickly and effectively. Security Management and Administration The NetIQ Security Management and Administration products enable you to administer, assess, enforce, and protect all aspects of security within your Windows environment. These products provide incident management and intrusion detection, vulnerability assessment, firewall reporting and analysis, and Windows security administration. Web Analytics The NetIQ Web Analytics products enable you to evaluate and analyze your Web site traffic and performance, as well as manage your visitor relationships. About this guide 13

16 Questions or suggestions? Contact us... NetIQ Corporation is a key Microsoft partner for operations management solutions, a Microsoft Certified Solution Provider, ADSI Partner, and Microsoft Gold Certified partner for security. NetIQ is headquartered in San Jose, California, with offices throughout the United States, Canada, Europe, and Asia. If you have questions or comments, we look forward to hearing from you. For information about contacting NetIQ, visit our Web site at From the Web site, you can get the latest news and information from Technical Support, Public Relations, Investor Relations, and Sales. In addition, you can find our office locations and a list of our current partners. To fill out an online Technical Support Request form or to provide comments or suggestions regarding AppManager, the AppManager documentation set, or online help, go to Support. 14 Installation Guide

17 Chapter 1 About AppManager AppManager is a client/server application with a multi-tier architecture. Before installing AppManager, it s important to understand this architecture and how AppManager components interact. Understanding how AppManager works will help you develop a workable implementation plan and ensure a successful deployment. If you aren t familiar with AppManager components and how these components communicate with each other, it s recommended you read this chapter for an overview. If you already understand the AppManager architecture, you may want to proceed to Chapter 2, Planning the installation, for guidelines to assist you in planning the implementation. For a more complete discussion of AppManager architecture, see the User Guide. What are the AppManager components? AppManager s flexible, multi-tier architecture consists of required and optional components. The components can be installed together on a single computer or separately on multiple computers. Each component has unique requirements or configuration options. The required components are: At least one AppManager Operator Console. An Operator Console is used to view and control the jobs that monitor and manage your computers and server applications. There are three Operator Console environments: the standard Windows interface 15

18 Operator Console, the Web-browser based Operator Web Console, and the MMC snap-in Operator Console MMC Snap-in. In addition to the Operator Console, AppManager includes several other console programs to help you manage your environment, such as the AppManager Security Manager and the Troubleshooter, which are installed automatically with the standard Operator Console. The AppManager agent. The AppManager agent is responsible for monitoring the managed computer s system and application resources, such as CPU utilization or active processes. For Windows computers, the AppManager agent consists of two Windows services (NetIQmc and NetIQccm), a local repository database, and at least one managed object that reside locally on each computer you are managing. For UNIX computers, the agent is a daemon and the supporting files and directories that provide data persistence (equivalent to the local repository) and access to system statistics (equivalent to managed objects). A Management server. The management server is a Windows service (NetIQms) that manages the event-driven communication between the AppManager repository and the AppManager agents. The AppManager repository. The repository is a SQL Server database that stores all of your management information. The optional components are: The AppManager Web management server. This component is required if you want to use the Operator Web Console to check the status of jobs and events, view charts and reports, run Knowledge Script jobs, and view details about the computers you are monitoring using a Web browser. The AppManager report agent. The report agent is an optional supplement to the AppManager agent that allows you to create and configure reports on the computers in your 16 Installation Guide

19 environment. You discover report-related elements on managed computers after installation to enable different types of reporting. The Distributed Event Console. This console allows you to view a summary of event information from one or more AppManager repositories in a single console. The Developer s Console Utilities. These utilities are used for developing custom Knowledge Scripts. When you run the AppManager Setup program, you select which components you want to install. As part of the planning process, you need to decide where to install these different components and how many of each component you need to effectively manage your environment. As an example, if the administrators who need to be able to view and respond to events are widely distributed, you may want to provide Operator Web Console access for the remote administrators. If you have support or Help Desk operators who need a summary of open events across repositories but don t need to run or stop jobs that monitor for events, you may want to provide this access through a Distributed Event Console. Chapter 1 About AppManager 17

20 The following figure illustrates a simplified installation with AppManager components installed across 20 computers. Distributed Event Console installed on DIVINE AppManager management server installed on TANGO Server group: NT, SMS Server group: Windows2000 AppManager repository installed on MOJO Server group: NT, Exchange Operator Console installed on DYNAMO SQL Server AppManager Web management server installed on IIS TAROT Server group: Windows2000, SQL 2000 Server group: NT only Agents on 15 managed computers. These are the servers and workstations you are monitoring (Optional) AppManager Operator Web Consoles using Microsoft Internet Explorer to access the Active Server Pages installed on TAROT 18 Installation Guide

21 Understanding communication between components When you install an AppManager agent on a computer, it becomes a managed client that you can monitor. You can then drag and drop Knowledge Scripts onto your managed client computers to configure the Knowledge Script jobs you want to run. Starting a job inserts a record into the AppManager repository s database, and the database update notifies the management server of the job request. This basic operation applies regardless of the operating environment you are monitoring. There are some differences, though, in communication, port requirements, and deployment options that do depend on the operating environments you intend to monitor. To help you plan the deployment of AppManager, you should consider the types of computers you need to monitor and understand the communication between AppManager components to ensure a successful implementation that suits your organization s needs: If you are planning to monitor only Windows-based agents, see Monitoring a Windows environment on page 20. If you are planning to monitor only UNIX-based agents, see Monitoring in a UNIX environment on page 21. If you plan to monitor a combination of Windows-based and UNIX-based agents, you should review the discussion of both the Windows and UNIX environments and Working with both Windows and UNIX computers on page 23. Once you install and configure all of the appropriate AppManager components, monitoring Windows and UNIX computers is a seamless process with no operational difference. Chapter 1 About AppManager 19

22 Monitoring a Windows environment When you start a job on Windows NT or Windows 2000 computers, the NetIQ AppManager Management Service (NetIQms) sends the job request to the NetIQ AppManager Client Resource Monitor service (NetIQmc). The NetIQmc service receives the request and runs the job locally. The basic flow is illustrated in the following diagram: 6 AppManager Operator Console 1 Knowledge Script job Managed client: MANGO 3 Knowledge Script job Event or data to Agent on be reported? MANGO runs the job Yes Job information recorded AppManager Repository 5 2 AppManager Management server 4 Event and/or data recorded As the agent runs a job, it uses the code in the Knowledge Script to collect whatever raw statistics or information it needs, such as the current CPU utilization or database lock activity. The method used to collect the requested information varies. For example, the script may check the value of performance counters, read log files, execute queries, or access system tables. Typically, in a Windows environment, scripts use an OLE automation call to one or more managed objects to get information. A managed object is a collection of lower-level COM/OLE objects, packaged in a DLL. The appropriate DLLs are copied to the managed client during setup when you select the servers and applications you want to monitor. 20 Installation Guide

23 Each time the Knowledge Script runs, it evaluates the information returned by the managed object and determines whether an event has occurred or data needs to be inserted into the repository. If an event condition is detected or a data point collected, the NetIQmc service notifies the NetIQ AppManager Client Communication service (NetIQccm). The NetIQccm service then communicates with the management server to upload the information to the repository. If the NetIQccm or NetIQmc service can t communicate with the management server for any reason (for example, because the network connection is down or you have intentionally prevented communication), the NetIQccm service writes the data to the local managed client repository. When connectivity is reestablished, the NetIQccm service uploads any data stored locally to the management server. Monitoring in a UNIX environment If you are monitoring UNIX servers, the AppManager agent is a NetIQ UNIX agent. UNIX agents send a periodic heartbeat message to the management server (NetIQms) to indicate the agent is operating properly and to get any new or updated job information. When the UNIX agent contacts the management server, the management server determines whether any of the Knowledge Script jobs for the managed client have been added or updated. If job properties have changed or new jobs have been added since the last heartbeat interval, the management server delivers the revised job information to the UNIX agent. If there s no change to the Knowledge Script job the managed client is running, the management Chapter 1 About AppManager 21

24 server simply acknowledges the heartbeat, then waits for the next heartbeat. The basic flow is illustrated in the following diagram: Heartbeat Data / events Primary Management Server UNIX Agent Have jobs been updated? Yes Knowledge Script jobs to collect data and events Once a job is received from the management server, the UNIX agent runs the job to access log files, system tables, or other data providers and retrieves the information requested. Each time the Knowledge Script job runs, it determines whether an event has occurred or data needs to be inserted into the repository. If an event condition is detected or a data point collected, the UNIX agent communicates with the management server to upload the information to the repository. If the UNIX agent service can t communicate with the management server for any reason (for example, because the network connection is down), the agent writes the data to the db directory on the UNIX server. When connectivity is reestablished, the UNIX agent uploads any data stored locally to the management server. Events and data returned by the UNIX agent are inserted by the management server into the standard AppManager workflow, so that events are displayed in the TreeView and data is stored in the 22 Installation Guide

25 AppManager repository in the same way events and data are handled for Windows computers. AppManager Workflow UNIX environment Operator Console Repository Management Server Working with both Windows and UNIX computers Although there are slight differences in communication for Windows-based agents and UNIX-based agents, the work flow through AppManager is the same as for any managed computer. From the Operator Console, you can work with managed UNIX computers in exactly the same way you work with Windows computers to start jobs, modify script properties, respond to events, and run charts and reports. Chapter 1 About AppManager 23

26 The following figure illustrates the basic relationship between AppManager components and the UNIX environment. Windows NT/ Windows 2000 managed computers Management Server AppManager Windows Agents Operator Console Repository AppManager UNIX Agent UNIX environment In an environment with both Windows computers and UNIX computers, one management server can talk to multiple UNIX agents or to a combination of Windows and UNIX agents. You can also install multiple management servers in your environment to distribute processing and to provide failover support for both Windows and UNIX computers. For more information about configuring a management site to use multiple management servers, see the Administrator Guide for AppManager. 24 Installation Guide

27 Understanding reporting in AppManager Most AppManager reports rely on the information collected by Knowledge Script jobs and stored in the AppManager repository. You configure the scope and content of reports using Report Scripts in the same way you create Knowledge Script jobs. To create the reports, however, you need to establish at least one report-enabled agent in your environment. You have the option to do this when you install the AppManager agent on computers in your environment. After you install and discover the report agent on at least one computer, you can use the Operator Console to run Report Scripts, which in turn generate reports and post the report output to a selected folder. In addition to the reports that use information in the AppManager repository, you can also install the Analysis Center in your environment to handle more complex reporting needs. The Analysis Center extends AppManager s reporting capabilities using Online Analytical Processing (OLAP) to provide more sophisticated data access and additional specialized report scripts. For more complete information about AppManager reporting and the Analysis Center, see the Reporting Guide for AppManager and the Analysis Center User Guide. Chapter 1 About AppManager 25

28 What is the impact on planning and configuration? Because AppManager uses a multi-tiered architecture, there are several characteristics of your environment to consider before you begin actively planning your implementation. For example, it s important to understand the communication between AppManager components because you need to plan network connectivity and bandwidth usage, the system resources you will need, where best to install different components, and how best to configure each component to suit your organization s requirements. In addition to understanding how AppManager works, it is essential that you evaluate your current environment and the scope of your monitoring requirements. This is especially true for larger scale deployments which may require additional research to get a complete picture of your current configuration. Although your initial estimates may need to be refined, it s important for you to have a basic management strategy and a thorough knowledge of your environment to ensure a successful deployment. For guidelines to planning the deployment, see Chapter 2, Planning the installation. 26 Installation Guide

29 Chapter 2 Planning the installation One of the first steps in a successful deployment of AppManager is developing a project plan that you can use as a roadmap to guide you during implementation. How much planning is required? The amount of planning you need to do depends on your enterprise and the make-up of your organization. For example: Installing for testing and evaluation purposes in a stand-alone configuration with all AppManager components on a single computer simply requires a quick check of whether you have the resources required on the selected computer. A pilot or small scale deployment may require some moderate planning to get access to the computers where you want to install components and check account and password information. A large scale or widely distributed deployment often requires more thorough planning to determine where to install which components and how best to configure the installation for maximum efficiency. A formal project plan is not typically required for smaller scale organizations or if you are monitoring a small number of servers in a local area network, but most larger deployments with complex management needs benefit from putting a plan in place. 27

30 If you are installing all components on a single computer for testing and evaluation, see the Sample installation steps in the standalone.chm file located in appmanager/documentation. This file provides a quick reference to the installation steps you need to follow. No additional planning should be necessary. If you are installing on multiple computers, review the information in this chapter for an overview of the additional planning steps that will help ensure a smooth installation. If you are installing on multiple computers and are planning a large scale, widely distributed deployment, you should review all of the information in this chapter and see the Administrator Guide for AppManager for information about managing and maintaining an AppManager site. You may also want to review Chapter 11, Staging the deployment, for strategies and suggestions in rolling out a large scale implementation. Assembling a project team In larger organizations, where the AppManager installation is likely to involve cross-functional or departmental groups, you may need to assemble a project team and identify the key tasks and responsibilities of each member. The size and technical expertise of the team should reflect the size and management requirements of the deployment. For example, if you are monitoring Exchange Servers, your team should include an Exchange Administrator or individuals with similar experience; if you are monitoring SQL Server, the team should include individuals with database administration experience. All team members should have fairly comprehensive knowledge of the Windows operating system and administration and the network configuration of the organization. If you are also monitoring UNIX, the team should have at least one UNIX administrator. 28 Installation Guide

31 The following table provides guidelines for the information team members should possess: Area of expertise Information or access required Windows Domain structure and trust relationships. Administrator passwords for all computers where AppManager components are to be installed. Ability to create and modify user accounts. Network Network bandwidth and topology. Latency and the configuration of switches and routers. Any DNS, WINS, or DHCP setup in use. SQL Server System administrator (sa) privileges for the AppManager repository server and any managed SQL Server computers, if applicable. Knowledge of SQL Server login IDs and users with permission to access system tables. Experience with SQL Server security modes. Ability to evaluate the hardware configuration for the computer that will serve as the AppManager repository server. Knowledge of SQL Server scheduled tasks. Understanding of ongoing database maintenance, such as backup / restore and consistency checking. Applications Varies depending on the applications monitored. For example: Monitoring hardware may require knowledge of SNMP community names in use. Monitoring SQL Server may require knowledge of each server s corresponding sa password or of login accounts with special privileges. Monitoring Exchange requires knowledge of mailboxes and profiles, granting view access, and turning on tracking logs. Monitoring Microsoft SMS, and Message Queue Server requires knowledge of each server s corresponding sa password. Monitoring Oracle requires knowledge of database and instance names, access to system-level (V$ tables), and the ability to create and modify users. Chapter 2 Planning the installation 29

32 Defining project phases Typically, a project plan describes the following phases used to stage the deployment. A staged deployment ensures the greatest success with the least impact on the production environment. Planning and design phase: In this phase, the project team collects all the necessary information about the environment, analyzes the data, reviews implementation options, identifies organization objectives for what needs to be monitored, and documents decisions. Testing and evaluation phase: In this phase, the project team creates a testing laboratory that resembles (on a smaller scale) the overall environment to be monitored, installs AppManager components on one or more computers, and runs jobs identified in the design phase on the computers in the testing lab. Pilot deployment phase: In this phase, the project team moves the implementation out of the testing lab to a pilot (or larger) group of servers, and evaluates deployment decisions to see if changes need to be made before a full scale deployment. This stage is important because it provides a realistic picture of how AppManager functions in the live environment and gives the team a chance to fine-tune configuration decisions. Expanded or full-production deployment phase: In this phase, AppManager is rolled out to the larger environment. In addition, most organizations begin to refine their management and notification policies and tailor AppManager to suit their environment. Post-deployment phase: In this phase, organizations focus on customizing, extending, and maintaining the AppManager environment. 30 Installation Guide

33 Establishing a time line Because most deployments proceed in phases, your project plan should include a time line for implementation. Depending on the detail in your project plan, your time line might address the period for individual tasks or for completing a stage of the deployment. In most cases, it is easier to establish the schedule for completing each phase than addressing individual tasks; however, each member of the project team should review the tasks to be completed to set a realistic schedule. The following table provides a quick summary of what to expect and some of the factors that may impact the time needed to complete each phase. Project phase Time Factors that may increase time needed Planning and design 3 to 5 days Delays in collecting the necessary information. Availability of key personnel or difficulties in the approval process. Difficulty identifying who needs to be notified of events and how notification should be handled. Difficulty producing required documentation (for example, the time it takes to document the project plan or the scope of the project). Testing and evaluation 5 days Access to a testing laboratory. Permission to create user or database accounts. Training for team members. Changes to management strategy (for example, jobs and event handling). Chapter 2 Planning the installation 31

34 Project phase Time Factors that may increase time needed Pilot deployment 1 to 4 weeks Full deployment 1 to 4 weeks Access to the pilot group of servers. Problems with domain and trust relationships. Problems with network name resolution. Refinement of management strategy. AppManager configuration issues. For example, if an organization has grown dramatically or in unexpected ways, the project team may need to reevaluate decisions such as a centralized management site versus multiple decentralized sites. Physical location of servers. Department policies and procedures. Problems with domain and trust relationships. Permission to create user or database accounts. Bandwidth or latency issues to be resolved. AppManager configuration issues. For example, if an organization has grown dramatically or in unexpected ways, the project team may need to reevaluate decisions such as a centralized management site versus multiple decentralized sites. Post-deployment ongoing Development expertise or interest. Database management expertise. The length of time required to complete each phase will vary depending on a number of factors, such as the number of servers and applications to be monitored, the physical location of computers, and internal policies and procedures. For example, if you are deploying AppManager in several departments that are located in different countries, each location may need to go through its own design and testing phase or may need the production deployment scheduled with local requirements in mind. 32 Installation Guide

35 Refining your deployment plan Although this time line illustrates a basic deployment schedule, keep in mind that you should continually review your assumptions and expectations throughout the implementation, especially if you are deploying AppManager in a large enterprise. Most likely, you will need to refine your management strategy over several weeks as more servers are monitored and events and data are generated. You may also need to plan for custom Knowledge Script development and testing, which may impact the schedule for implementation. We recommend you carefully evaluate the test installation and the pilot program to determine whether any custom development needs to be done before moving to a full deployment. Evaluating the environment to be monitored An essential part of the planning process is understanding the characteristics of your environment and the network you are going to monitor. Before you can decide where to install or how to configure AppManager components, you need to be able to answer several questions about the physical and logical make-up of your network. To get started, you need to think about the computers you want to monitor and how you plan to use AppManager. The questions you need to answer include: Number of Windows and UNIX servers to be monitored? Number and type of application servers (such as the number of Exchange, Domino, or Oracle RDBMS servers) to be monitored? Number of hardware types to be monitored? Note that a single computer may fall into more than one category. For example, you may have a Compaq server with Windows NT and Exchange Server installed on it. As part of your planning you need to decide, for example, if you will monitor Windows NT, CIM, and Exchange on that computer or just NT because this decision may Chapter 2 Planning the installation 33

36 affect how you size the repository or how you decide to distribute AppManager components. In addition to the computers you are going to monitor, you need to decide and document how you intend to use AppManager. The questions you need to answer include: Who needs to view events? Who will respond to events? How are users going to view events and other information? What type of consoles are needed? For example, will some users require web access? dial in to a terminal server? connect through RAS? Should specialized consoles, such as the Security Manager or Chart Console be placed on separate computers that are only accessed by a few users? What are your main monitoring objectives? Is your organization only concerned with event monitoring? with a small amount of data collecting? with collecting a great deal of data for reporting and graphing? How does the organization intend to handle event notification? Should events trigger a call to a paging system, send an message, forward an SNMP trap to an external system, or perform some other action? Do you need to monitor clustered applications or resources? How is the cluster configured (for example as an active-passive or active-active cluster), and what kind of monitoring do you need to do? As with the number of servers and applications to be monitored, this information will affect how you size the repository and how you decide to distribute AppManager components. Your monitoring and event handling goals may also impact the configuration you need to do after you install AppManager. 34 Installation Guide

37 Reviewing your network configuration As you evaluate the computers you intend to monitor, you also need to be aware of where those computers are and how they are configured. This is a key part of the data collection you do in the planning phase. The questions you need to answer include: What is the physical location of the servers to be monitored? What are the bandwidth and latency characteristics of your network? Where are the broad band and narrow band connections and where are the routers and gateways through which network communication flows? What is your network load at different points in the day? What are the peak and off-peak times? How are server domains and trusts currently defined? (Although you can monitor across trusted and untrusted domains, you should collect information about domains and trusts for installation purposes.) Which accounts have Administrator privileges in which domains? Information about your network topology and its limitations is likely to affect how you distribute AppManager components. For example, you may decide, based on this information, to create two regional management sites instead of one centralized site for network efficiency. This information is also useful for determining how best to group computers for remote agent installation. To help you record network information in preparation for installation, you may find it useful to create a chart that records key Chapter 2 Planning the installation 35

38 information for each computer, such as what you plan to monitor, domain and trust information, and physical location. For example: Computer name What to monitor Domain and trusts Location Disk Porche Windows NT Exchange Server WEST1 domain Trusted by: Enterprise00 Trusts: CAL1 CAL2 WASH1 Portland, OR 2 GB Gremlin Windows NT Domino WEST1 domain Trusted by: Enterprise00 San Jose, CA 1.2 GB Additional columns for disk space or configuration notes may be added (for example, when a server is part of a cluster). You can prepare a similar worksheet for the computers on which you are planning to install other AppManager components, such as the repository and management server. Tip You may also want to add columns for other important information unrelated to configuration but useful for installation or administrative purposes. For example, you may want to add an Owner column to track the person or group who needs to provide you with permission to install, or a Business-critical column to highlight the servers that you can only access during non-production hours. Creating a chart like this can help you see potential troublespots in domain and trust relationships or if you need to collect additional information. For example, if you are monitoring an Exchange Server, you may need to create a Windows user account for the AppManager agent to use. 36 Installation Guide

39 Planning network connection requirements Reviewing your network configuration should help you determine where to install AppManager components. However, you should also keep in mind that specific types of network connectivity must exist between the computers where specific AppManager components are installed. In deciding where you are going to install components, check the following network connections (the following checks represent the typical network connections; if you have configured your network differently for example with ODBC running over RPC your connectivity points may be different): AppManager Operator Console computer and the repository server require TCP/IP and ODBC connectivity. AppManager repository and the management server, if installed on separate servers, require TCP/IP and ODBC connectivity. AppManager management server and each managed client on which AppManager agent has been installed require TCP/IP and RPC connectivity. In addition, the AppManager management server needs to be able resolve the name or IP address for each managed client and each managed client needs to be able to resolve the name/ip address of the management server. AppManager repository and the Web management server, if installed on separate servers, require TCP/IP and ODBC connectivity. If you want to enable reporting on a managed client, there must be ODBC connectivity between the managed client and the repository server. AppManager Web management server and the computer with a web browser (that acts as the Operator Web Console) require TCP/IP connectivity. Chapter 2 Planning the installation 37

40 AppManager components expect to communicate with each other through specific ports. You should check for any port restrictions or firewall protections. Typically, AppManager uses the following ports for communication between components. Communication between these components Uses this port Protocol Operator Console and repository 1433 (TCP/IP) 135 (Named Pipes) SQL ODBC Management server and repository 1433 SQL ODBC Web management server and repository 1433 SQL ODBC Web Operator Console and Web management server 80 HTTP NetIQms service to NetIQmc service 9999 TCP/IP NetIQmc/NetIQccm to NetIQms 9998 TCP/IP NetIQ UNIX agent to NetIQms 9001 TCP/IP AMAdmin_AgentInstall (NQEXEC program) to remote directories RPC - XCopy (for remote installation scripts, such as AgentInstall) 9979 TCP/IP 135 RPC Note You can change the listening ports that the NetIQ AppManager Management Service (NetIQms) and NetIQ AppManager Client Resource Monitor (NetIQmc) use. However, you should be particularly careful if you intend to change the port settings. Setting ports incorrectly can disable communication between components. Consult your security administrator before installing if you intend to change communication ports. 38 Installation Guide

41 Planning management sites As described in What are the AppManager components? on page 15, AppManager consists of required and optional components that can be installed together on a single computer or installed separately, in virtually any combination, on multiple computers. Each component has specific system requirements, so in the planning process you should try to determine where you want to install which components. It is especially important to consider the number and placement of management sites. A management site always consists of one AppManager repository and at least one AppManager management server, regardless of where these components are installed. A management site may have multiple management servers to distribute processing and communication for managed clients, but each management site has exactly one repository and each management server has only one repository it communicates with. The one management server-to-one repository or many management servers-to-one repository association is the primary element that defines a management site. Each managed client needs at least one authorized management server for installing and discovering the AppManager agent. In small to mid-size deployments, a single management server may be sufficient. However, in many organizations it is beneficial to install multiple management servers. If you install multiple management servers within a given management site (that is, for a single repository), you can explicitly designate a primary and secondary management server for each managed client to distribute processing, provide failover support, and control which management servers communicate with which agents. The managed clients always communicate with only one management server (and, therefore, one repository) at any time within a management site, but they can be monitored independently by other management sites if your organization permits it. Chapter 2 Planning the installation 39

42 Note Designating the primary and secondary management servers is done after installation using the Knowledge Scripts AMAdmin_SetPrimaryMS and AMAdminUNIX_SetPrimaryMS. You should, however, do some planning before installation to determine how best to set up communication for your management site. In planning where to install components and how many management servers and management sites you ll need, there are several issues to consider: When you set AppManager repository preferences for event and data handling, these preferences serve as the defaults for the site (they can be overridden on a job-by-job basis). If you are monitoring a large number of managed clients and you have the capability to stagger or schedule communication between managed clients and the management server, you may want to use a single centralized site. If you have a widely distributed environment or have latency or bandwidth restrictions, you may want to set up regional or divisional management sites for increased network efficiency. If your organization s internal policies require more localized operational control over parts of the network and who has access, you may want to set up separate management sites to provide this control. If you have a large number of jobs and expect to generate a large number of events or collect a great deal of data, you may want to have multiple management sites to balance the load or improve performance. Smaller-scale management sites may offer you increased efficiency and performance, but multiple sites will also increase the complexity of handling system and site administration. If you are monitoring a combination of Windows computers and UNIX computers, you may want to devote separate management servers or separate management sites for the Windows agents and the UNIX agents. Managing the platforms separately through 40 Installation Guide

43 dedicated management servers and/or management sites may give you more flexibility in defining policies and tuning performance. In general, if your organization has a large, widely distributed network, you may want to have different management sites focused on particular groups. In a smaller organization, you may prefer to centralize management in one site. Deciding where to install the management server and repository As part of planning your management site or sites, you need to determine whether to install the AppManager repository and management server on the same computer or on separate computers. In deciding where to locate the management server and repository, you should consider several factors, such as: Who is responsible for the servers you are going to be managing in a given site? How many groups need to manage the servers and what level of authority or autonomy is needed for each group? What is the geographical distribution of the servers and management groups? What is the network bandwidth, latency, and normal load between the computer you want to use as the management server and the servers to be managed? What is the network bandwidth, latency, and normal load between the computer you want to use as the management server and the associated repository server? Although managed clients need to communicate with the management server to send events and data, the most concentrated network traffic that the management server generates is between the management server and the repository database. In sites supporting 200 or fewer servers, NetIQ recommends locating the repository and management server on the same computer for maximum efficiency and easier maintenance. For sites monitoring Chapter 2 Planning the installation 41

44 more than 200 servers, NetIQ recommends installing the repository and management server on separate computers if the computers are on a 100 Mbps or faster backbone on the same IP subnet. In most cases, even organizations with 200 to 250 servers can use a single computer for both the repository and management server (the preferred configuration), unless the computer is overloaded or experiencing performance problems. If you monitor more than 250 servers, you may first want to consider creating multiple management sites with the repository and server installed on the same computer in each site. This model suits many organizations because it mirrors departmental or geographical divisions already in place and allows for distributed management by groups that may already be functionally separate. In other cases, however, it may make sense to install the repository and management server on separate computers even if you are monitoring fewer servers. For example, you may want to install the repository on a computer that is managed through your database administration team to take advantage of the database expertise but choose to install the management server on a computer that is maintained by IT personnel. In planning where to install components it is just as important to consider your organization s structure and policies as any physical system attributes or network requirements. Planning system resources for AppManager Each AppManager component and managed object has specific system requirements, such as RAM, disk space, or supported software versions. The minimum requirements for AppManager components are described in Chapter 3, Performing a pre-install check, in the section Review system requirements on page 57. These minimum system requirements are verified when you run the pre-installation 42 Installation Guide

45 check on any computer where you want to install AppManager components. In planning the system resources required to suit your specific environment and monitoring needs, you should keep in mind the following guidelines. On a computer where this component is installed System resource requirements can be impacted by Repository Number of computers, jobs, events, and data streams in your environment. Network bandwidth and latency and where other components are installed. Historical reporting requirements. Management server Number of computers you are monitoring. Number and frequency of events in your environment. Number and frequency of data points collected. Network bandwidth and latency. Operator Console The preferences and options you have set (for example, the Views, panes, and tabs you decide to display). Number of computers and details displayed in the TreeView. Number of jobs, events, data streams, and active, real-time graphs you elect to display. Agent Number of jobs running on the computer. Number of server applications you are monitoring. Interval at which the jobs run. Types of jobs you run (some jobs perform multiple or more complex tasks than others, and so use more resources). Note For peak AppManager performance, you may want to use a dedicated computer for the Operator Console and separate computers for the management server and repository. In addition, you can Chapter 2 Planning the installation 43

46 optimize performance by reducing the number of views you display, using the split TreeView option, and filtering the information included in the List pane. Sizing the AppManager repository There are many factors that influence the configuration of the database, but two of the most important factors are the number of events you expect and the number of data points you intend to collect and save for historical reporting or trend analysis. Because this information is often difficult to estimate before you install and is subject to change over time as you expand and refine your deployment strategy, NetIQ recommends the following as a starting point: 1 Count the number of servers you plan to monitor and multiply that number by 1 MB to account for the events and data each will generate. 2 Multiply the result by the number of days you intend to keep data in the repository. For example, assume you have 180 servers that you intend to monitor and that you want to retain data in the repository for 30 days to generate monthly reports. From this, you can estimate that your database is likely to need 5.4 GB for full deployment and data collection. 3 Set the initial database size during installation to be 2 GB, the initial log device to 600 MB, and keep the data and the log on separate devices. Sizing the initial database along these guidelines is a good starting point in most environments and is roughly a third of what you have estimated you will need for the full deployment. Setting the initial size to about a third of what you estimate you ll need prevents you from reserving space you won t use during the early stages of deployment, when it is unlikely that you ll run a full set of Knowledge Script jobs or collect all of the data in which you are interested. Instead, it s likely you will increase the number of servers and the number of jobs you run over time. In addition, it is easier for you to perform maintenance operations such as backup 44 Installation Guide

47 and restore if you create smaller data devices and plan for growth rather than sizing the data device at the onset to handle your eventual database requirements. Note SQL Server 7.0 and SQL Server 2000 can dynamically increase the size of database files and memory, as needed, depending on your SQL Server configuration options. If you install the management server and the repository on the same computer, however, you may want to configure a fixed amount of memory for SQL Server to minimize resource contention between the management server and the repository. Adjusting the size of other databases As you increase the data you store, you may also need to increase the size of the temp database to handle queries that require temporary space. By default, this database is usually 10 MB. The more data you store and access and the more you plan to use AppManager s reporting capabilities, the more space you should set aside for the temp database. The size of the other databases, for example, the master database, can typically remain the same. Planning security Although not required, it can be useful to plan security before installing AppManager. In reviewing your security requirements, you need to: Decide on the SQL Server security mode to use for the repository and how you want to set up SQL Server users, groups, and login accounts for the users who will access AppManager. For more information, see your Microsoft SQL Server documentation and Granting users access to AppManager on page 178. Determine the AppManager user roles you need and the AppManager-related rights associated with each role. In general, it Chapter 2 Planning the installation 45

48 is recommended that you stringently restrict user rights initially and expand rights over time as you refine AppManager roles. For more information, see Granting users access to AppManager on page 178. Determine the level of security needed between the AppManager management server and agents on the managed computers. By default, you can restrict communication by defining a list of authorized management servers for a managed computer to communicate with or allow unsecured communication. For maximum security in your environment, all communication between managed client computers and the management server can be encrypted. Note For encrypted communication (maximum security) between the management server and managed clients, you must use the rpckey.exe program to generate a key file before installing the management server. If you want to enforce this type of security, thoroughly review the information in the Administrator Guide before installing. Determine any security-related information needed to run Knowledge Scripts (for example, community names, user account or password information). Typically, you need to enter this information when you install the managed object for an application that requires it. For example, AppManager for Microsoft Exchange Server requires a user account, profile, and mailbox alias name. If you choose to install the AppManager for Microsoft Exchange Server managed object, you are asked to provide this information. For more information, see Using the Security Manager to update information on page Installation Guide

49 Planning your management strategy Planning your deployment has one additional key element: deciding on your core management tasks. Most likely you will refine your management policies throughout the deployment cycle, so any strategy you define in the planning phase should be considered workin-progress, but planning ahead can help you decide which components you need to install on which computers. Identifying management goals Different organizations have different goals and those goals influence which Knowledge Scripts they run, their event notification policies, and their data collection requirements. As a starting point, you should identify your primary and secondary objectives. For example, are you most concerned with: Immediate event notification when something goes wrong. Proactive management that allows you to see and respond to potential problems before something goes wrong. Automating event notification, acknowledgment, and response. Ongoing analysis and capacity planning. Service level reporting. As you consider what you want to achieve through monitoring your environment, you should also prioritize your goals in realistic ways given the size and experience of your staff, the physical location of your servers and administrators, and the business needs of your organization. Having this high-level view of what you want to accomplish will help you decide what you need to implement when. Preparing to monitor specific applications As part of your planning process, you should already have identified the applications you want to monitor and the characteristics of your environments. For most applications, no additional preparation is Chapter 2 Planning the installation 47

50 needed. Some applications, however, do have special requirements or configuration issues. For example, monitoring Exchange requires a user account, profile, and mailbox and monitoring SAP R/3 requires you to establish a computer to serve as a proxy for SAP R/3 systems. Because these requirements are strictly application-specific and not part of the typical installation process, detailed information is not provided in this guide. Instead, application-specific configuration notes are provided separately in the appmanager\documentation\supplements folder. Before you install, you should check this folder for any application-specific details you may need to consider or steps you may need to perform before or after you install your AppManager agents, such as creating new accounts, modifying user rights, or locating a computer for proxy management. Selecting Knowledge Scripts and setting thresholds A good way to begin developing your management strategy is to create a spreadsheet that describes the Knowledge Scripts, intervals, and thresholds you intend to start with. You can find recommendations for which Knowledge Scripts to run from NetIQ Support if you are a registered AppManager customer. Planning event handling and response In most organizations, the event handling strategy evolves over time and is closely tied to which Knowledge Scripts you run. However, there are a few issues that you may want to consider during the planning phase. For example: Is the group geared primarily to receiving and responding to events? Is the manpower available to respond to a large number of events or should administrators only respond to events of a certain severity? 48 Installation Guide

51 What constitutes a severe event and how visible should events of different severity levels be? How should console programs be distributed to let the right people see events that have been raised? Most event handling is configured after installation on a site or even job-by-job basis. It is useful, however, to consider how your organization will respond to events. For example, you may need to install a MAPI client to enable events to send an message or may need to install an AppManager Connector to send events to an external console, such as Tivoli Enterprise Console or Cabletron SPECTRUM. (For information about AppManager Connectors and integration with other products and applications, see the NetIQ Web site.) Planning data handling and reporting Because both event detection and data collection impact the sizing of the repository and the placement of AppManager components, it s useful to consider your goals for these operations from the beginning. For the purposes of installation, it is useful to consider: How and when data gets transferred between components. Who needs access to graphs and reports. How much historical data you need access to. Where your reporting needs are concentrated. Which computers to use for reporting and how many of these report agents you will need. Any time you install the AppManager agent, you have the option of enabling reporting from that computer. You should, however, make explicit plans for the number and location of report agents to install. After installing an agent with reporting enabled, you must run the Discovery_ReportAgent Knowledge Script before you can run any reports (this discovery is not automatic). Therefore, your deployment plan should indicate the computers to be used for reporting. Chapter 2 Planning the installation 49

52 Note Depending on the amount of information in each report and the number and frequency of reports you run, a report-enbabled agent can consume significant system resources. It is recommended that you use a separate report-enbabled agent for each repository in your environment, and install each report-enbabled agent on a dedicated report server, and not on a computer where you have installed any other core AppManager components. This configuration optimizes performance of the report-enbabled agent by limiting the number of queries and render operations it s responsible for, and by keeping the agent from competing with other programs for system resources. Planning for customization Although not required, many organizations find it useful to identify any custom Knowledge Script requirements during the planning phase. At a minimum, you should consider whether you intend to do custom Knowledge Script development to determine whether or not to install Developer s Console Utilities and where these programs should be installed. Planning a staged deployment Most organizations find it useful to take a staged approach to deploying the AppManager components and core Knowledge Script jobs. In a staged approach, you would typically install a relatively small number of agents and a basic set of monitoring jobs, fine tune your event thresholds, data collection, and event handling policies, then expand the scope and complexity of your monitoring environment over time. If you are new to AppManager, you may want to review Chapter 11, Staging the deployment, for guidelines and suggestions in planning a staged deployment. The chapter includes recommended practices for installing core AppManager components, selecting Knowledge Scripts to run, setting and adjusting thresholds, and configuring your AppManager environment to best suit your needs. 50 Installation Guide

53 If you are an experienced AppManager user but are planning a large scale deployment, you may want to review Chapter 11, Staging the deployment, for recommendations and strategies to help ensure a successful implementation. Chapter 2 Planning the installation 51

54 Documenting your decisions and policies An important part of a highly successful deployment is complete and accurate documentation. Throughout the deployment cycle it is critical that you document your plans, testing, results, and policy decisions. Ideally, each stage of the project should include a document that records the tasks completed and the strategies implemented. For example, you should articulate specific policies for who should respond to which events, how individuals should receive notification, who is responsible for closing or deleting events, and how or when events should be closed or deleted. Documenting your decisions and communicating policies is an essential part of the implementation whether it is a matter of recording the standard threshold values you ve settled on or identifying who should be paged when problems of a certain severity are found.

55 Chapter 3 Performing a pre-install check This chapter describes the steps you can take to ensure a smooth and successful installation that avoids common problems. It includes instructions for steps that are taken outside of AppManager and instructions for running AppManager s pre-installation check to verify system requirements. The following topics are covered: Select your configuration Review system requirements Check account information Test network connections Check database communication Generate an encrypted key file Run the pre-installation check Review the pre-installation report Avoiding common installation problems Select your configuration If you have developed a deployment plan, you should already have a road map for where you are going to install which AppManager components. Knowing where you plan to install which components helps ensure you have all the information you need to complete the installation easily. 53

56 For convenience, the most common installation scenarios are described in the following table. To prepare for installation, note the scenario that most closely resembles what you want to do and follow the recommended steps. Installation scenario Typical configuration What you need to do Testing, evaluation, training Stand-alone with all components installed on a single computer Run pre-installation check. Install AppManager and select all components and the default options in most cases. Standard deployment Install AppManager repository and management server on the same computer Install other components, as needed Run pre-installation check on the repository and management server computer. Install AppManager repository and management server with the Setup program. Run the pre-installation check on the Operator Console computer, then install the Operator Console. Install other console programs, as needed. Run the pre-installation check or AMAdmin_AgentPreInstall on computers to be monitored. Run Setup or AMAdmin_AgentInstall to install the AppManager agent services and managed objects on a pilot (or larger) group of computers to be monitored. 54 Installation Guide

57 Installation scenario Centralized enterprise deployment Typical configuration What you need to do Install AppManager repository and management server on different computers. Install additional management servers, as needed. Install other components as needed Develop a deployment plan and determine where to install AppManager components and whether multiple management servers will increase efficiency. Run pre-installation check on the repository server computer. Install AppManager repository with the Setup program. Run pre-installation check on the management server computer, then install the first management server with the Setup program. Run the pre-installation check on the Operator Console computer, then install the Operator Console. Run the pre-installation check or AMAdmin_AgentPreInstall on computers to be monitored. Run Setup or AMAdmin_AgentInstall to install the AppManager agent services and managed objects on a pilot (or larger) group of computers to be monitored. Install additional management servers, as needed. Install other console programs, as needed. Run AMAdmin_AgentInstall to install the AppManager agent services and managed objects on computers to be monitored. Chapter 3 Performing a pre-install check 55

58 Installation scenario Typical configuration What you need to do Widely distributed enterprise deployment Define multiple management sites Install the AppManager repository and management server on one computer for eachsiteor separately on different computers* at each site. Install other components, as needed. Develop a deployment plan and determine where to install AppManager components and how to organize management sites. Run pre-installation check on the repository/management server computer for the first site. Install the AppManager repository and management server with the Setup program. Run the pre-installation check on the Operator Console computer, then install the Operator Console. Run the pre-installation check or AMAdmin_AgentPreInstall on computers to be monitored. Run Setup or AMAdmin_AgentInstall to install the AppManager agent services and managed objects on computers to be monitored in the first site. Install additional repositories and management servers, as needed. Install other console programs, as needed. Run AMAdmin_AgentInstall to install the AppManager agent services and managed objects on computers to be monitored. * If needed, you can install the repository and management server components on different computers. You should use this configuration if you expect a heavy load for data and events. Note This table only summarizes a few typical configurations, you may want to employ. AppManager is very flexible in how you can deploy components. For a review of what to consider in planning your configuration, see Planning management sites on page 39 and Deciding where to install the management server and repository on page Installation Guide

59 Review system requirements Before running the AppManager setup program, you should review the AppManager system requirements and verify the computers on which you are about to install AppManager components meet all of the appropriate system requirements. The AppManager setup program includes a pre-installation check that verifies whether the computer on which you are about to install AppManager components passes or fails the system requirements. Although the pre-installation check program verifies most system requirements, some requirements, such as account permissions or network connectivity between computers, must be done manually. Note Most installation problems stem from insufficient RAM or disk space for the combination of components selected, insufficient or inaccurate account information, or a lack of network connectivity. Besides running the pre-installation check program, it s recommended that you take the time to thoroughly review this section and Appendix D, Pre-installation requirements. Requirements for each AppManager component In deciding which components to install and where to install them, you need to evaluate your system resources and environment configuration. Note For system requirements for NetIQ UNIX agents, see the ReadMe.txt file on the NetIQ UNIX Components CD-ROM. The following table lists the minimum requirements for each AppManager component, if installed separately. Component Requirement Minimum configuration Repository CPU Intel Pentium III (733+ MHz) 1 RAM 512 MB or more Available disk space 200 MB or more Chapter 3 Performing a pre-install check 57

60 Component Requirement Minimum configuration Repository (continued) OS type Windows NT Server, Windows 2000 Server, or Windows Server OS version Windows NT 4.0 (SP6a or later), Windows 2000 Server (SP2 or later), or Windows Server 2003 MDAC 2.5 SP2 or later for SQL Server 7.0, 2.6 or 2.7 for SQL Server 2000 Database Database driver SQL Server 7.0 SP3 or later SQL Server 2000 SP2 or later ODBC SQL Server driver Management server CPU Intel Pentium III (733+ MHz) 1 RAM 256 MB or more Available disk space 70 MB OS type Windows NT Server, Windows 2000 Server, or Windows Server OS version MDAC Database driver Windows NT 4.0 (SP6a or later), Windows 2000 Server (SP2 or later), or Windows Server SP2 or later ODBC SQL Server driver (included in MDAC) Console CPU Intel Pentium III (733+ MHz) 1 RAM 256 MB or more Available disk space 134 MB OS type OS version Windows NT Server or Workstation, Windows 2000 Server, Windows XP Professional, or Windows Server Windows NT 4.0 (SP6a or later), Windows 2000 Server (SP2), Windows XP Professional, or Windows Server 2003 MDAC 2.5 SP2 or Installation Guide

61 Component Requirement Minimum configuration Console (continued) Database driver ODBC SQL Server driver (included in MDAC) Web browser Internet Explorer 5.5 SP2 (or later) Windows Agent CPU Intel Pentium (100+ MHz) 1 RAM 32 MB or more Available disk space 55 MB OS type OS version MDAC Database driver Windows NT Server or Workstation, Windows 2000 Server, Windows XP Professional, or Windows Server Windows NT 4.0 (SP4 or later), Windows 2000, Windows XP, or Windows Server SP2 or later (2.5 or 2.6 for the report-enabled agent) Note If you use MDAC 2.6 or later, you may need to install the JetPack driver separately. This driver is required for the local repository on the managed client, but is not included in MDAC 2.6 or later. ODBC Access driver ODBC SQL Server driver if monitoring SQL Server on the computer UNIX Agent OS type Sun Solaris, Red Hat Linux, HP-UX, IBM AIX operating environments OS version See the ReadMe on the NetIQ UNIX Components CD-ROM for complete information about system requirements and patches. Available disk space Approximately 100MB on the target directory and 10MB of temporary space (see the ReadMe for details). Chapter 3 Performing a pre-install check 59

62 Component Requirement Minimum configuration Web management server CPU Intel Pentium III (733+ MHz) 1 RAM 256 MB or more Available disk space 24 MB OS type Windows NT 4.0, Windows 2000 Server, or Windows Server OS version MDAC Database driver Internet Windows NT 4.0 (SP6a or later), Windows 2000 Server (SP2 or later), or Windows Server SP2 or later ODBC SQL Server driver (included in MDAC) IIS (4.0 or later for Windows NT or 5.0 or later on Windows 2000), ASP, ADO installed Web browser Internet Explorer 5.5 (SP2 or later) 1 Windows 2000 Server also includes Advanced Server, Professional Server, and DataCenter Server and Windows Server 2003 includes Standard Edition, Enterprise Edition, DataCenter Edition, and Web Edition. 2 The minimum configuration is intended only as a guide. Several factors, such as the number of servers monitored and the view options you select, can influence Operator Console performance and the recommended minimum configuration. Adjusting requirements to suit your environment It s important to keep in mind that these are the minimum requirements for each component. Depending on the characteristics of your environment for example, the number and distribution of servers monitored, the number of jobs you are running, and the number of events or data points you are generating you may need to adjust these requirements to ensure optimal performance. 60 Installation Guide

63 Requirements for multiple components on a single computer Any combination of components can be installed on an Intel-based computer. In most cases, you want to install the management server, repository, and agent together on at least one computer to monitor the Windows operating system and SQL Server on that computer. When you install multiple components on a computer: RAM should be configured for the component that requires the most RAM (not the sum of the RAM requirements). For example, a computer with the management server (256 MB), agent (32 MB), and repository (512 MB) requires a minimum of 512 MB of RAM. The computer must have enough disk space to accommodate all of the components you plan to install. Add up the disk space required for each component and verify that the computer has at least that much disk space. For example, a computer with the management server (70 MB) and the agent with the Windows NT or Windows 2000 managed object (55 MB), and a repository (200 MB), requires approximately 325 MB of available disk space. Any requirements unique to an individual component must be present on the computer. For example, a computer with the AppManager Operator Console, management server, and repository requires the ODBC SQL Server driver; however, if the computer is also a managed client, it must also have an ODBC Access driver. Chapter 3 Performing a pre-install check 61

64 Supported platforms and operating systems For a quick look at the platforms and operating systems that AppManager components support, review the following table. AppManager component AppManager repository AppManager management server AppManager Web management server and Operator Web Console AppManager console programs AppManager agent Supported on OS version Intel Windows NT 4.0 Windows 2000 Windows Server 2003 Intel Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 AppManager agent UNIX Sun Solaris Red Hat Linux HP-UX IBM AIX In most cases, AppManager can monitor current versions of supported systems and applications installed on either Windows NT or Windows For up-to-date information regarding the systems and applications and versions of those products that AppManager currently supports, click the Supported Products link on the NetIQ Support web site. 62 Installation Guide

65 Check account information The AppManager setup program requires access to various administrator privileges and user account information to install AppManager components. Note If you are installing AppManager on a cluster, you should also review Accounts needed to install the repository on a cluster on page 99. The following table lists the accounts Setup requires. To install this component Any AppManager component Repository Management server You need A valid Windows login account with Administrator privileges for the local computer (required) or the Domain (optional) to run Setup. Account access and the password for the SQL Server sa login account. Setup creates a NetIQ SQL Server login account. The default password for the NetIQ SQL Server login is netiq. You can specify a different password, if desired. A service account (sometimes called the run-as account) for the NetIQms service to use. Either: The LocalSystem account. A valid Windows login account. A valid Windows login account is required if you use Windows Authentication (Integrated) security mode for SQL Server. If you don t use Windows Authentication security for SQL Server, the NetIQms service runs under the LocalSystem account by default. You can specify a different Windows login account, if desired. Chapter 3 Performing a pre-install check 63

66 To install this component Agent Agent or managed object remotely using AMAdmin Microsoft Exchange Server or Exchange 2000 Server managed object Microsoft Message Queue Server/Service managed object Microsoft SQL Server managed object You need A service account (sometimes called the run-as account) for the NetIQmc service or the UNIX agent to use. For Windows, the account can be either the LocalSystem account or a valid Windows login account. For UNIX, the account can be a valid UNIX login account. Note In some cases, the agent must use a valid login account. For example, if you enable the report agent, you must provide a valid Windows login account. A Windows login account with domain Administrator privileges. See Running the AgentInstall Knowledge Script on page 152. A service account (sometimes called the run-as account) for the NetIQmc servicetouse.the account must have permission to map drives on the target server. A valid Windows login account with Logonas Service privileges for each domain that contains an Exchange Server to be monitored. (The LocalSystem account can t be used.) Windows account domain. Windows account user. Windows account password. Note For Setup to create an Exchange profile (automatic) and (optional) mailbox, the Windows login account must be an Exchange Administrator with the Permissions Admin role for the Recipients configuration level. Account access and password for the local SQL Server sa login account. Account access and password for the local SQL Server sa login account. Note Depending on the SQL Server version and the security mode you are using, you may be able to install the managed object without the sa account. Setup creates a local NetIQ SQL Server login account for monitoring the local SQL Server. 64 Installation Guide

67 To install this component Microsoft Systems Management Server managed object You need SMS Administrator privileges. Account access and password for the SMS SQL Server sa login account. SAP R/3 managed object A valid Windows login account for the AppManager agent to run as. A valid SAP R/3 login that maps to an AppManager configuration name A valid SQL Server login account. For more information, see the SAP R/3 Configuration Note in the appmanager\documentation\supplements folder. Test network connections AppManager requires communication between specific components as noted in Planning network connection requirements on page 37. Network connectivity must exist between the computers on which each of these components are installed. When preparing to install, you should test the following connection points: AppManager Operator Console and the repository AppManager repository and the management server, if installed on separate servers AppManager management server and each managed client on which the AppManager agent has been installed AppManager repository and the Web management server, if installed on separate servers AppManager Web management server and the computer with a Web browser (that acts as the Operator Web Console) There are no special domain security requirements for network communication between components. To conduct the test: 1 Log on to a computer you want to test. Chapter 3 Performing a pre-install check 65

68 For example, if you re testing the connection between the repository and the management server, log on to the computer where the repository is installed. 2 Start Command Prompt. 3 At the command prompt, type ping <computer> where <computer> is the name of the computer to which you want to test the connection. For example, enter the name of the computer where the management server is installed. If there is network connectivity between the two computers, then you ll see a reply like the one below: F:\Mgmt_Server> ping corp08 pinging corp08.west.com [ ] Reply from If you don t get a reply, contact your network administrator. Check database communication The SQL Server ODBC driver handles communication between the AppManager consoles and the repository, and communication between the repository and the management server. Therefore, an ODBC driver must be installed on the computers where these components are installed: Operator Console, Operator Console MMC Snap-In, Security Manager, and Distributed Event Console AppManager repository AppManager management server In addition, the AppManager agent uses Access ODBC data access technology to enable local repository storage and autonomous operation. 66 Installation Guide

69 Generate an encrypted key file If you want to enforce maximum security in your Windows environment and encrypt all communication between Windows-based managed client computers and the management server, you need to use the rpckey.exe program to generate a key file before installing the management server. The rpckey.exe program creates an encrypted file that, along with a password, enables the management server and managed clients to send and receive encrypted data. You can find the rpckey.exe program in the appmanager\setup folder on the AppManager CD-ROM. To generate a key file for secure communication: 1 On a computer in your network, open a Command Prompt window. 2 Change to the appmanager\setup directory on the AppManager CD-ROM. For example, if the CD drive is the E: drive: cd E:\appmanager\setup 3 Run the rpckey.exe program using the following options: rpckey -generate <filename> -pwd <password> For example: rpckey.exe -generate c:\temp\rpckey.txt -pwd netiq 4 Make note of the key file full path and the password. You will need to specify this information when you install the AppManager management server and agents that require secure communication with each other. Note Each time you run the rpckey.exe program, it generates a new, unique key file. For more information about managing secure communication, see the Administrator Guide. Chapter 3 Performing a pre-install check 67

70 Run the pre-installation check The pre-installation check feature verifies that the computer on which you are about to install AppManager components passes most system requirements. Based on the components you select to check, the program writes a report (in HTML format) that summarizes each component s requirements and indicates whether your system passed or failed. You view this report in a Web browser. Be sure to run the pre-installation check on each computer on which you plan to install any AppManager component. Note Once you ve installed the AppManager repository, management server, console, agent, and optionally the Web management server components in your environment, you can then verify the installation requirements for the AppManager agent on a Windows computer or group of computers by running the AMADMIN_AgentPreInstall Knowledge Script from the AppManager Operator Console or Operator Web Console. For more information about this script, see the online help for the Knowledge Script or the Knowledge Script Reference Guide. If you want to review the system requirements for any AppManager component before you run the pre-installation check, see Appendix D, Pre-installation requirements. 68 Installation Guide

71 Starting the pre-installation check program The pre-installation check is part of the AppManager Setup program. 1 Insert the AppManager CD-ROM into a CD drive. The CD-ROM autorun program starts your default Web browser and opens the Setup page. If your browser is Microsoft Internet Explorer Netscape Navigator Then At the Setup page: Click Begin Setup. When prompted, select the option to open or run the file (not to save it), then click OK. A Command Prompt window opens and the AppManager setup program starts. Note Optionally, you can manually launch the setup program from the CD-ROM by double-clicking appmanager\setup\setup.exe. You can use the Web page to view the Release Notes, access the documentation PDF files, and link to online resources such as the NetIQ Support site. The AppManager setup program can t be run from the Setup page, however. Instead, you need to manually start the setup program from the CD-ROM by double-clicking appmanager\setup\setup.exe. To exit the Setup program at any time, click Cancel or press F3. 2 At the Welcome screen, click Next. Chapter 3 Performing a pre-install check 69

72 3 Click Pre-Installation Check, then click Next. 4 Select the folder where you plan to install AppManager: To Accept the default folder location (D:\Program Files\NetIQ) Change the folder location Do this Click Next. Click Browse. Select the drive and path name of the folder you want. Click OK. Then click Next. 70 Installation Guide

73 5 Select the AppManager components for which you want to check your system configuration, then click Next. The pre-installation steps from this point vary depending on the component or combination of components you are checking. Checking the requirements for some components will require you to provide additional information. Other components simply proceed with the pre-installation check and generate the report. Depending on the component requirements you are checking, review the appropriate sections. If you selected See AppManager repository Checking requirements for the AppManager repository on page 72. AppManager agent Checking requirements for the AppManager agent and managed objects on page 74. Chapter 3 Performing a pre-install check 71

74 6 When the pre-installation check is complete: If you want to View the results now View the results later Do this Click Yes. A document is opened with the default Web browser on your computer. When you're finished viewing the document, close the browser. Click No. Then click OK. When you want to view the document later, open it in a Web browser. The file (<computer>_results.htm) can be found in the directory you specified in Select the folder where you plan to install AppManager: on page 70 (the default directory is c:\program Files\NetIQ). Note If the pre-installation check report indicates there are requirement failures for a particular component, you'll need to update your configuration before you can successfully install that component. If your computer passes the pre-installation check, you are ready to install. See Chapter 4, Starting installation. Checking requirements for the AppManager repository You must have SQL Server 7.0 or SQL Server 2000 on the computer where you are installing the AppManager repository. If you are checking the system requirements for the AppManager repository component: 1 Type the name of the SQL Server and instance, the name of the AppManager repository (optional), and the password for the SQL 72 Installation Guide

75 Server sa account (required), then click Next: For SQL Server name Repository name SQL sa password Type The name of the SQL Server computer and instance, if applicable, for the AppManager repository database. The default is the name of the computer where you are running the setup program. If there are multiple SQL Server instances on the computer, use the format: ServerName\InstanceName The name of the AppManager repository database. The password for your SQL Server sa login account. The default is Null. (If you don t know the sa password, contact your database system administrator.) The setup process requires sa privileges to create the AppManager database, database devices, tables, stored procedures, and the netiq SQL Server login account. The pre-installation check verifies you have a valid sa password. Chapter 3 Performing a pre-install check 73

76 Checking requirements for the AppManager agent and managed objects AppManager can monitor the operating system and one or more server applications on a single managed client. For each server application or system AppManager supports, NetIQ supplies a managed object that extracts application- and system-specific information. Knowledge Script jobs access these managed objects to perform their monitoring functions. If you are checking the system requirements for the AppManager agent component: 1 Select the managed objects for the applications and systems you want to monitor on this managed client, then click Next. The pre-installation program checks the system requirements for each selected managed object. 2 Select any of the Response Time modules you want to install on this managed client, then click Next. The pre-installation program 74 Installation Guide

77 checks the system requirements for each selected Response Time module. For information about installing and using AppManager Response Time modules, see the appropriate module documentation. You can find the documentation in the appmanager\documentation\responsetime folder on the AppManager CD-ROM. 3 Provide any additional information requested, as appropriate. Checking the requirements for some managed objects will require you to provide additional information. Depending on the Chapter 3 Performing a pre-install check 75

78 application requirements you are checking, you may have to provide the following. If you selected Any hardware product, such as: Compaq Insight Manager Dell OpenManage HP TopTools for Servers IBM Netfinity Manager Siemens ServerView Any SQL Server based product, such as: Microsoft SQL Server Microsoft System Management Server Microsoft Message Queue Server You need to Type the SNMP community string for this computer, then click Next. The default community name is public. Type the password for SQL sa login account for the local SQL Server on the computer where you are checking requirements, then click Next. In addition to running the pre-installation check, check for supplemental information on the AppManager CD-ROM, in the appmanager\documentation\supplements folder, and in Work Smarter Guides on the NetIQ Extended Support web site to help you prepare for configuring AppManager to monitor specific applications. Note Once AppManager has been installed in your environment, you can verify system requirements for additional AppManager agents from a centralized location. For information about running the AMADMIN_AgentPreInstall Knowledge Script, see Planning the configuration of AgentInstall jobs on page Installation Guide

79 Review the pre-installation report After you run the pre-installation check, you can view the results. The report is saved in HTML format in the directory you specified as the folder for installing AppManager using the naming convention <computer>_results.htm. You can open the file in a Web browser to see a summary of the requirements checked and whether the computer passed or failed each check. For example: In addition, some requirement checks may post a Warning result. A Warning result indicates that there may be configuration issues or recommendations for changing your current configuration that you should investigate before installing the corresponding AppManager component. Chapter 3 Performing a pre-install check 77

80 For more information about any requirement, click the link in the CheckID column. This displays the <computer>_resultdetails.htm file with detailed information about each requirement. For example: Avoiding common installation problems Sometimes system requirements, even the most basic ones, are overlooked. By running the pre-installation check program and reviewing the system requirement checklists, you should be well prepared to successfully install AppManager, but here are the most common problems you may encounter during installation: For information about this problem Insufficient RAM and available disk space for each AppManager component. Lack of proper permissions for each AppManager component. Lack of network connectivity between computers. See Requirements for each AppManager component on page 57. Check account information on page 63 for a summary of all account requirements. Test network connections on page Installation Guide

81 Chapter 4 Starting installation Because AppManager components can be installed together or separately, this chapter provides a brief overview of the installation process, component installation order, and starting the setup program. Subsequent chapters cover the details about each component independently. This is the way components are typically installed in most production environments independent of each other across multiple computers or in limited combinations. If you want to perform a stand-alone installation with all components installed on the same computer by running Setup once, you may want to review the Sample installation steps in the standalone.chm file located in appmanager\documentation. Getting a preview of the installation After you run the pre-installation check on a computer, you should know whether the computer meets all of the system requirements for the component you want to install. NetIQ strongly recommends running the pre-installation check on every computer that will be part of your AppManager environment. You should also check that you have all the account information and permissions you need to install on each of the computers that will be part of the AppManager environment. 79

82 The typical installation process for most production environments can be summarized as: Plan the implementation Run the Pre-Installation Check Keys to this stage: Assemble a project team. Gather information about the environment and server and account access. Develop a project plan with basic implementation requirements. Identify where components need to be installed, an initial group of managed clients and the managed objects to be installed. Keys to this stage: Locate the computers where components are to be installed and run Setup with Pre-Installation Check selected. Resolve any issues with computers that fail the system requirements check. Install the AppManager backbone Keys to this stage: Run Setup to Install the repository, management server, and Operator Console on selected computers. Test the installation, as needed. Install additional and optional components and local agents Run AMAdmin_AgentPreInstall to check system requirements on remote computers Keys to this stage: Run Setup to install additional management servers, as needed. Run Setup to install additional console programs, as needed. Run Setup to install the Web management server. Run Setup to install agents and managed objects locally on your pilot group of managed clients. Begin configuring security, the AppManager environment and core Knowledge Script jobs. Keys to this stage: Configure several AMAdmin_AgentPreInstall Knowledge Script jobs to check groups of computers you want to manage remotely. Run AMAdmin_AgentInstall to install the agent on remote computers Keys to this stage: Configure several AMAdmin_AgentInstall Knowledge Script jobs to install the AppManager agent and managed objects remotely. 80 Installation Guide

83 Installing components in order AppManager lets you install any combination of components on the same computer. Each time you run Setup, you select the components you want to install on the computer you are using. It s recommended that you always install the AppManager repository component first. You can install other components on the repository server in the same setup process, if desired. Often the management server and repository are installed on the same computer in the same setup process. If you don t select the AppManager management server when you install the repository, you should install at least one management server next. If the AppManager repository and AppManager management server are installed first, details about each managed client can be automatically discovered when you install the AppManager agent. If you don t install the repository and management server first, or don t identify the management server when you install the AppManager agent, then you need to manually run Discovery Knowledge Scripts from the AppManager Operator Console or Operator Web Console after installation to see managed client resources. See the User Guide for more information. Other components can be installed in any order. Starting the AppManager setup program Be sure you have a valid Windows login account with either local or domain Administrator privileges for the workstation or server on which you plan to install any AppManager component. Selecting Setup from the AppManager CD-ROM autorun home page opens the SETUP.EXE file to start the setup program. Chapter 4 Starting installation 81

84 The steps in this section are common to all AppManager components, whether you re installing one or more than one. (To exit the Setup program, click Cancel or press F3.) 1 Insert the AppManager CD-ROM into a CD drive. The CD-ROM autorun program starts your default Web browser and opens the Setup page. If your browser is Microsoft Internet Explorer Then You can run the Installation directly from the browser. At the Setup page: Click Begin Setup. When prompted, select the option to open or run the file (not to save it), then click OK. A Command Prompt window opens and the AppManager setup program starts. Note Optionally, you can manually launch the setup program from the CD-ROM by double-clicking appmanager\setup\setup.exe. Netscape Navigator You can use the Web page to view the Release Notes, access the documentation PDF files, and link to online resources such as the NetIQ Support site. The AppManager setup program can t be run directly from the Setup page, however. Instead, you need to manually start the setup program from the CD-ROM by double-clicking appmanager\setup\setup.exe. 2 At the Welcome dialog box, click Next. 82 Installation Guide

85 3 Click Install Products, then click Next. 4 Select the folder where you plan to install AppManager. To Accept the default folder location (C:\Program Files\NetIQ) Change the folder location Do this Click Next. Click Browse. Select the drive and path name of the folder you want. Click OK. Then click Next. Note Do not install AppManager on a network drive. Chapter 4 Starting installation 83

86 5 Select the AppManager components you want to install on the server or workstation you are using, then click Next. The installation steps from this point vary depending on the component or combination of components you are installing. Most components require at least some configuration. For each component you are installing, follow the instructions in the appropriate chapter to guide you through the rest of the setup. If you select this component AppManager repository AppManager management server AppManager agent AppManager console AppManager Web management server See the setup instructions in Chapter 5, Installing the repository. Chapter 6, Installing the management server. Chapter 8, Installing AppManager agents. Chapter 7, Installing console programs. Chapter 9, Installing the Web management server. Note For convenience, a summary of the steps for starting and completing the installation are included in each chapter. 84 Installation Guide

87 Special installation scenarios In most environments, installing AppManager is a simple process. There are, however, some cases where installing AppManager involves some unique steps or special requirements. These scenarios are not specifically addressed in this chapter and it s recommended that you note the special requirements and additional documentation described in the following table. Ifyouare Upgrading from a previous version of AppManager Installing AppManager components over a network Installing AppManager components on a cluster node Youneedto Install the new version of the repository, management server, console, and Web management server components. It is recommended that you upgrade all components, including all of your managed clients. Upgrading the agent is required if the agent is on a computer where another AppManager component is installed (such as the repository or management server). We highly recommend that you read the Upgrade and Migration Guide, which is included on the AppManager CD-ROM. Create an installation file or SMS package. For information about installing AppManager components silently over the network, see Appendix B, Performing a silent installation. For information about using SMS to install AppManager agents, see your Microsoft SMS documentation. Configure the component for cluster or local operation. See the appropriate section: Installing the repository on a cluster on page 97. Installing the management server on a cluster on page 113. Configuring agents for working in a cluster on page 161. Chapter 4 Starting installation 85

88

89 Chapter 5 Installing the repository This chapter describes the steps for installing the AppManager repository. The following topics are covered: Review the requirements for the repository Start the AppManager setup program Select the AppManager repository Create the repository database and database owner Configure the repository data and log devices Complete the installation Installing the repository on a cluster Review the requirements for the repository Before you install the AppManager repository component, be sure the computer has Microsoft SQL Server 7.0 (with SP3 or later) or Microsoft SQL Server 2000 (with SP2 or later). The AppManager repository can be installed on a local SQL Server on an independent computer, on a local SQL Server on a cluster node, or on a virtual SQL Server in a cluster. For information about installing the AppManager repository on a cluster, see Installing the repository on a cluster on page

90 Start the AppManager setup program Using a valid Windows login account with either local or domain Administrator privileges: 1 Insert the AppManager CD-ROM into a CD drive and start the Setup program. For more information about starting Setup, see Chapter 4, Starting installation. 2 At the Welcome dialog box, click Next. 3 Click Install Products, then click Next. 4 Select the folder where you plan to install AppManager, then click Next. If installing multiple AppManager components on a computer, install them all in the same location. For example, C:\Program Files\NetIQ. Note Select a local drive. Do not install AppManager on a network drive. Select the AppManager repository 1 Select the AppManager repository and any other components you want to install, then click Next. Note It is common to install the repository and management server 88 Installation Guide

91 on the same computer, but not required. NetIQ does recommend that you install the AppManager agent on the computer where the repository is installed. (An agent is automatically installed on the management server even if you don t select it; the agent is not automatically installed if you only select the repository component.) 2 At the License Agreement dialog box, click I have read and agree to be bound by the license agreement for this product, then click Next. 3 At the License Manager dialog box, add the license keys you ve purchased, or accept the default evaluation key, then click Next: 30-day evaluation license key for AppManager components Type the license key in the format nnnnn-nnnnn-nnnnn To install Do this A copy of AppManager that you purchased Type the 15-digit license key number you were given when you purchased AppManager. Use the format nnnnn-nnnnn-nnnnn, then click Add. Note When you purchase AppManager products, you may receive a number of license keys. To simplify the licensing process, you can request a text file that contains the license keys, then click Import to import all of the license keys in a single step. Alternatively, you can use the default key, which is automatically registered, and update the license information after you complete the installation. For more information about updating license information or what to do if you can t locate your license key, see Appendix A, Updating license information. Chapter 5 Installing the repository 89

92 To install An evaluation copy of AppManager Do this The default key is automatically registered and allows you to use all AppManager components for a 30-day evaluation period from the date you install the repository component. Note Once you convert the evaluation copy to a licensed one, you must update the license information. 4 Type your Name and an Organization name, then click Next. Create the repository database and database owner The next step in the setup program creates the repository database and the database owner SQL login account. Because doing this requires the SQL Server sa account permission, the setup program also prompts you to provide the password for the sa account. 90 Installation Guide

93 1 Type the name of the SQL Server computer and the AppManager repository name, then click Next. For SQL Server name Repository name Type The name of the SQL Server computer and instance, if applicable, for the AppManager repository database. The default is the name of the computer where you are running the setup program. If there are multiple SQL Server instances on the computer, use the format: ServerName\InstanceName Note If you are installing on a cluster node, type the network name for the virtual SQL Server. The network name is the virtual server name or computer name that the SQL Client uses to connect to the clustered SQL Server. For more information, see Installing AppManager repository on a virtual server on page 99. A name for the AppManager database. The default is QDB. The repository name you type is referred to as <DBNAME> intherestofthesesteps. Note If there is an existing database on this computer that you don t want to upgrade but you still want to preserve, then give the new repository database a different name than the existing one. Chapter 5 Installing the repository 91

94 2 Type the passwords for the SQL Server sa and netiq users, then click Next. For SQL sa password Type The password for your SQL Server sa login account. The default is Null. (If you don t know the sa password, contact your database system administrator.) The setup process requires sa privileges to create the AppManager database, database devices, tables, stored procedures, and the netiq SQL Server login account, which is used to access the AppManager repository to store and retrieve information. 92 Installation Guide

95 For SQL netiq password Type The password for the netiq SQL Server login account. The default is netiq. The setup program will create the netiq account for you using the password you specify and will define the account as the AppManager repository database owner. The management server uses the netiq SQL Server login account to query and write to the AppManager repository. Note For successful installation, check that the netiq SQL login does not already exist in your SQL Server environment. If this login exists, it may create a conflict unless the database administrator uses SQL Enterprise Manager and sets the Login Properties on the Database Access tab for the account to use a fully qualified account name (DOMAIN\login). 3 If this is the first time you are installing an AppManager repository on this computer, then go to Configure the repository data and log devices on page 94. If you have a previous version of AppManager installed and an upgrade from that version to the current version is supported, you are prompted to choose between an upgrade to the existing database and a fresh installation: Click Upgrade repository Replace existing repository To Upgrade the existing AppManager repository to the current version. Upgrading the repository saves all Knowledge Script and job information. Note You won t see this dialog box if you have a repository from a pre-release version of AppManager on your computer (for example, a beta version). Continue with a fresh AppManager repository installation. Note Be sure you gave the new repository database a different name than the repository that currently exists on this computer if you want to keep the existing repository. Chapter 5 Installing the repository 93

96 Configure the repository data and log devices The next step in the setup program configures the size and location of data and log devices for the repository database. 1 Type the following information or accept the default values, then click Next: For Data file name Data device size Type The name of the AppManager repository database data file. The default name is <DBNAME>Data. Thefile created is named <DBNAME>Data.mdf. The size in MB for the AppManager repository data device. The default is 100 MB. Note AppManager uses 13 MB to store Knowledge Scripts, tables, and stored procedures, but your sizing requirements are largely dependent on your monitoring environment (number of servers, events, and data you expect). Generally, 1 MB for data and events per server, per day, is an appropriate starting point for calculating the size of the repository. SQL Server can be configured to dynamically increase the size of databases, as needed. 94 Installation Guide

97 For Data device path Log file name Log device size Log device path Type The location of the folder where the AppManager database data is stored. For example: C:\Program Files\Microsoft SQL Server\MSSQL\Data The disk space available on the target drive must be larger than the size specified by the Data device size option. Many environments with significant amounts of SQL Server database data save their data devices on a large drive. To browse for the folder location, click the Browse [...] button. The name of the log file for the AppManager repository. The default name is <DBNAME>Log. The file created is named <DBNAME>Log.ldf. The size in MB for the AppManager repository log device. The default is 50 MB. The location of the folder where the AppManager database log is stored. For example: C:\Program Files\Microsoft SQL Server\MSSQL\LOG The disk space available on the target drive must be larger than the size specified by the Log device size option. Many environments with significant amounts of SQL Server database data save their log devices on a large drive. To browse for the folder location, click the Browse [...] button. In creating the repository, the options you are most likely to want to modify are Data device size and Log device size. These options may need adjusting based on the amount of data you intend to collect and the number of computers you plan to monitor. For general guidelines for sizing the repository, see Sizing the AppManager repository on page 44. Note If you change Data device path or Log device path, keep in mind you should not install AppManager software on a network drive. (Additionally, SQL Server should not be installed on a compressed drive.) Chapter 5 Installing the repository 95

98 If you are installing any other components, additional steps may be required before you complete the installation. Follow the on-screen instructions and the information in subsequent chapters to complete the installation. Complete the installation Using the information you have specified, the setup program checks for previously installed AppManager services and then performs a number of automated tasks. During this period, Setup: Creates the repository database. Allocates data and log space. Checks and adjusts configuration options. Installs the database schema, stored procedures, and triggers. Creates the netiq database user login. Checks in all of the Knowledge Scripts. If necessary, the setup program will also add user connections or increase the size of tempdb. Once the repository is successfully installed, you are prompted to register or complete setup. 1 Click Yes to register online immediately and qualify for early notification of upgrades, regular newsletters, and special promotions. If you have Internet access, your default Web browser is opened at the NetIQ AppManager online registration Web site. Follow the instructions for filling out and submitting the registration form. Click No to skip registration. You can register later through the Operator Console. 2 When setup is complete, click OK. 96 Installation Guide

99 Installing the repository on a cluster AppManager supports installation of the repository on a cluster. Installing the AppManager repository and management server on a Microsoft Cluster Service (MSCS) server can help ensure that the management and monitoring of your network environment continues uninterrupted. MSCS provides fault tolerance and uninterrupted service by detecting the failure of applications and servers and automatically recovering resources and workload. Understanding Microsoft Cluster Service terminology A cluster is a collection of one or more Windows servers that work together. Each Windows server that is part of the cluster is called a cluster node. Nodes share one or more SCSI disks, which are called cluster shared disks, and manage cluster resources. A cluster resource is a basic system entity (for example, a physical disk, process, service, network address, or network name). A cluster group is a collection of one or more cluster resources related either logically or physically by dependency. When a node provides resources and executes processes belonging to a cluster group, the node owns the cluster group and all of its resources. A node in a cluster may own different cluster shared disks at different times; however, each shared physical disk (and all logical disks on the physical disk) is owned by only one cluster node at a time. A failover happens when one or more cluster resources in a cluster group fail and MSCS migrates the problematic group from one node to another. Ownership of the group is transferred to the new node at the time the failover takes place. When installing MSCS, you specify the network name of the cluster. This name is important because it becomes the name of the virtual servers you install on the cluster. A virtual server is an application server within a cluster group. Executable and other dependent files of a virtual server are installed Chapter 5 Installing the repository 97

100 on a cluster shared disk so that each node in the cluster can execute the program. Clients connect to the virtual server through a cluster resource network name. The network name which is part of the cluster group provides transparent access to the virtual server regardless of which cluster node currently owns the group. If a failover takes place, ownership of the group including the network name is transferred to the new cluster node. The node restarts all member processes of the virtual servers in the group. Because the client uses the network name to connect to the virtual server, it doesn t matter that a different node now owns the group. There are various execution modes for a virtual server, including: Active/passive (also referred to as active/inactive): In this mode, there can be only one active instance of the virtual server among all nodes in the cluster. When a failover happens and MSCS migrates the virtual server from one node to another, the virtual server becomes passive on the old node and active on the new node. Active/active: In this mode, there can be active instances of the virtual server on more than one node in the cluster. To distribute the workload evenly among all cluster nodes, each instance of an active/active virtual server is usually configured to run on a different cluster node. When a cluster node is brought down or fails, the virtual server instance is migrated to another cluster node, along with the rest of the cluster group. The AppManager repository can be installed on a virtual SQL Server instance running in either active/passive or active/active application mode. In active/passive mode, there can only be one AppManager repository with the same name on each instance of the virtual SQL Server. Therefore, to have multiple repositories on the same instance of a virtual server, the repository names must be unique. If the virtual SQL Server is running in active/active application mode, each active instance of a virtual server can have a repository with the same name. 98 Installation Guide

101 Accounts needed to install the repository on a cluster The AppManager setup program requires following account information to install the repository on a cluster: A valid Windows login account with either Local or Domain Administrator privileges. Network name for the virtual SQL Server. The password for the SQL Server sa login account. Installing AppManager repository on a virtual server When installing the AppManager repository, the AppManager setup program prompts you to identify the repository server name (Step 1 on page 91). If you type the local server name for the cluster node, the repository is installed on the cluster node acting as a stand-alone server. The AppManager repository is not cluster-enabled and you don t get the benefits of MSCS, such as availability. To install the repository on a virtual SQL Server in the cluster: 1 Type the network name for the virtual SQL Server. The network name is the virtual server name or computer name that the SQL Client uses to connect to the clustered SQL Server. If there are multiple SQL Server instances on the computer, use the format VirtualServerName\InstanceName. Chapter 5 Installing the repository 99

102 For example, if the repository is being installed on a SQL Server 2000 computer with the local host name vanilla but using the virtual server name spice and the coreapps instance: 2 Click Next and continue with the installation as described from Step 2 on page 92 on. AppManager Knowledge Script files are installed on the cluster shared disk in the <drive>\program Files\NetIQ\AppManager\qdb directory. 100 Installation Guide

103 Chapter 6 Installing the management server This chapter describes the steps for installing the AppManager management server. The following topics are covered: Start the AppManager setup program Select AppManager management server Configure the connection to the repository Specify an account for the service to use Select the security level Configure the ports to use Complete the installation Installing the management server on a cluster Start the AppManager setup program Using a valid Windows login account with either local or domain Administrator privileges: 1 Insert the AppManager CD-ROM into a CD drive and start the Setup program. For more information about starting Setup, see Chapter 4, Starting installation. 2 At the Welcome dialog box, click Next. 3 Click Install Products, then click Next. 101

104 4 Select the folder where you plan to install AppManager, then click Next. If installing multiple AppManager components on a computer, install them all in the same location. For example, C:\Program Files\NetIQ. Note Select a local drive. Do not install AppManager on a network drive. Select AppManager management server 1 Select the AppManager management server and any other components you want to install, then click Next. Note For the AppManager management server to handle actions or install agents remotely from a centralized location, the AppManager agent component must be installed on the computer where the management server resides. Therefore, the agent is automatically installed on the management server even if you don t select it. Selecting the agent, however, allows you to configure its operation and select what you want to monitor on the management server during the setup process. (When the agent is installed automatically, it is configured with all default values.) Keep in mind, however, that you should not enable the agent on the management server for reporting and that you should minimize the number of jobs this agent is responsible for running. 102 Installation Guide

105 Configure the connection to the repository The next step is to configure communication between the management server service and the AppManager repository. To do this, you need to specify the data source name the management server should use to connect to the repository, the repository database name, and the name of the computer where the repository is installed. 1 Type the following information or accept the default values, then click Next: For DataSourceName Type TheODBC32DataSourceName(DSN)forthe AppManager management server. The management server service (NetIQms) usesthisdsnto communicate with the AppManager repository database. If you install the repository and the management server on the same computer during the same setup process, the default name of the DSN is <DBNAME>ms. If you install the management server on a separate computer or during a separate setup process, the default DSN name is QDBms. In most cases, the default DSN can be used. Chapter 6 Installing the management server 103

106 For Repository name Repository server name Type The name of the AppManager repository database. The database name is required for the DSN configuration. If you are installing the repository and the management server on the same computer during the same setup process, the default name of the database is the <DBNAME> you specified when you created the repository. If you install the management server on a separate computer or during a separate setup, the default database name is QDB. The name of the SQL Server computer and instance, if applicable, where the AppManager repository database is located. If there are multiple SQL Server instances on the computer, use the format: ServerName\InstanceName The location of the database is required for DSN configuration. The default location is the SQL Server computer on which the management server component is being installed. Cluster support: If the AppManager repository is installed on a virtual SQL Server on a cluster, be sure to enter the network name of the virtual server (not the local computer name). For more information, see Installing the management server on a cluster on page Installation Guide

107 2 Type the password for the netiq SQL Server login account on the server where the AppManager repository is installed, then click Next: The password for the netiq SQL login is required because the netiq account is the one that the DSN uses to connect to the database. You define the password for the netiq SQL Server login account when you install the repository. The default is netiq. If you install the AppManager repository and management server at the same time, this step is skipped. Note For successful installation, check that the netiq SQL login does not already exist in your SQL Server environment. If this login exists, it may create a conflict unless the database administrator uses SQL Enterprise Manager and sets the Login Properties on the Database Access tab for the account to use a fully qualified account name (DOMAIN\login). Specify an account for the service to use Typically, the NetIQ AppManager Management Service runs using the LocalSystem account. If your SQL Server uses Mixed Mode security, you can leave the service to run under the LocalSystem account or identify a specific Windows user account for the service to run under (this account is sometimes referred to as a service account or a Chapter 6 Installing the management server 105

108 run-as account ). If your SQL Server uses Windows Authentication mode security, however, you must specify a valid Windows login account for the NetIQ AppManager Management Service to use. The account you use should have dbo or db_owner rights for the AppManager repository database. Note The account information you enter must be valid in the domain you specify. If you haven t created a login account to use or don t have valid account information, exit Setup and create the user account in Windows, then resume installation. 1 Select the type of account for the NetIQ AppManager Management Service (NetIQms) to use, then click Next. If you want the management server to run using a Windows user account, you will need to specify the domain, user name, and password for the account in the next step. If you use the Local System account, you skip the next step and go on to complete the installation. If the setup program can connect to the SQL Server where the AppManager repository is installed and it detects the Windows Authentication mode, this step is skipped and you are prompted for the domain, user name, and password directly. Note If the SQL Server where the AppManager repository is installed is on a different computer than the management server, the management server must run as an account with network access 106 Installation Guide

109 to the remote computer. The Local System account does not provide network access. If you use an account that does not have network access permission, the management service will get installed but will not run or communicate with the repository. Therefore, if your AppManager repository and management server are on different computers, select the Use Windows account option and specify an account with network access to the SQL Server to install or upgrade. 2 Type the account information for the account you want to use, then click Next: For Windows account domain Windows account user Windows account password Type The name of the domain to which the Windows login account belongs. The name of the Windows login account you want to designate as the service account for the service to use. The default is netiq_nt. Note The Windows login account can t bethe LocalSystem account. Password of the Windows login account. Chapter 6 Installing the management server 107

110 Select the security level The next step in the setup process is to configure security for communication between the management server and Windows-based managed clients. 1 Select the type of security to enforce, then click Next. Click Todothis Maximum security to encrypt all communication Encrypt all communication between the management server and Windows-based managed clients. Note You must use the rpckey.exe program to generate a key file before installing the management server. For more information about enforcing and managing secure communication, see the Administrator Guide. Standard security to set authorization on each managed client Allow unencrypted communication between the management server and managed clients. Note If you select this option, you can still authorize communication between specific management servers and managed clients when you install the AppManager agent. See When you select standard security on page 139 for more information. 108 Installation Guide

111 2 If you selected Maximum security to encrypt all communication, type the location for the key file generated with the rpckey.exe program, and the password for secure communication, then click Next. For Type Location of the key file The full path to the encrypted key file created by the rpckey.exe program on the local computer. This file is required for encrypted communication. Note If the key file is not on the local computer, click the Browse button to locate the computer on your network and navigate to the file. If you did not generate this file before installation, exit the setup program and follow the steps described in Generate an encrypted key file on page 67 to generate the file, then rerun setup. Password The password used to encrypt and decrypt the key file. Use the same password you specified when you created the key file. This password must be the same password you specify for each managed client that communicates with this management server using encrypted data. The default password is netiq. For more information about encrypting communication between the management server and managed clients, see the Administrator Guide. Chapter 6 Installing the management server 109

112 Configure the ports to use To enable communication between the NetIQ AppManager Management Service (NetIQms) and the AppManager agent you need to specify the ports that the management server and agent use. The port information must be set to use the correct ports on both the management server and each managed client the management server communicates with. For example, if you change the port that the management server binds to for receiving information from the managed client but don t set corresponding port information when you install the AppManager agent, there will be no communication between the management server and the managed client. Configuring port communication for Windows To enable communication between the NetIQ AppManager Management Service (NetIQms) and the NetIQ AppManager Client Resource Monitor Service (NetIQmc) and Client Communication Manager Service (NetIQccm), you need to specify the ports that the services listen on. Typically, the default ports with the management server sending data to the managed client using port 9999 and receiving data from the managed client using port 9998 are appropriate. 110 Installation Guide

113 1 Click Next to accept the default ports or change port information, then click Next. Note In most organizations, it s recommended that you consult your security administrator before changing port information. Configuring port communication for UNIX After you are prompted to configure the ports for the management server and managed clients to listen on for communication in the Windows environment, you are prompted for the port number for UNIX agents to use for communication with the management server to enable UNIX support. Chapter 6 Installing the management server 111

114 If you are not monitoring any UNIX computers, select Do not bind a port for managing UNIX servers, then click Next. If you want to monitor UNIX computers with AppManager: 1 Click Bind management server port for UNIX agents to enable UNIX support. 2 Type a new port number or accept the default port for the management server to use for communication from UNIX agents, then click Next. Note Be sure to select an available port that does not conflict with any existing communication point. In most organizations, it s recommended that you consult your security administrator before changing port information. Complete the installation Using the information you have specified, the setup program checks for previously installed AppManager services and then performs a number of automated tasks. During this period, Setup: Creates the ODBC32 data source name. Registers and configures the NetIQ AppManager Management Service for the management server. 112 Installation Guide

115 Note If the management server has been installed previously on this computer, you have the option to retain your existing registry settings or to recreate the registry, which may remove or change some registry key names or values. For information about registry key settings, see the Administrator Guide. Once the management server is successfully installed, you are prompted to complete setup. Click OK. Installing the management server on a cluster The AppManager management server can be installed on Microsoft Cluster Service (MSCS) to help ensure that the management and monitoring of your network environment continues uninterrupted. To do this, the AppManager management server runs as a virtual server on MSCS. A virtual server is an application server within a cluster group. Executable and other dependent files of a virtual server should be installed on a cluster shared disk so that each node in the cluster can execute the program. Clients then connect to the virtual server through a cluster resource network name. The network name provides transparent access to the virtual server regardless of which cluster node currently owns the group. The repository and management server can be installed on the same cluster or on different clusters, as needed. Note For a brief introduction to MSCS and cluster terminology, see Understanding Microsoft Cluster Service terminology on page 97. Accounts needed to install on a cluster The AppManager setup program requires the following account information to install the management server on a cluster: A valid Windows login account with either Local or Domain Administrator privileges. Chapter 6 Installing the management server 113

116 An account for the NetIQms service to run under, either the LocalSystem account or a valid Windows login account. Running Setup on a cluster node To install the management server on a cluster, run the AppManager setup program on the cluster node that currently has ownership of the shared disk where you want to install the AppManager management server. (You can use Cluster Administrator to change ownership of a shared disk to the cluster node you want.) When installing the AppManager management server on a cluster node, the AppManager setup program asks whether you want to install the management server to a cluster node or a local computer. 1 Select Cluster shared disk to install the management server on a cluster. If you select Local cluster node as a stand-alone server, the management server is installed on the local cluster node acting as a stand-alone server (the management server is not cluster-enabled and you don t get the benefits of MSCS, such as availability). 2 When prompted with a list of all shared disks owned by the cluster node on which you are running the AppManager setup program, 114 Installation Guide

117 select the shared disk where you want the management server to reside, then click Next. The new destination is displayed for confirmation. Click Next. 3 Continue with the installation described in Configure the connection to the repository on page 103. Note If the AppManager repository is installed on a clustered virtual SQL Server, be sure to enter the network name of the virtual server (not the local computer name) when prompted for the repository server name Step 1 on page 102. If the AppManager repository is installed on a virtual SQL Server: Type the network name of the virtual server (not the local computer name) using the format: ServerName\InstanceName Chapter 6 Installing the management server 115

118 When you install the AppManager management server on one cluster node, the setup program automatically installs the management server on the other nodes in the cluster. A NetIQms cluster resource is created and is added to either: An existing cluster group, if other cluster resources depend on the shared disk on which the management server was installed or A newly created cluster group, if no other cluster resources depend on the shared disk. The cluster group is then migrated to the other nodes in the cluster. To minimize the amount of time it takes to migrate the cluster group, it s recommended that you install the management server on a shared physical disk that other cluster resources aren t dependent on. After you install the AppManager management server on a cluster node, move the Quorum Disk for the cluster to the NetIQms cluster resource. Moving the Quorum Disk ensures proper fail-over operation. Operating in active/passive mode on a cluster After you install the management server on a cluster node, the AppManager management server operates in an active/passive application mode. In this mode, there can be only one active instance of the virtual server among all nodes in the cluster. When a failover happens and MSCS migrates the virtual server from one node to another, the virtual server becomes passive on the old node and active on the new node. Installing AppManager agents on each cluster node When the management server is installed on a cluster node, the AppManager agent and the Windows NT managed object are automatically installed on that node only. You must install the agent on each of the other nodes in the cluster. Note When you install the AppManager agent and are asked to provide the name of the AppManager management server, the name of the 116 Installation Guide

119 clustered management server is the network name of the cluster, which is specified when you install MSCS. Configuring communication with managed clients It is important that the AppManager agent on the managed client communicate with the clustered AppManager management server using the network name of the management server, not the IP address. After installing the management server on a cluster and installing the AppManager agent on the computers the management server communicates with: 1 Start an AMAdmin_ConfigSiteCommType Knowledge Script job on all managed clients that are monitored by the management server. 2 In the Properties dialog, click the Values tab and set the Communication via IP address parameter set to n. This setting changes the communication method from IP address to host name. 3 Click OK to run the job. For more information about this Knowledge Script, see the Knowledge Script Reference Guide, or select the script in the Knowledge Script pane and press F1. Chapter 6 Installing the management server 117

120

121 Chapter 7 Installing console programs This chapter describes the steps for installing AppManager console programs. Console programs include the central interface for AppManager the Operator Console and a variety of special purpose consoles for managing security, creating charts, viewing events or database tables, and performing other tasks. Starting the AppManager setup program Using a valid Windows login account with either local or domain Administrator privileges: 1 Insert the AppManager CD-ROM into a CD drive and start the Setup program. For more information about starting Setup, see Chapter 4, Starting installation. 2 At the Welcome dialog box, click Next. 3 Click Install Products, then click Next. 4 Select the folder where you plan to install AppManager, then click Next. If installing multiple AppManager components on a computer, install them all in the same location. For example, C:\Program Files\NetIQ\. Note Select a local drive. Do not install AppManager on a network drive. 119

122 Select the AppManager console 1 Select the AppManager console and any other components you want to install, then click Next. 2 Type your Name and Organization name, then click Next. 120 Installation Guide

123 3 Select the AppManager console programs you want installed on this computer: Select this console Operator Console To do this View the servers and workstations on the network, check system configurations, and view information about the availability and performance of server and application resources. Operator Console MMC Snap-In Add the AppManager Operator Console as an MMC snap-in. This enables you to access AppManager s Operator Console features from within MMC. Security Manager Distributed Event Console Developer s Console Utilities Manage security for an AppManager site. The Security Manager allows you to identify users who are allowed to access AppManager, define user roles and rights, and maintain passwords and other secure information. View event information on one or more AppManager repositories. Add custom icons and Knowledge Scripts to the AppManager repository. The Developer s Console includes tools and utilities for script development. For more information about using these utilities, see Developing Custom Knowledge Scripts for AppManager. Chapter 7 Installing console programs 121

124 AppManager requires at least one Operator Console to be installed in your environment. There are three variations on the Operator Console: the standard Windows program, the Web interface console, and the MMC Snap-in console. All three provide roughly equivalent functionality in slightly different ways, but at a minimum you should install one standard Operator Console in your environment. (For the Operator Web Console, you need to install the Web management server component in your environment. See Chapter 9, Installing the Web management server. ) When you purchase the AppManager Developer s Console, you get licensing keys for all of the programs associated with the AppManager console component plus several extra utilities, such as the Developer Console for creating custom Knowledge Scripts, the Icon Manager which enables you to add custom icons to the AppManager repository, and the Knowledge Script Editor for editing and debugging your Knowledge Scripts. For information about these utilities, see Developing Custom Knowledge Scripts for AppManager and AppManager Help. 4 Click Next. The next time you reboot the computer, the system path will be updated. Note If you plan to immediately install any AppManager connector product (such as the AppManager Connector for Tivoli Enterprise), be sure to first reboot the system so that the system path is updated with the \NetIQ\AppManager\bin folder. For information about installing AppManager connectors, see the appropriate connector documentation. You can find the documentation for connectors on the AppManager CD-ROM in the corresponding appmanager\connectors\connector_name\documentation folder. For example, the documentation for the AppManager Connector for Tivoli Enterprise is in the folder: appmanager\connectors\tivoli\documentation 122 Installation Guide

125 Complete the installation The setup program checks for previously installed AppManager consoles, then installs the selected console programs and associated help files on the computer. Once the console programs are successfully installed, you are prompted to complete setup. Click OK. Chapter 7 Installing console programs 123

126

127 Chapter 8 Installing AppManager agents The AppManager agent is the component you install on all of the servers you want to monitor. The steps for installing the agent and what gets installed on the managed computer vary depending on the environment you are monitoring. In a Windows environment, you can install the agent: Locally by running the setup program from the AppManager installation CD-ROM or from an AppManager distribution directory. Remotely using the AMAdmin_AgentInstall Knowledge Script after you have installed the AppManager repository, management server, and console on at least one computer in your environment. In a UNIX environment, you can install the agent: Locally by running the installation script netiq_agent_install from the NetIQ AppManager UNIX Components CD-ROM. This chapter describes the steps for installing the agent component on a Windows computer using the setup program and using the AMAdmin_AgentInstall Knowledge Script. It also provides a brief discussion of installing the agent on a UNIX computer. For additional information about installing and working with the NetIQ UNIX Agent, see Monitoring UNIX Servers with AppManager (am_unix.pdf) in the UNIX/documentation directory of the NetIQ AppManager UNIX Components CD-ROM. 125

128 Installing agents in a Windows environment When you install the AppManager agent component on Windows computers, you actually install a package that consists of: NetIQ AppManager Client Resource Monitor (NetIQmc) NetIQ AppManager Client Communication Manager (NetIQccm) Local repository for storing data and events At least one managed object probe (the Windows managed object) You can install the AppManager agent by running the setup program locally on a computer. After you have installed the AppManager repository, management server, and console on at least one computer in your environment, you can also install the AppManager agent on a computer or group of computers by running the AMAdmin_AgentInstall Knowledge Script. In most organizations, administrators run the setup program on a small number of servers to get started, then expand the deployment by running Knowledge Script jobs on additional distributed servers in the environment. Installing agents locally using the setup program Using a valid Windows login account with either local or domain Administrator privileges: 1 Insert the AppManager CD-ROM into a CD drive and start the Setup program. For more information about starting Setup, see Chapter 4, Starting installation. 2 At the Welcome dialog box, click Next. 3 Click Install Products, then click Next. 4 Select the folder where you plan to install AppManager, then click Next. If installing multiple AppManager components on a 126 Installation Guide

129 computer, install them all in the same location. For example, C:\Program Files\NetIQ. Note Select a local drive. Do not install AppManager on a network drive. Select the AppManager agent and managed objects 1 Select the AppManager agent and any other components you want to install on the server or workstation you are using, then click Next. 2 If this is the first time you are installing an AppManager agent on this computer, then go to Step 3 on page 129. If you have previously installed the AppManager agent on this computer, you are prompted to choose between replacing the Chapter 8 Installing AppManager agents 127

130 current services, repository, and managed objects or adding managed objects not previously installed: Click Replace the agent services, local repository, and managed objects Install only new managed objects To Reinstall the AppManager agent, local repository, and managed objects. The AppManager agent services (NetIQmc and NetIQccm) and any running jobs are stopped, and the local repository on the managed client will be replaced. Install only managed objects that were not previously installed. The AppManager agent services, running jobs, and the local repository are not affected. Note If you are upgrading from a previous release of AppManager, see the Upgrade and Migration Guide. Keep in mind that you should always upgrade the repository and management server before attempting to upgrade agent computers. 128 Installation Guide

131 3 Select the managed objects for the applications and systems you want to monitor. Only the AppManager managed objects for those Windows applications and systems that are on the managed client appear in the list If you selected Install only new managed objects in Step 2 on page 127, you won t be able to select any managed objects previously installed on this managed client. For example, if the Microsoft SQL Server managed object is already installed, then that item in the list will be grayed out. 4 Click Next. Chapter 8 Installing AppManager agents 129

132 5 Select the Response Time modules you want to install, then click Next. Note For information about working with any of the Response Time modules, see the appropriate Response Time documentation. You can find documentation for each Response Time module on the AppManager CD-ROM in the appmanager\documentation\responsetime folder. Configure agent options The next several steps allow you to configure communication with the local repository, establish the management server(s) this computer communicates with, and set other options. The selections you make will affect which additional screens you see. 130 Installation Guide

133 1 Set these options as needed, then click Next. Check this option Perform discovery To Automatically attempt an AppManager discovery process on this computer during setup. The discovery process gathers information about a computer s operating system resources (CPU, disk, memory, etc.) and server resources (for example, SQL Server Database Devices and Exchange Server MTA Queues). You must identify the management server and the network connection to that computer must be up to successfully perform an automatic discovery. See Identify a management server for discovery on page 140. Deselect this option if you want to manually run discovery. You can continue the installation, then run discovery from the Operator Console after installation. See the User Guide for more information. Note Some applications require you to run a Discovery Knowledge Script manually after installation. For example, the Discovery for SAP R/3 (Discovery_SAP) must be run after installation. Chapter 8 Installing AppManager agents 131

134 Check this option To Use computer name in the Operator Console display Display the name of this computer in the AppManager Operator Console after discovery. Deselect this option if you want to specify the name or address you want displayed. If you deselect the option, you are prompted to specify an IP address, DNS name, or some other identifying name. Use default RPC port number Enable MAPI mail Enable report agent Use the default ports for communication between the managed client and the management server. Deselect this option if you changed the port information when you installed the management server. See Configure the ports to use on page 140 for more information. Set up an Exchange profile and mailbox to send MAPI mail as an action from this computer. For more information, see Configuration for sending MAPI mail as an action on page 187. If you check this option, you are prompted to specify an account for the AppManager agent services to use. See Specify an account for the service to use on page 133. Note You won t see this option if the Exchange Server managed object was selected in Step3on page 129. Allow this managed computer to execute the report scripts that are used to configure and create reports. If you check this option, you are prompted to specify a Windows account for the AppManager agent services to use. See Specify an account for the servicetouse on page 133. See the Reporting Guide for more information. Note To discover the report-enabled agent, run the Discovery_ReportAgent Knowledge Script after installation. 2 Click Next to accept the default folder for the local repository on the managed client, or click Browse to specify a new path for the local repository, then click Next. 132 Installation Guide

135 Note Depending on the combination of options you select, you are prompted for additional configuration information. Specify an account for the service to use Typically, the NetIQ AppManager Client Resource Monitor (NetIQmc) and the NetIQ AppManager Client Communication Manager (NetIQccm) both run using the LocalSystem account. In some cases, however, you must run these services using a valid Windows user account. In a few rare cases, you may also need the account to have specific privileges, such as Domain Admin privileges. You must specify a valid Windows login account for the agent services to use, if you are: Monitoring SQL Server on a computer and using SQL Server s Windows Authentication mode security Enabling MAPI mail as an action on the local computer Enabling the report agent on the local computer In addition, some application managed objects (such as the managed object for Exchange Server, Exchange Server 2000, and SAP R/3) require agent services to run using a Windows login account. See the Knowledge Script Guide for a list of Knowledge Scripts that have special requirements. Note Depending on the configuration options you select, you may be allowed to select the LocalSystem account or a Windows account or be required to specify a Windows account. If you are specifying a Windows account, be sure that the account has been configured with the Log On As Service right. If the account does not have this right, the agent services will fail to start. You can configure this right after installation, if needed, but will need to start the services manually if you do so. Chapter 8 Installing AppManager agents 133

136 To specify a Windows account for the AppManager agent services to run as: 1 Select Use Windows account. 2 Type the account information for the account you want to use, then click Next. For Domain User name Password Type The name of the domain to which the Windows login account belongs. The name of the Windows login account you want to designate as the service account for the NetIQmc and NetIQccm services. The default is netiq_nt. Note The Windows login account can t bethe LocalSystem account. Password of the Windows login account. Note You can modify the account used by the services at any time using the Services Control Panel. Both services, however, must always be configured to use the same account information. 134 Installation Guide

137 Enabling MAPI mail If you set the Enable MAPI mail option to enable sending MAPI mail as an action in response to an event, you need to specify a Windows account to use, and the Exchange Server, profile name, and mailbox alias to send mail from. 1 Type the Windows account information for the account you want to use, then click Next. 2 Type the name of the Exchange Server, profile, and mailbox alias to use for sending mail from this computer, then click Next. For Exchange Server Profile Type Name of the Microsoft Exchange Server. Exchange client profile name that the AppManager agent on the managed client will use to send test mail messages to monitor Exchange connectivity. The AppManager setup program automatically creates the Exchange profile for the mailbox. The default is netiq-<computer>. Chapter 8 Installing AppManager agents 135

138 For Mailbox alias Type Exchange mailbox alias name for the service account (sometimes called the run-as account) of the NetIQmc service. The default is netiq-<computer>. If the mailbox alias doesn t already exist for the user and profile, you need to use Exchange Administrator to set it up. For information about how to create the mailbox, see Configuration for sending MAPI mail as an action on page 187. Note If during setup you don t enter the Exchange Server profile and mailbox alias name, then you ll need to register the Exchange information using the AppManager Security Manager. Also use the Security Manager if you want to change or update this information. For more information, see Using the Security Manager to update information on page Installation Guide

139 Configure the level of security The next step in the setup process is to configure security for communication between the management server and Windows-based managed clients. 1 Select the type of security to enforce, then click Next. Click Maximum security to encrypt all communication Standard security to authorize communication with specific management servers Todothis Encrypt all communication between the management server and managed clients. Note You must use the rpckey.exe program to generate a key file before installing the agent. If you select this option, you are prompted to type the location and password for the key file. For more information, see the Administrator Guide. Specify a list of AppManager management servers that are authorized to communicate with this managed client. If you select this option, you are prompted to type the names of the AppManager management servers that are authorized to communicate with this managed client, separated by commas. Note If you are specifying management server names and a management server is installed on a cluster, type the network name of the management server. Chapter 8 Installing AppManager agents 137

140 When you select maximum security If you select Maximum security to encrypt all communication, type the location and password for the key file then click Next. 1 Type or browse to the location of the key file you created before installing. If you have not already created the key file, click Cancel to exit the setup program, create the key file, then rerun setup. For more information about creating the key file, see Generate an encrypted key file on page Type the password you set when you created the key file. 3 Click Next. 138 Installation Guide

141 When you select standard security If you select Standard security to authorize specific management servers, type the names of the management server computers authorized to communicate with this managed client, then click Next. To Authorize one or more specific management servers Do this Type the names of the management server computers you want authorized to communicate with this managed client, separated by commas with no spaces, then click Next. Note If you want to specify a list of management servers, be sure that the list includes the management server you will use for performing discovery. See Identify a management server for discovery on page 140. Allow all management servers to access this managed client Accept the default (*), then click Next. Note If your management server is installed on a cluster, you should accept the default to allow all management servers to communicate with the managed client during installation. You should do this because default communication is based on the management server IP address rather than host name. After installation, you can use the AMAdmin_ConfigSiteCommType Knowledge Script to change the communication to use a host name (the virtual server name). Chapter 8 Installing AppManager agents 139

142 Identify a management server for discovery To automatically attempt to discover computer resources during setup, you need to identify a management server to communicate with. The network connection between the specified management server and the managed client computer must be up for discovery to succeed. In addition, if you are using standard security and specified a list of authorized management servers, be sure to use one of the specified management servers for attempting discovery. 1 Type the name of the computer on which the AppManager management server resides, then click Next. Note If the agent will be communicating with a management server that is installed on a cluster, be sure to enter the network name of the management server, which is the network name of the cluster. For more information, see Configuring agents for working in a cluster on page 161. Configure the ports to use If you aren t using the default RPC port to enable communication between the management server and the NetIQ AppManager Client Resource Monitor Service (NetIQmc) and Client Communication Manager Service (NetIQccm), you need to specify the ports that the services listen on. 140 Installation Guide

143 The port information must be set correctly to use the same ports on both the management server and each managed client the management server communicates with. For example, if you change the port that the management server binds to when you install the management server but don t set corresponding port information when you install the AppManager agent, there will be no communication between the management server and the managed client. Typically, the default ports with the management server sending data to the managed client s listening port 9999 and receiving data from the managed client using port 9998 are appropriate. If you unchecked the Use default RPC port number option: 1 Click Next to accept the default ports or change port information, then click Next. Note In most organizations, it s recommended that you consult your security administrator before changing port information. Configure information for managed objects AppManager can monitor one or more server applications and systems on a managed client. When you select the systems and applications to monitor in Step 3 on page 129, you select a corresponding managed object that is used to extract application- and Chapter 8 Installing AppManager agents 141

144 system-specific information for Knowledge Scripts to use when they perform monitoring functions. Typically, managed objects are packaged in a DLL. For example, QSQLA4.DLL is the name of the managed object for monitoring SQL Server. During setup, the selected managed object s DLL is installed in \NetIQ\AppManager\bin and automatically registered. Note The Windows NT managed object, which also supports Windows 2000, Windows XP, and Windows Server 2003, is automatically installed when you select the AppManager agent component. In most cases, simply selecting what you want to monitor is sufficient and the setup program proceeds to completing the installation. Some AppManager managed objects, however, require additional configuration information. For this system or application Compaq Insight Manager Dell OpenManage HP TopTools for Servers IBM Netfinity Manager or Director Siemens ServerView Microsoft Message Queue Service Microsoft SMS You need to Type the SNMP community string, then click Next. Type the password for the local SQL Server sa account, then click Next. Note If installing on a cluster, you are prompted for the SQL Server sa password for all SQL Servers in the cluster. For more information, see Configuring agents for working in a cluster on page Installation Guide

145 For this system or application Microsoft SQL Server Lotus Domino You need to Type the password for the SQL Server sa account or leave this field blank, then click Next. If the agent runs using a domain account on the server, you can leave the password field blank to use the service account information instead of the sa account. To use the service account, click Next. If you are installing on a computer that has SQL Server 6.5 and you are using SQL Server authentication, you must provide the sa password. If you are installing on a SQL Server 7.0, SQL Server 2000, or any SQL Sever using Windows authentication, you can use the service account. Note If installing on a cluster, you are prompted for the SQL Server sa password for all SQL Servers in the cluster. For more information, see Configuring agents for working in a cluster on page 161. Click Yes to have the Lotus Domino configured for monitoring by AppManager automatically. If you click No, run the NetIQ Domino configuration program (nqdomconf.exe) after installing AppManager. For more information, see the Domino configuration notes in the appmanager\documentation\supplements\ am_domino.pdf file on the AppManager CD-ROM. Chapter 8 Installing AppManager agents 143

146 For this system or application Microsoft Exchange Server (5.5) Microsoft Exchange Server 2000 You need to 1 Type account information for the agent services to use, then click Next. 2 Click Yes to automatically create the Exchange profile and mailbox alias for AppManager to use. If you click No, you need to manually create the mailbox. 3 Type names for the Exchange profile and mailbox, then click Next. For more information, see the Exchange configuration notes in the appmanager\documentation\supplements\ am_exch.pdf file on the AppManager CD-ROM. Type account information for the Exchange 2000 management service to use, then click Next. If the account does not already exist, the setup program can automatically create it. If the account and mailbox exist: 1 Type a name for the Exchange profile to be created, then click Next. If the account exists but the mailbox is not enabled: 1 Select Create Exchange 2000 Mailbox, then click Next. 2 Select a mailbox store as a home location for the mailbox. 3 Type names for the Exchange profile and mailbox, then click Next. If the account and mailbox are new: 1 Select Create User Account and Exchange 2000 Mailbox, then click Next. 2 Select a mailbox store as a home location for the mailbox. 3 Type names for the Exchange profile and mailbox, then click Next. For more information, see the Exchange configuration notes in the appmanager\documentation\supplements\ am_exch2k_config.pdf file on the AppManager CD-ROM. 144 Installation Guide

147 For this system or application Novell NetWare Oracle RDBMS Server SAP R/3 You need to Click Yes to keep the existing NetWare configuration file if you are upgrading from a previous version of AppManager. If you click No, the NetWare configuration file nwmlm.cfg is overwritten. For more information, see the NetWare configuration notes in the appmanager\documentation\supplements\ am_netware.pdf file on the AppManager CD-ROM. 1 Select the databases you want to monitor. 2 Type the name of a single Oracle user account with permission to access each database that you want to monitor. 3 Type the password associated with the user account name on each database. The installation program prompts you for a password for each database. Although the user account name must be the same on all databases, each database can have a unique password. For more detailed information, see the Oracle configuration notes in the appmanager\documentation\ supplements\am_oracle_config.pdf file on the AppManager CD-ROM. Enter configuration information for the SAP proxy database. 1 Type the server name, instance name, and database name for the proxy database. 2 Type the sa and netiq passwords for the proxy database. 3 Configure the data and log file name, location, and size. For more detailed information, see the SAP R/3 configuration notes in the appmanager\documentation\ supplements\am_sap_config.pdf file on the AppManager CD-ROM. Chapter 8 Installing AppManager agents 145

148 Depending on the combination of managed objects you select, the order in which you see dialog boxes may change. Also, if more than one managed object requires the same information, you ll be prompted only once to provide the information. Note Most systems and applications don t require any special configuration before or after installation. However, we recommend you check the AppManager CD-ROM appmanager\documentation\supplements folder and the NetIQ Support web site before making AppManager widely available. Completing the installation Using the information you have specified, the setup program checks for previously installed AppManager services and then performs a number of automated tasks. During this period, Setup: Creates and configures the local repository. Registers and configures the AppManager agent services. Installs the default NT managed object and any other managed objects you ve selected. Discovers system resources if communication with the management server is successful. Stores any application- or system-specific information in the repository, if required (for example, SNMP community strings or sa passwords). Once the AppManager agent is successfully installed, you are prompted to complete setup. 1 If prompted with the reminder that AppManager requires disk performance counters to be started, click OK. 2 When setup is complete, click OK. 146 Installation Guide

149 Installing agents from a centralized location Once you have installed the AppManager repository, management server, and at least one Operator Console in your environment, you can install the AppManager agent on a Windows computer or group of computers by running the AMAdmin_AgentInstall Knowledge Script from the AppManager Operator Console or Operator Web Console. In a typical environment, the AppManager agent component is installed on many more computers than the other AppManager components. For example, in a large organization you may need to monitor hundreds or thousands of managed client computers. You may also need to monitor managed client computers in remote locations. The AMAdmin_AgentInstall Knowledge Script simplifies this process by allowing you to configure installation jobs for individual or groups of computers and schedule when the jobs should run. Because configuring the job can be a daunting task at first, this Knowledge Script provides a Wizard option to step through the configuration options. This Wizard configuration process is the one described in this guide. If you are an experienced AppManager user and don t want to step through the parameters using the Wizard, see the Knowledge Script Reference Guide or the online help for the AMAdmin_AgentInstall Knowledge Script. How the AgentInstall Knowledge Script works The AgentInstall Knowledge Script differs from most Knowledge Scripts in that it is run by the AppManager agent that resides on the AppManager management server. Setup automatically installs an agent on the management server, even if you don t select it when you install the management server, to enable remote installation and other tasks. When you run the script, the AppManager agent on the management server: Chapter 8 Installing AppManager agents 147

150 Creates a temporary directory and a Windows service named NQEXECD on each managed client. NQEXECD then distributes the files from the AppManager installation directory to the temporary directory on the managed client. Performs and monitors the installation of each remote AppManager agent. Creates an event and flashes an indicator next to the managed client s name in the TreeView pane of the Operator Console if the installation isn t successful. Deletes the temporary directory and the files in it, and removes the NQEXECD service on each managed client when the installation is completed. The agent services (NetIQmc and NetIQccm) that reside on the management server must be configured with a valid Windows login account that has Domain Admin privileges for the domain associated with the target managed clients. Each managed client must have a valid Windows login account configured with Administrator privileges with permission to copy files from the AppManager release distribution directory. 148 Installation Guide

151 Preparing your environment Before you run the AgentInstall Knowledge Script, you need to prepare your environment. The following requirements must be met: Requirements The AppManager repository, management server, console, and agent must already be installed in your environment. The AppManager agent must be installed on the same server where the AppManager management server resides. (The setup program automatically installs an agent on the management server.) Select one management server to be used for remote installation jobs. For all other management servers, manually set the Allow Agent Install registry key to 0. The key is located in the HKEY_LOCAL_MACHINE registry under: \Software\NetIQ\AppManager\4.0\NetIQms\Config Check the availability of TCP ports. On the computer where the management server resides: port 9999 On the computer where the agent resides: ports 9998 and 9979 (port 9979 allows the agent on the management server to communicate with the NQEXECD service on the managed client computer) If these ports are being used by another application, you will need to identify the proper ports to use. Configure the AppManager agent services (NetIQmc and NetIQccm) onthe AppManager management server to run as a valid Windows account with Domain Admins privileges. By default, the services run under the LocalSystem account that doesn't have the proper privileges to run the AgentInstall Knowledge Script. (After you run the Knowledge Script, you can change the Windows login account for the agent services back to the LocalSystem account.) You can use Services Control Panel to stop, change the Log On properties, and restart the services. See your Windows documentation for more information about changing login account for each service. Chapter 8 Installing AppManager agents 149

152 Requirements Check that the service account for the AppManager agent on the management server has permission to access all of the remote computers on which you are attempting to install. Make sure the domain of the management server is the same as that of all the managed clients. If the domain is not the same, or if the managed clients belong to more than one domain, then set the management server domain to be trusted by the different managed client domains. (A trust relationship allows a user to access resources on the entire network using a single user account and password.) Verify each managed client has a valid Windows login account configured with Administrator privileges that you can use for the installation. Verify the directory that holds the AppManager installation files (for example, the appmanager\setup directory on the AppManager CD-ROM or a shared directory available over a network) is shared and accessible to the managed client. The directory must conform to UNC (Universal Naming Convention) format as a shared directory or network drive. For example, \\mis\appmgr\ or \\mis\d$. The directory must be readable to the service account (a Windows login account) for the AppManager agent on the managed client. Note Keep in mind that the managed client needs permission to access the distribution computer and that AgentInstall copies all of the files in the installation directory to the managed client. Verify the computer on which you are about to install the AppManager agent passes the requirements for the systems and applications you want to monitor. You can run the AMAdmin_AgentPreInstall Knowledge Script to verify requirements on remote computers. For more information, see the Knowledge Script Reference Guide or online help. Planning the configuration of AgentInstall jobs You must run a separate instance of the AgentInstall Knowledge Script if you want to set different Knowledge Script properties for a computer or a group of computers. To take advantage of centralized-installation, create server groups when you plan to install the AppManager agent with the same set of managed objects and properties on more than one managed client. For example, create a server group for managed clients on which you plan to manage SQL; create another server group if you plan to 150 Installation Guide

153 manage SQL but with different properties, such as a different sa password and netiq password; and yet another if you plan to manage SQL and IIS. Keep in mind that: When installing the AppManager agent on more than one computer to enable MAPI mail or monitor SMS or SQL, each computer must share the same Exchange, SMS, or SQL specific configuration names or parameters. For example, the computers must share the same SQL login account or the same Exchange Server or mailbox alias. If the configuration names or parameters differ on any computers, then run separate instances of the AgentInstall Knowledge Script on those systems. If you set Allow setup to create mailbox to No in the Knowledge Script properties, then you must run a separate instance of the AgentInstall Knowledge Script for each Exchange Server that you plan to monitor since you must enter different mailbox aliases and profile names for each Exchange Server. If you don t want to disturb your production environment while you install the AppManager agents (for example, you don t want to change any domain trust relationships), you can set up a different AppManager management server, repository, and agent for running the AgentInstall Knowledge Script (using the same example, on a computer in the same domain as the computers on which you want to install the agent). After the agents are installed, your production environment can resume managing the agents. It s not necessary to stop any running jobs in your production environment. If you run the AgentInstall Knowledge Script on a managed client that already has the AppManager agent installed on it, then the agent is re-installed and any properties and the agent software from the previous installation will be replaced by this installation. If you have more than one management server in your environment, you need to select one to handle all Chapter 8 Installing AppManager agents 151

154 installation-related jobs. For all other management servers, set the NetIQms\Config\Allow Agent Install registry key to 0 to prevent them from attempting to start installation jobs. Keep in mind, however, that you should always approach editing the registry with caution. For more information about working with multiple management servers, see the Administrator Guide. If you run the AgentInstall Knowledge Script on the Master directory in the TreeView pane, the AppManager agent will be installed (or re-installed if previously installed) on all managed clients in the Master directory, but won t be re-installed on the server where the AppManager management server resides. (To install the agent on the server where the management server resides, run the AppManager setup program.) Running the AgentInstall Knowledge Script 1 Open the AppManager Operator Console. 2 Be sure the TreeView and Knowledge Script panes are open (a check mark should be by TreeView Pane and KS Pane on the View menu). 3 If the computer on which you want to install the AppManager agent isn t in the TreeView pane, then click TreeView > Add Computer. For more information on adding computers, see the User Guide. 4 In the Knowledge Script pane, click the AMADMIN tab. 5 Drag the AgentInstall Knowledge Script to the computers or computer groups in the TreeView pane on which you want to install AppManager agent. 152 Installation Guide

155 6 At the Properties for KS AMADMIN_AgentInstall dialog box, on the Schedule tab, set the schedule to run once (the default). 7 Click the Values tab, then click Wizard. Setting the configuration for the job using the Wizard 1 Set the event notification and severity for the successful completion of the AgentInstall job and type the name, password, and domain for the Windows login account to use on the remote managed client, then click Next. Description Raise event when complete? How to set it The default setting Yes generates an event indicating the successful completion of the installation job. Uncheck this option if you don t want job completion to generate an event. Note If the installation fails for any reason, an event is always generated, even if you uncheck this option. Event severity for successful completion If you are generating an event for the successful completion of the installation, set the event severity level. The default severity for a successful installation is 20 (yellow event indicator). Note If the installation fails for any reason, a severity 5 event is raised (red event indicator). Chapter 8 Installing AppManager agents 153

156 Description User for temporary service on target Password for temporary service on target How to set it Type the Windows login account name on the managed clients which will be used to install the agent. This is the user account running the NQEXECD service on the remote computers. The default is netiq. Note The Windows login account must have permission to transfer files from the AppManager distribution directory to the temporary directory on the managed clients. You can either use the Administrator account or an account with Administrator privileges. Type the password for the Windows login account running the NQEXECD service on the target computers. The default is netiq. Domain for temporary service on target Type the name of the domain for the Windows login running the NQEXECD service on the target computers. Note Remember that the Windows login account must have permission to transfer files from the AppManager distribution directory domain to the temporary directory on the managed client. The domain should be the same as the domain of the management server or a domain that trusts the management server domain. 154 Installation Guide

157 2 Type the path of the distribution directory for AppManager components and target directory information, then click Next. Description UNC path to the installation file How to set it Type the directory where the AppManager distribution files are located. For example, \\mis\appmgr\ or \\mis\appmanager\setup. The distribution directory must: Be shared and accessible to the managed client Be readable to the Windows login account you specified as the User for remote install. Conform to UNC (Universal Naming Convention) format as a shared directory or network drive. For example, \\mis\appmgr\ or \\mis\d$\ The distribution directory can be on the CD-ROM or available over a network. Tip If the agent on the management server cannot access the shared folder where you have placed the installation files, the AgentInstall job will fail with an error indicating an invalid distribution directory. If you see this error, try copying or mapping the folder to the management server computer then re-running the job. Chapter 8 Installing AppManager agents 155

158 Description Temporary directory on target machine Install path on target machine Local repository path on target machine How to set it Type the name of a temporary directory on the target computer. The AppManager files are copied from the release distribution directory to the temporary directory on the managed client. After installation, the files and temporary directory are deleted. You can use the System Variable TEMP (%temp%) to locate a directory on the target computer if this System Variable is set in your environment. For example, %temp%\agtinst. Type the name of the directory on the managed clients where you plan to install the AppManager agent. You can use the System Variable ProgramFiles (%programfiles%) to locate a directory on the target computer if this System Variable is set in your environment. For example: %programfiles%\netiq\appmanager. Type the path to the local AppManager repository on the managed clients. You can use the System Variable ProgramFiles (%programfiles%) to locate a directory on the target computer if this System Variable is set in your environment. For example: %programfiles%\netiq\appmanager\db. Tip In most cases, you will want to establish a distribution computer that has all of the AppManager folders and files similar to the CD-ROM layout. You then use the AppManager directory on that computer as the distribution directory. You may want to consider bandwidth and your network configuration in selecting a distribution computer. For example, you may want to set up a distribution directory on a computer in a localized network for more efficient communication between the managed clients and the distribution computer. Keep in mind that the managed client needs permission to access the distribution computer and that AgentInstall copies all of the files from the distribution directory to the managed client. Make sure the distribution directory contains only the AppManager distribution files. 156 Installation Guide

159 3 Type the name of a management server to connect to, set the security level, and list any other management servers authorized to communicate with the managed client, if applicable, then click Next. Description Management server name Port number the management server uses Port number managed clients use How to set it Type the name of the management server to connect to to attempt automatic discovery and other setup tasks. The management server for the managed client can be different from the one used to run this Knowledge Script. If this management server is running, it will update its repository based on the information you enter and run an automatic discovery job for each remote computer. Note If you plan to use Standard security and want to specify a list of management servers (with the List of authorized management servers parameter), be sure that the authorization list includes the management server you enter for this parameter. Type the port number the management server uses to communicate with managed clients. For more information, see Configure the ports to use on page 140. Type the port number the managed clients use to communicate with the management server. For more information, see Configure the ports to use on page 140. Chapter 8 Installing AppManager agents 157

160 Description Select security level Maximum security password How to set it Click the selection arrow to choose a security level. Select Maximum security to encrypt all communication between the managed client and management server. (To prevent communication problems, only advanced users should select Maximum security.) Select Standard security to authorize the specific management servers that are allowed to communicate with this managed client. For more information, see Configure the level of security on page 137. If you selected Maximum security, type the password you specified when you created the key file. If you selected Standard security, leave this field blank. For more information, see Configure the level of security on page 137. Maximum security key file List of authorized management servers If you selected Maximum security, type the full path to the key file. For example, if the file is in the D:\RPCsecure folder on the target computer, the path might look similar to this: D:\RPCsecure\sitekey.txt To specify some other computer in the environment rather than the target computer, type the UNC path to the file. For example, for the E:\Temp folder on the computer zebra: \\zebra\e$\temp\sitekey.key If you selected Standard security, leave this field blank. For more information, see Configure the level of security on page 137. If you selected Standard security, type the names of the management servers, separated by commas, that are authorized to access and manage this computer. For example: AJAX,ATHENA,MARS The default (*) allows all management servers to manage this computer. Note If you want to specify a list of management servers, be sure that the list includes the management server available for performing discovery. 158 Installation Guide

161 4 Set any of the optional agent configuration options, then click Next. Description Run agent service on target computer as a Windows account Enable MAPI mail as an action How to set it Set to Yes to use a specific Windows login account as the NetIQmc service startup user. When you leave this option unchecked, the agent service runs as the LocalSystem account. If you check this option, you need to specify a domain, user name, and password for the Windows account you want to use. For more information, see Specify an account for the service to use on page 133. Set to Yes to set up an Exchange profile and mailbox so you can send MAPI mail as an action. If you check this option, you need to: Specify a domain, user name, and password for the Windows login account you want to use for setting up the profile. Enter the name of the Exchange Server to use, and the profile name and mailbox alias name you want to create. Check the Run agent service on target computer as a Windows account option, if you have not already done so. For more information, see Enabling MAPI mail on page 135. Chapter 8 Installing AppManager agents 159

162 Description Install Report Agent Automatically run discovery script? How to set it Set to Yes to install optional components that allow the target computer to execute the report scripts for configuring and creating reports. If you check this option, you need to: Specify a domain, user name, and password for the Windows login account you want to use for setting up the profile. Check the Run agent service on target computer as a Windows account option, if you have not already done so. Set to Yes to attempt to perform an automatic discovery for the target computer. Set to n if you want to run the discovery manually after installation, for example, because you want to configure the discovery parameters. 5 Check to select the systems and applications you want to monitor, then click Next to continue making selections (the list of systems and applications extends beyond one page). For example: For some managed objects, all you need to do is check Yes. No further configuration is necessary. For other managed objects, you need to provide additional information. For example, if you select Install CIM managed object, you are prompted to type the SNMP community name for the target computer(s). For a summary 160 Installation Guide

163 of the additional information you may need to provide, see Configure information for managed objects on page 141. If prompted for additional information, follow the instructions displayed on the page, then click Next. If you need a more detailed explanation than displayed on any page, press F1. 6 When you are finished configuring the parameters, click Finished. 7 On the Actions tab, set an action if you want to be notified when either the installation is complete (assuming you kept the default setting of y for Raise event when complete) or the installation fails. 8 Click OK to run the Knowledge Script. One job for each managed client on which the AgentInstall Knowledge Script is run appears in the Job pane. For more information about monitoring and controlling jobs, see the User Guide. For more information about the AgentInstall Knowledge Script, see the Knowledge Script Reference Guide or online help. Configuring agents for working in a cluster The AppManager agent does not run as a virtual application; therefore, it must be installed on the local (not shared) disk of each node in a cluster. For some applications, such as Microsoft Exchange Server, Microsoft SQL Server, and Oracle RDBMS, you can run application-specific Knowledge Scripts on the physical nodes that make up the cluster to monitor the virtual server. For these applications, monitoring is handled through the application-specific managed object, such as the Exchange managed object or the SQL Server managed object. For cluster resources that aren t linked to a particular application, monitoring is handled through the Microsoft Cluster Server managed object and MSCS Knowledge Scripts. Chapter 8 Installing AppManager agents 161

164 Not all Windows server applications are cluster-enabled, however. In general, you can use AppManager to monitor Microsoft Exchange Server, Microsoft Exchange 2000, Microsoft SQL Server, and Oracle RDBMS running as virtual servers in a cluster and cluster resources through the Microsoft Cluster Service and NT managed objects. Besides installing the agent on each node in the cluster, it s recommended that you install the same set of managed objects on each node of the cluster to ensure that there is no interruption of monitoring functions in case there is a failover of the node where the AppManager management server resides. Installing on an active cluster node Before you install the AppManager agent and the application-specific or Microsoft Cluster Service managed object, check that the virtual server is active on the cluster node on which you are installing. Typically, discovery of the virtual server can only take place when the virtual server is active on the computer where you are installing. It s recommended that you move the active virtual server to each node before installing the managed object. Alternatively, you can install on an inactive node and uncheck the Perform Discovery option. After installation, you can then move the virtual server to the appropriate node and run the discovery script manually. To install the agent and appropriate managed object on each cluster node, follow the instructions in this chapter. Note Be sure you have a Windows domain, account name, and password for the agent to use. The agent on each node of a cluster must run as a Windows login account (not the LocalSystem account). For more information about designating a specific user account for the AppManager agent to use, see Specify an account for the service to use on page 133. Depending on the managed objects you select, you may need to provide additional information. For example: 162 Installation Guide

165 If you are running the setup program and installing the Microsoft SQL Server managed object, type the SQL Server sa password for each SQL Server (virtual and local) in the cluster. If you are running the setup program and installing the Microsoft Exchange 2000 managed object, type the account information for the monitoring service accounts that will run on each node of the cluster. If you are running the setup program and installing the Oracle RDBMS managed object, type the user name and password for discovering each database on the server. If you are installing the agent remotely or are unable to enter the information prompted for during setup, use the AppManager Security Manager to update the AppManager repository with the information after installation. For information about using the Security Manager, see the User Guide. For additional application-specific information, see the documentation in the appmanager\documentation\supplements folder on the AppManager Suite installation CD-ROM Monitoring clustered resources After installing the agent and managed objects, you can run a combination of application-specific, MSCS, and NT Knowledge Scripts to monitor a virtual server. Before you can monitor the virtual server, however, you need to run the AMAdmin_SetResDependency Knowledge Script to identify the shared logical drive where the virtual application resides, or define the services that must be active when a virtual application is running on a target physical node. To establish the resource dependency, run the AMAdmin_SetResDependency Knowledge Script on all physical Chapter 8 Installing AppManager agents 163

166 nodes in the cluster. In the Properties dialog box, click the Values tab then set the following parameters as appropriate: For Knowledge Script category Required available resources Required active services Do this Specify the Knowledge Script category that you want dependent on the resource you specify. This may be an existing Knowledge Script category, such as Exchange, SQL, ororacle, or it may be a custom Knowledge Script category that you create specifically for cluster monitoring, for example, Cluster. This setting identifies which jobs should only run when the specified resource is owned by the current node. Otherwise, the job is inactive. For example, if you drop this Knowledge Script on the computer BAJA and specify the SQL job category and the dependency as the M: drive, the jobs you have created for the SQL category will only run on the computer BAJA when it is the active node that owns the M: drive. Type the name of the shared logical disk where the virtual server resides. For example, G: You can specify a shared logical drive if it is the primary resource the cluster depends upon. If the cluster has multiple shared drives, you may want to base the resource dependency on an active service. Type the name of a service that must be available on the local node when it is the active node. For example, MSExchangeIS or MSSQLServer$virtualserver. Keep in mind that in specifying a resource dependency, you should identify a single resource, whether it is a physical drive or a service name, within the Cluster Group. For more information about this Knowledge Script, see the Knowledge Script Reference Guide, or select the script in the Knowledge Script pane and press F1. For additional application-specific information, see the documentation in the appmanager\documentation\supplements folder on the AppManager Suite installation CD-ROM. 164 Installation Guide

167 Communicating with a clustered management server To be sure all of the managed clients in the cluster are properly monitored by the AppManager management server, run the AMAdmin_ConfigSiteCommType Knowledge Script on each cluster node and set the Communication via IP address parameter to n. The AppManager agent on the managed client will then communicate with the clustered management server using the network name, not the IP address. For more information about this Knowledge Script, see the Knowledge Script Reference Guide, or select the script in the Knowledge Script pane and press F1. Monitoring other applications on a cluster Not all Windows Server applications that have been installed on MSCS are cluster-enabled. For example, you can install Microsoft Proxy Server on MSCS; however, Proxy Server is not cluster-enabled. Currently: Only a few cluster-enabled applications running as virtual servers on a cluster can be monitored through AppManager. With the Microsoft Cluster Server managed object, the agent can monitor any virtual server on the cluster. For all other managed objects, the agent monitors the application only on the local node. Chapter 8 Installing AppManager agents 165

168 Installing agents on UNIX computers The NetIQ UNIX agent is a daemon that you install on each of the UNIX servers you want to manage through AppManager. An installation script guides you through the steps for installing and starting the agent. Note Running the installation script requires root user permission. To install the UNIX agent: 1 Insert the NetIQ UNIX Components CD-ROM into a CD drive. 2 Mount the CD-ROM, if necessary. Depending on your platform, the CD may be mounted automatically or you may need to use the mount command. If the CD-ROM is not accessed automatically, follow the procedures appropriate for your operating environment. 3 Switch to the root user account. For example: % su root # 4 Run the netiq_agent_install command to start the installation. This script checks your current environment to see if it meets system requirements and asks you for information about where you want to install product files and the computer you are using as the management server. Default responses are displayed in brackets ([ ]). Press Enter or Return to accept the default, or type new information then press Enter or Return. Note If the installation script detects that your system does not meet any system requirement, it will display the change you need to make and exit the installation. If the installation script detects your system does not match a recommended configuration, it records information about your current configuration and any updates you may need to make in a log file, displays the location of the log file, and continues with the installation. After you complete the installation you should review the information in the log file to determine whether you need to perform any additional action. 166 Installation Guide

169 To start the installation, change to the appropriate mount point or directory. For example, if you are installing on Sun Solaris from the /cdrom drive: # cd /cdrom # cd UNIX./netiq_agent_install Follow the instructions displayed on the screen. The following table provides a summary of the information you are asked to provide: When you are asked for Host name or IP address for the NetIQ AppManager Management Service NetIQ AppManager Management Service listening port You need to provide The host name, fully-qualified domain name, or IP address for the computer where the management service, NetIQms, is installed. There is no default. The listening port set on the management server computer. The default is port If you change the default port on the Windows computer that hosts the management server, be sure to provide the correct port number for all of your UNIX servers that need to communicate with the management server. For information about changing the default listening port, see the Monitoring UNIX Servers with AppManager Work Smarter Guide. Chapter 8 Installing AppManager agents 167

170 When you are asked for Machinenametobe displayed in the Operator Console TreeView Destination directory User name that runs the agent You need to provide The name you want displayed for this computer in the Operator Console TreeView. You can specify the name using: Host name for the computer, for example, ajax or ajax.redrock.local. IP address for the computer, for example, You should specify the fully qualified domain name for the computer to ensure the management server will be able to resolve the name or IP address you specify. The management server must be able to resolve the name for discovery to succeed. If necessary, you can run the nslookup command to determine the full name of the UNIX computer. Note If you are monitoring a computer with more than one network interface card and therefore more than one host name or IP address, use getlocalhost to determine the name you should use for the TreeView. Normally, the default host name or IP address returned is the one the management server can resolve. The absolute path to the directory where you want product files installed. The default is /opt/netiq or /usr/netiq. The installation directory UnixAgent will be installed in the location you specify. A user name that you want to use for running the NetIQ UNIX agent. In most cases, the user account does not require any special privileges. However, retrieving information from some performance counters or in certain environments may require the UNIX agent to run as root or may require root environment variables to be defined. For example, the UNIX agent may require /sbin and /usr/sbin in the $PATH environment variable to perform certain tasks. Note You need to log in as this user to start the UNIX agent. 168 Installation Guide

171 The installation script extracts all of the necessary files from the CD-ROM, and creates the configuration file and the startup script nqmdaemon for the NetIQ UNIX agent. You are then prompted to install any applicable AppManager application management modules for monitoring UNIX applications. 5 Select the modules you are interested in monitoring as they are displayed and follow the instructions displayed on the screen to complete the installation. Note Some AppManager modules for monitoring UNIX applications require user names and passwords or other secure information to run certain Knowledge Scripts. During installation, you are prompted to provide this information if it is required for a module you select. After installation, you can use the AppManager Security Manager to update this information, if needed. The Security Manager stores the information in the AppManager repository so it is available for the Knowledge Script jobs that need it. For a list of the AppManager modules that require you to enter information using the Security Manager, see the Using the Security Manager to update information on page Choose whether you want to automatically start the UNIX agent and attempt to perform the discovery or manually start the UNIX agent and manually run the Discovery_UNIX Knowledge Script. Note The management server must be available and able to resolve the network host name or IP address you specified for the computer for discovery to succeed. If automatic discovery fails, the management server records an event in the Application log. You can use the AMAdmin_MSHealth Knowledge Script to check for these events and raise AppManager events in the Operator Console if they occur (you can filter the event log entries using the search string autodiscovery for the Unix machine). 7 When the installation is complete, exit root and unmount the CD-ROM drive. Chapter 8 Installing AppManager agents 169

172 After you install the UNIX agent on your server, the UNIX agent daemon nqmagt is added to the startup profile on your server and will be automatically started or stopped when you restart or shut down the UNIX system. You can manually start the process at any time by running the nqmdaemon start command. The path for running this command can vary, depending on the UNIX platform and information you entered during installation. The complete path for the current platform is always displayed at the end of the NetIQ UNIX agent installation. You should make note of the path when you install the agent for future reference. Note To start the UNIX agent, you need to be logged in as the user you specified during installation before issuing the nqmdaemon start command.

173 Chapter 9 Installing the Web management server The AppManager Web management server allows you to view your managed computers, monitor event status, and start and stop jobs using the Operator Web Console and Microsoft Internet Explorer. This chapter describes the steps for installing the AppManager Web management server and configuring Web service security. Starting the AppManager setup program Using a valid Windows login account with either local or domain Administrator privileges: 1 Insert the AppManager CD-ROM into a CD drive and start the Setup program. For more information about starting Setup, see Chapter 4, Starting installation. 2 At the Welcome dialog box, click Next. 3 Click Install Products, then click Next. 4 Select the folder where you plan to install AppManager, then click Next. If installing multiple AppManager components on a computer, install them all in the same location. For example, D:\Program Files\NetIQ. 171

174 Select the web management server 1 Select the AppManager console and any other components you want to install, then click Next. 2 When prompted to stop and restart the IIS Admin service, click Yes. Complete the installation Using the information you have specified, the setup program checks for previously installed AppManager services and then performs a number of automated tasks. During this period, Setup: Copies the Active Server Pages and HTML pages for the Operator Web Console and online help to the selected location. Restarts the IIS Admin service. Appends the \NetIQ\AppManager\bin folder (for example, c:\program Files\NetIQ\AppManager\bin) to your system path. Once the Web management server is successfully installed, you are prompted to complete setup. Click OK. 172 Installation Guide

175 Configuring Web service security After you install the AppManager web management server, you need to configure the security for the Web server to authenticate the users who will be logging on to the AppManager repository using the Operator Web Console. The user account for the Web server must be a valid user account for the SQL Server where the AppManager repository resides. 1 Start Internet Services Manager in Microsoft Management Console (MMC). (Internet Services Manager is an MMC snap-in.) Either: Start MMC. Open a console that contains the Internet Services Manager snap-in or add the snap-in to the existing console. Click the Start button, and then Programs > Administration Tools > Internet Services Manager. 2 In the MMC Console Tree pane, double-click Internet Information Services. 3 Double-click the name of the Web server on which you installed the AppManager Web management server. 4 Double-click the Web site (for example, Default Web Site). 5 Right-click the NetIQ node and then click Properties. Chapter 9 Installing the Web management server 173

176 6 Click the Directory Security tab. 7 Click Edit for the option to enable anonymous access and edit the authentication methods. 8 At the Authentication Methods dialog box, set the following options, then click OK: For Allow Anonymous Access Basic Authentication Integrated Windows Authentication Do this Deselect. Select. This option transmits passwords over the network without encrypting them. When prompted, click Yes to continue. To specify a domain name other than the local one, click Edit, type a domain name, and then click OK. Select. 9 To implement the changes, click Apply. 174 Installation Guide

177 Accessing charts from the Operator Web Console After you install the AppManager Web management server component, you can use a Web browser to access the Web management server. When you use your Web browser to access the Web management server, the browser becomes your Operator Web Console. You can then use the Operator Web Console to start and stop jobs, view and respond to events, and perform other AppManager tasks. However, if you want to use the Operator Web Console to generate and view charts, you need to download and install the AppManager Version Checker program. The AppManager Version Checker program verifies that the correct version of the AppManager chart component is installed. To install the AppManager chart component in the Operator Web Console: 1 Start the Operator Web Console and log in to an AppManager repository. 2 Click Charts in the Navigation bar. 3 When prompted, download and install the AppManager Version Checker program by clicking the Chart Component hyperlink and either: Click Open on Internet Explorer 6, or Run this program from its current location on Internet Explorer 5.x. Once the chart component installation completes, click Charts in the Navigation bar to view charts. For more information, see the User Guide. Chapter 9 Installing the Web management server 175

178

179 Chapter 10 Configuring access after installing After you install AppManager, you need to identify the user logins that are allowed to view resources, start jobs, respond to events, and perform other tasks. You may also need to configure or update application-specific information before you can begin monitoring your environment. This chapter describes the final configuration steps to prepare AppManager for general use. The following topics are covered: Granting users access to AppManager Configuration for monitoring hardware Configuration for sending MAPI mail as an action Using the Security Manager to update information Working with AppManager connectors Although this chapter covers the basic configuration steps that are most common, some applications require additional pre- or postinstallation configuration. Detailed application-specific configuration information may be provided in NetIQ Work Smarter Guides or supplemental documentation. For example, if you are installing AppManager to monitor SAP R/3 systems or Oracle, you should consult the supplemental documentation available for those applications in the appmanager\documentation\supplements folder on your AppManager CD-ROM. Work Smarter guides are in PDF format and can be found on the NetIQ Support site. To access this site, you must be a registered AppManager user. You may want to occasionally check the NetIQ Support site for updated guides. 177

180 Granting users access to AppManager To start most AppManager console programs (the Operator Console, Operator Console MMC Snap-In, Operator Web Console, Security Manager, Distributed Event Console, Repository Browser, License Manager, and command line scripts), you must log on to the AppManager repository with a SQL Server login account that has permission to access AppManager. The default SQL Server login account for the AppManager repository is the SQL Server sa login account. If you are using this account, and you are running SQL Server in Mixed security mode, you ll be able to start the AppManager programs. If, however, you ll be using a different SQL Server login account (this will be the case in most organizations), or if you are running SQL Server in Windows Authentication security mode (whether using the sa or a different account), you must first use the AppManager Security Manager to grant access to AppManager to the SQL Server login account you are going to use. Create the default roles To use the Security Manager for the first time, you must have System Administrator (sa) privileges. After you begin granting access to other SQL Server login accounts, you can use an account that is a member of the admin group for the AppManager repository database. 178 Installation Guide

181 1 From the Windows desktop, click the Start button and select the Programs folder, then click NetIQ > AppManager > Tools & Utilities > Security Manager. 2 At the Security Manager Logon dialog box, log on to the AppManager repository as the SQL Server sa login account. For Server Repository Login name Password Do this Type the name of the Windows server where the AppManager repository you want to work with is installed. After you enter the name, the repositories available on that server are displayed in the Repository list. Select the database name for the AppManager repository you want to work with. The default repository name for AppManager is QDB. Note Once you have logged into the Security Manager, you can switch to another repository. Type sa, for the SQL Server sa login account. Note If you re running SQL Server in Windows Authentication mode, you won t see this option. Type the password for the SQL Server sa login account. Note If you re running SQL Server in Windows Authentication mode, you won t see this option. 3 Click Logon. When the Security Manager starts, three pre-defined security roles Administrator, Standard User and Read-Only User are created for you. You can use them as is or modify their security profiles. Later, you can create as many additional custom roles as your needs dictate. For example, you may want to create AppManager roles for AppManager Administrators and ReportOnly Users. For information about creating roles and defining rights, see the Security Manager online help or the Administrator Guide. Chapter 10 Configuring access after installing 179

182 Set the default role to Standard User 1 In the Security Manager s left pane, click AppManager Roles. Security pane Set the default role to Standard User 2 In the AppManager Roles tab, select Standard User from the Default role list. The default role is applied to every new AppManager user you create. To get started, you probably want to create Standard Users with specific access rights and then change roles for individual users for special cases such as administrators. Before adding users, you may also want to review the default rights for the Standard User and make any necessary changes to the role. To do this, select the Standard User in the left pane, then click 180 Installation Guide

183 through the tabs that describe the rights for this role in the right pane. Click to define security roles for AppManager users Click to assign roles to AppManager users Note For more information about setting rights and exceptions for AppManager roles and individual users, see the Administrator Guide for AppManager. Add SQL Server logins as AppManager users 1 In the Security Manager s left pane, right-click AppManager Users, then click User Setup. Chapter 10 Configuring access after installing 181

184 2 In the AppManager User Setup dialog box: Select SQL Server users to add as AppManager users, then click Add When you select SQL Server users, corresponding login accounts are displayed If the SQL user Exists Does not exist Do this In the SQL users list, select dbo and any other SQL users you want. (To select multiple users, press the Ctrl or Shift keys as you make your selections.) Then click Add, to add the users to the AppManager users list. Click New SQL User. AttheNewSQLUserdialogbox,typeaSQLusername and password, and select a group. Then click OK. In the AppManager User Setup dialog box, select the SQL user in the SQL users list and then click Add. Note You can only add users if you log on to the Security Manager using the SQL Server sa login account and SQL Server is running in Mixed security mode. If you are using Windows Authentication security, you must create a Windows account outside of AppManager. See your Microsoft SQL Server documentation for information on adding a Windows account to SQL Server, then use Security Manager to add the SQL user to the AppManager users list. Note For more information about adding AppManager users, creating SQL users, and defining security profiles, see the Administrator Guide for AppManager. 182 Installation Guide

185 3 When you re finished adding users, click OK. 4 Exit Security Manager. You can now start AppManager programs using the SQL Server login accounts that you defined as AppManager users. Configuration for monitoring hardware AppManager monitors hardware statistics through integration with SNMP-based agents on the managed clients. If you are monitoring any products in the Hardware category, check that the SNMP service is installed and started and that you have registered the SNMP community name for the server when you installed the managed object on the computer. Keep in mind that the community name string is case-sensitive. The products included in the Hardware category include: Compaq Insight Manager Dell OpenManage HP TopTools for Servers IBM Netfinity Manager or Director Siemens ServerView If the community name has been entered incorrectly or changed after installation, use the AppManager Security Manager to update it. For more information, see Using the Security Manager to update information on page 192. Note that the Security Manager doesn t change the actual SNMP community string or verify the information you enter. It only updates the information in the AppManager repository. Chapter 10 Configuring access after installing 183

186 Checking the SNMP service In some environments, the SNMP service may not be installed by default or may be set to run manually. To check whether the service is installed and running: 1 Double-click Services in the Windows NT Control Panel or Windows 2000 Administrative Tools. 2 In the list of services, be sure SNMP is listed and started. If the SNMP service is not listed: Exit the Services program. Follow the SNMP installation instructions for your computer. Completing the installation requires restarting your computer and may require re-applying a Windows service pack. Start the SNMP service. 184 Installation Guide

187 3 In the list of services, be sure other appropriate services are listed and started. For Check these services Compaq Insight Manager CIM agent services for your version of CIM. Dell OpenManage Dell Baseboard Agent Win32sl Note The version of the Dell OpenManage agent software must correspond to a supported version of the Dell server BIOS. For more information, see the Dell Support Web page at support. HP TopTools for Servers IBM Netfinity Manager Siemens ServerView To verify that the HP NetServer SNMP Agents component (which is included on the HP NetServer Navigator CD-ROM) is installed and running: In the Windows Registry, go to this key: HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\SNMP\Parameters\ ExtensionAgents Look for this entry: #:REG_SZ:SOFTWARE\Hewlett_Packard\ NetSrvAsst\hpscdll\CurrentVersion Netfinity Support Program service. Siemens ServerView SNMP agent. 4 Exit the Services program. Checking SNMP security If SNMP security on the managed client computer is configured to accept SNMP packets from a specified host list, the managed client computer must be configured to accept its own SNMP packets. To check the SNMP security settings: 1 On the Windows desktop, right-click Network Neighborhood and then click Properties. 2 In the Network dialog box, click the Services tab. Right-click SNMP Service; then click Properties. Chapter 10 Configuring access after installing 185

188 3 In the Microsoft SNMP Properties dialog box, click the Security tab. 4 If Accept SNMP Packets from These Hosts is selected, make sure the name of the local computer is included in the list. If it s not in the list, click Add and type the local computer name or IP address. 5 Click OK and then click Close. If you added a host name, stop and then re-start the SNMP service for your changes to take effect. Using the Microsoft SNMP Utility The Microsoft Windows resource kit includes a utility for checking SNMP which can be useful for troubleshooting the installation of SNMP and hardware agents. This utility is called SNMPUTIL.EXE. With the SNMPUTIL.EXE, you can verify whether basic SNMP is installed and configured correctly by using a command such as: snmputil getnext servername communitystring 1 For example: Q:\>snmputil getnext zebra public 1 If SNMP is installed and configured properly, the utility should return information similar to this: SnmpTool - Simple Network Management Protocol Tool for Win32 ErrorStatus: 0 (No Error) ErrorIndex: 0 varbind 1: Name: system.sysdescr.0 OID: Type: OCTET STRING Length: 135 Value: Hardware: x86 Family 6 Model 5 Stepping 2 AT/ AT COMPATIBLE - Software: Windows NT Version 4.0 (Build Number: 1381 Uniprocessor Free ) 186 Installation Guide

189 If the utility returns an error, then reinstall or re-check SNMP configuration. You can also use the utility to verify the installation of the hardware agent by specifying the proper OID for the agent. For example, you can check for the CIM agent using the following command: snmputil get servername communitystring Check the documentation for your hardware vendor to determine the appropriate OID to specify in checking the hardware agent. Configuration for sending MAPI mail as an action To send MAPI as a recovery action by the AppManager agent service (NetIQmc) from a managed client, you must: Install Exchange Client (such as Microsoft Outlook) on the computer. Set up a Windows login account for the netiq_nt user. Set up an Exchange mailbox. Enter the Windows account information and Exchange Server, profile, and mailbox alias names during the installation of the AppManager agent. If the managed client is also an Exchange Server you plan to monitor, and you want to use the same Windows login account and Exchange mailbox for the Exchange managed object, see the Exchange Configuration Note in the appmanager\documentation\supplements folder or the Monitoring Exchange with AppManager Work Smarter Guide instead of following the instructions in this section. If you plan on using an existing Windows user account and an existing Exchange mailbox for sending MAPI action, you can skip steps 1 through 3 that follow. See Step 4: Install AppManager agent on page 192. Chapter 10 Configuring access after installing 187

190 Note If you are setting up your management server to send MAPI mail as an action and you are working in a cluster environment, you must use the same user account and Exchange profile information on each cluster node. Step 1: Install Exchange Client If the computer is not an Exchange Server or an Exchange Client, a MAPI client must be installed in order to set up the Exchange profile and mailbox alias for sending MAPI mail. See your Exchange documentation for installation instructions. Step 2: Create a user account The user account is required to create an Exchange profile and mailbox alias. In order to create a Windows user account, you must have Administrator privileges. As an example of the steps, the following describes creating a Windows NT user account. 1 Open Windows NT User Manager for Domains. 2 Click User > New User. 3 For Username, Password, and Confirm Password, type netiq_nt. 188 Installation Guide

191 You can use any name for this account. The NetIQmc service typically uses netiq_nt. The user account is unique in each Windows security domain. Note Both the NetIQmc and NetIQccm service must use the same account information. You are prompted to provide this information when you run the setup program or the AgentInstall Knowledge Script, and it is automatically applied for both services. If you change the service account after installation, however, be sure that you change the account information for both services. 4 Type a full name and description for the account. 5 Select Password Never Expires. Then click Groups. 6 In the Group Memberships dialog box, double-click Domain Admins in the Not member of list to add them to the Member of list. Then click OK. Note If the Windows account belongs to different domain and you don t want to add the account to the Domain Admins group for this domain, then add it to the Server Operator group. 7 Click Add. Then click Close. 8 To set the user permission, click Policies > User Rights. Grant To lists the users and groups that also have the selected right 9 Select Show Advanced User Rights. 10 For Right, select Log on as a Service from the list. Then click Add. Chapter 10 Configuring access after installing 189

192 11 In the Add Users and Groups dialog box, click Show Users. 12 In the Names list, select the netiq_nt user you created. 13 Click Add. Then click OK. 14 Repeat steps 8 through 10 to add the following right: Log on locally. 15 When you re finished, click OK. 16 Exit Windows NT User Manager for Domains. Step 3: Create an Exchange mailbox In order to create an Exchange mailbox, you must be an Exchange Administrator with the Permissions Admin role for the Recipient level. 1 Start Exchange Server Administrator. 2 To connect to the Exchange Server on which the managed client s Exchange service resides, click File > Connect to server. 3 Type the name of the computer on which the Exchange Server resides. Click OK. 4 Type a full name and description for the account. 5 In the tree view (container pane), select Recipients under the site. 190 Installation Guide

193 6 Click File > New Mailbox. 7 Enter a Display and Alias name for the mailbox. Note Once you enter the alias name for the mailbox, it s recommended that you not change it. If you do need to change the alias name, you can do one of two things: Delete the mailbox that you created in Step 6, create a new one with the alias name you want, and then re-run the setup program and enter the new name. Run the Exchange Administrator with the /raw parameter. Select the mailbox and then click File > Raw Properties. In the Object attributes list, click Obj-Dist-Name. In the Attribute Value box, the name that appears after the last equal sign (=) in the string is the mailbox alias name you first created (it is not the modified name). Enter this name during the AppManager setup program (do not enter the modified name). 8 Click Primary Windows NT Account. 9 Select the appropriate Windows NT user account. For example, netiq_nt. Chapter 10 Configuring access after installing 191

194 Step 4: Install AppManager agent Install the AppManager agent as described in Chapter 8, Installing AppManager agents. When prompted, enter the Windows account (for example, netiq_nt) and the Exchange mailbox alias name you created in the previous steps. Using the Security Manager to update information Some AppManager modules require user names, passwords, or other secure information to run certain Knowledge Scripts. Typically, you provide this information during the installation, for example when you are prompted to provide account information, profile and mailbox names, or SNMP community strings. In some cases, however, you may need to enter or update this information manually after completing the installation. Identifying modules that require secure information With this release, the following AppManager modules require secure information to run some or all Knowledge Scripts in the category: AppManager for Exchange and Exchange 2000 Server AppManager for Oracle RDBMS Server AppManager for SAP R/3 AppManager for Microsoft Systems Management Server AppManager for Compaq Insight Manager AppManager for Dell OpenManage AppManager for HP TopTools AppManager for IBM Netfinity Director AppManager for IBM Netfinity Manager AppManager for Siemens ServerView AppManager for BEA WebLogic Server 192 Installation Guide

195 If you are monitoring applications with any of these modules, you need to provide secure information such as user names and passwords either through the setup program when you install the module or manually through the Security Manager after installation. (Additional AppManager modules may be available by web download that require you to provide user names, passwords, or other information. See the documentation for the individual module for instructions.) Note If you did not enter secure information during installation, you must enter the information manually through the Security Manager after you have installed the agent and discovered the computer and its application resources. Entering secure information To enter or update secure information after installation, you must use the AppManager Security Manager. The Security Manager will store the information in the AppManager repository so it is available for the Knowledge Script jobs that need it. You can choose to install Security Manager when you install the AppManager console component. For more information, see Chapter 7, Installing console programs. Note To use the Security Manager, you must have System Administrator (sa) privileges or be a member of the admin group for the AppManager repository database. 1 Start the Security Manager by clicking the Start button and selecting the Programs folder, then click NetIQ > AppManager > Tools & Utilities > Security Manager (or by clicking Extensions > Security in the Operator Console). Chapter 10 Configuring access after installing 193

196 2 At the Logon dialog box, log onto the database you want to use. For Server Repository Login name Password Do this Type the name of the Windows server where the AppManager repository you want to work with is installed. After you enter the name, the repositories available on that server are displayed in the Repository list. Select the database name for the AppManager repository you want to work with. The default repository name for AppManager is QDB. Note Once you have logged into the Security Manager, you can switch to another repository. Type sa (for the SQL Server sa login account) or the name of a member of the admin group that has been granted access to AppManager. Note If you re running SQL Server with Windows Authentication security mode, you won t see this option. Type the password for the SQL Server login account. Note If you re running SQL Server with Windows Authentication security mode, you won t see this option. 3 Click Logon. 194 Installation Guide

197 4 In the Security pane, click the + (plus sign) next to Computers to display the list of discovered computers. Click this to store security information for discovered computers Note Secure information is stored on a computer-by-computer basis and the tabs available will change depending on whether the computer you have selected is a Windows computer or a UNIX computer. The tabs do not change to reflect the specific applications discovered on the computers in your network. For example, you always see the Oracle tab even if you have not discovered any Oracle RDBMS database servers. 5 Click the computer whose security information you want to update. 6 Click the tab that relates to the information you need to enter or change. If the computer you selected is a Windows computer: Click this DB2 Exchange To provide Instance names, user names, and passwords to log on to DB2 databases. Exchange profile names and mailbox alias names. Chapter 10 Configuring access after installing 195

198 Click this Exch2000 Oracle SAP SMS SNMP SQL WebLogic Custom To provide Exchange 2000 Server names, profile name and mailbox alias name. Oracle user names and passwords for Oracle databases. AppManager for SAP R/3 configuration names and SAP R/3 login information. The password for the SMS SQL Server sa login account. The SNMP community name for hardware monitoring with the following modules: Compaq Insight Manager Dell OpenManage HP TopTools for Servers IBM Netfinity Manager or IBM Director Siemens ServerView The SQL Server login accounts that are allowed to run SQL Knowledge Scripts on the selected computer. WebLogic Administrator user names and passwords. Secure information for new application management modules or for custom Knowledge Scripts. If the computer you selected is a UNIX computer: Click this DB2 Oracle TSM WebLogic Custom To provide Instance names, user names, and passwords to log on to DB2 databases. Oracle user names and passwords for Oracle databases. Instance names, user names, and passwords for Tivoli Storage Manager. WebLogic Administrator user names and passwords. Secure information for new application management modules or for custom Knowledge Scripts. 7 Enter or update the information for the current tab, then click Apply to save the change. Click Help for detailed information about how to enter information in each tab. 196 Installation Guide

199 8 Continue to click tabs and make the changes you want for each computer where you are monitoring an application that requires secure information. 9 To exit Security Manager, click Security > Exit. For more information about using the Security Manager, see the Security Manager online help or the Administrator Guide. Working with AppManager connectors Once you ve installed AppManager, you must run the AppManager connector setup program for any framework products with which you want to integrate. Each connector has its own setup program and documentation. In most cases, you run the setup program on the computer where the AppManager management server is installed. For specific information on how to install and use AppManager connectors, see the appropriate connector documentation. You can find the documentation for connectors on the AppManager CD-ROM in the corresponding appmanager\connectors\connector_name\documentation folder. For example, the documentation for the AppManager Connector for Tivoli Enterprise is in the folder: appmanager\connectors\tivoli\documentation Chapter 10 Configuring access after installing 197

200

201 Chapter 11 Staging the deployment Although it is useful to make thorough plans before you begin an implementation, the plan is really only an outline to what you need to do. Once you being installing components and using the product you will be constantly refining and clarifying your plans and expanding your management strategy. This is the natural evolution of an AppManager deployment. Because of this natural progression, we recommend you approach the implementation in a series of stages. This chapter provides an overview of the typical stages and describes the recommended deployment process. Installing in a lab environment Although it is not always necessary or practical to take the time to establish a test deployment, in many cases having the project team install AppManager in a lab environment can be instructive. Note In many organizations, this stage is actually part of the AppManager evaluation prior to purchase. Installing in a lab before any actual deployment can point out particularities of the organization that the project team may need to address to ensure a successful pilot. In addition, the test installation gives the project team experience in installing AppManager components and learning what to expect in the installation process. Therefore, NetIQ recommends that you install in a lab initially if it is at all possible to do so, especially if the project team has no previous experience installing AppManager components. 199

202 When you install AppManager in a test environment, you should focus on the following key goals: Uncovering potential conflicts between AppManager and other applications. If you uncover any problems, consult the AppManager Knowledge Base on the NetIQ web site for information about resolving the problem or for maintenance fixes that correct it, or contact NetIQ Support at for help. Quantifying the resource usage requirements of AppManager components before distribution. This allows you to test your assumptions in a safe but meaningful way, and verify the computers where you intend to install components during the actual deployment meet your requirements. Documenting network utilization between components. Although you are deploying in a test environment, if you set up a realistic sample of scripts and distribution of components, you ll be able to assess your bandwidth and latency assumptions. Testing the distribution of AppManager agents to ensure you have reliable account information and permissions (for example, usable passwords and domain account names). Preparing to install the pilot group Depending on your organization s size, the criticality of your monitoring needs, the expertise of your deployment team, and the resources available to you, the pilot deployment may involve a small representative number of computers or all of the servers you intend to monitor. The recommended practice is install on enough computers to get a realistic view of the full scale deployment. Identify and contact the owners of the computers that are going to be part of the initial deployment. In meeting with key individuals, provide a realistic estimate of the time it takes to install components. Although installation itself takes very little time, your estimate should provide enough buffer time to troubleshoot any failures. 200 Installation Guide

203 Best Practices The AppManager setup program does not require you to reboot your servers. Therefore, it isn t necessary to schedule installation for non-production hours. You should, however, consider the importance of any applications running on the servers. For servers running business-critical applications, such as a messaging system, it is best to schedule the installation during a time that will cause the least disruption of service. This practice is recommended when installing any new software on a server that runs business-critical applications, not just AppManager. The most common sources of failure stem from problems with account privileges and permission to access the servers. Even if you have researched and documented this information, allow enough time to resolve these kinds of issues. Identify dates and times the computers are available. In many organizations, access may be strictly controlled or need careful orchestration. Gather all the necessary information, such as passwords or user accounts required. Keep in mind you may need information for both the operating system and the application to be monitored. Run the AppManager Pre-install check. Run the AppManager setup program to install components (the AppManager repository, management server, console programs, web management server, and agent) locally on the selected computers. Although not required, it s recommended that you install the AppManager repository, management server, and one Operator Console first to verify installation is successful, then proceed to install additional components where required. Run the AMAdmin_AgentInstall Knowledge Script to install the AppManager agent and monitoring probes (managed objects) remotely on selected computers. Chapter 11 Staging the deployment 201

204 Running the recommended core Knowledge Scripts Once you have installed AppManager on a number of computers in your environment, you need to make specific decisions about what to monitor. During the planning stage, you should have determined a list of the key Knowledge Scripts to run. That list may include many Knowledge Scripts and cover a large number of applications. At this stage, NetIQ recommends you start with a core set of Knowledge Scripts that monitor basic server health and availability. The core set of recommended General and NT Knowledge Scripts includes: Knowledge Script General_EventLog Guidelines for running this Knowledge Script Understanding what you are monitoring: This script monitors the Event Log for events based on virtually any criteria. Initially, we recommend you monitor all logs for any Error ( Stop ) type of event. You can further filter the log entries to include or exclude specific IDs, descriptions, user names, computer names, or other criteria. 202 Installation Guide

205 Knowledge Script Guidelines for running this Knowledge Script General_MachineDown Understanding what you are monitoring: This script checks communication between the computer you drop the script on and a list of computers you specify. Special requirements: This Knowledge Script requires the AppManager agent services, NetIQmc and NetIQccm, to run as a service account with Admin privileges on the server where the script is running and on the servers the script is testing the connection to. Where to run this script: NetIQ recommends you run this Knowledge Script on a computer in the same subnet as the management server. When specifying the properties for that job, for the Machine List, you should specify a limited number of machines that represent different subnets in your network. You can then drop additional MachineDown jobs on each of the computers specified in the first job to monitor the machines in each of their own subnets. This gives you coverage without stressing network bandwidth. It also ensures that, if a router or subnet is down, you only receive one event for the server being monitored from the agent on the management server s subnet. The other servers in that subnet will not post duplicate Machine Down events. Chapter 11 Staging the deployment 203

206 Knowledge Script NT_CpuLoaded Guidelines for running this Knowledge Script Understanding what you are monitoring: This script monitors both the percentage of CPU used and processor queue length. By itself, high CPU usage may not indicate a problem. Instead, you need to consider several factors, including: queue length how you are using the computers monitored your overall strategy for the environment For example, in a transactional environment you may have a computer with CPU usage at 90% consistently. There s no room for growth on the computer, but if the queue length remains low and stable (never more than 2 or 3 processes waiting), the computer may be sized perfectly for maximum efficiency. If the queue length increases and processes are waiting, it s likelytobea problem you need to address. In a batch environment, however, you may want an event if CPU usage is over 50% and any process is waiting (queue length at 0) to ensure the machine has enough CPU headroom for when batch jobs are running. You should also consider the number of users you expect to support, for how long, and how much room for growth you need. Overall or individual CPU load: We recommend you monitor load for each CPU individually. This provides more specific information about what is really happening on a system. For example, if you monitor overall load and see CPU usage is 100%, it doesn t doesn t tell you as much about the resource usage as seeing that CPU 0 is running at 90% and CPU 1 is running at 10%. Handling spikes: Because CPU and queue length are often subject to temporary spikes, we recommend you set a short interval (2 to 5 minutes), but raise an event only after thresholds are exceeded in 3 consecutive periods. Collecting data: This Knowledge Script can be set to collect data to help you identify usage trends for your servers. For example, if you see the CPU usage increasing steadily, it can help you plan for growth. For this type of analysis, it s recommended you run a second job at a less frequent interval. 204 Installation Guide

207 Knowledge Script NT_MemUtil NT_LogicalDiskSpace Guidelines for running this Knowledge Script Understanding what you are monitoring: Physical memory is the most critical statistic you should monitor with this Knowledge Script. It is often used in conjunction with other Knowledge Scripts, such as NT_PagingHigh. Handling spikes: Because memory usage is often subject to temporary spikes, we recommend you set a short interval (2 to 5 minutes), but raise an event only after thresholds are exceeded in 3 to 5 consecutive periods. Understanding what you are monitoring: This script is recommended for monitoring disk space used and free space available for all logical disks. Running this Knowledge Script is strongly recommended, especially on computers with Exchange Server or SQL Server 7.0. On computers with applications like Exchange Server or SQL Server 7.0 that take available disk space as needed, we recommend you set a lower than normal threshold (for example, 80%) to prevent unplanned changes in disk usage from overloading the system. If you see events, add disk or remove unnecessary files. NT_LogicalDiskBusy or NT_PhysicalDiskBusy Understanding what you are monitoring: These scripts are recommended for monitoring disk operation and queue length. In a RAID array environment, use LogicalDiskBusy. In a non-raid array environment, use PhysicalDiskBusy. Events may indicate a slow disk controller, a bad physical disk, or an application that needs to be tuned (for example, a poorly tuned database application that is causing excessive swapping). These scripts can also be used in conjunction with NT_PagingHigh to help you determine the root of an event. Chapter 11 Staging the deployment 205

208 Knowledge Script NT_ServiceDown NT_TrustRelationship Guidelines for running this Knowledge Script Understanding what you are monitoring: This script is recommended for checking that required services are running and automatically restarting down services. Although you can specify services individually, we recommend you enter an asterisk (*) to check all automatically started services unless you are collecting data. If you are collecting data, specify the services you want to collect data on (for example, you may want to exclude services such as Messenger and Spooler). If you are collecting data, you should not specify all (*) services. Understanding what you are monitoring: This script is recommended for checking that a computer in a domain (Brazil) trusts a specified domain (Peru). Special requirements: This Knowledge Script requires the AppManager agent services, NetIQmc and NetIQccm, to run as a service account with Domain Admin privileges. You should not run this Knowledge Script on the PDC. Beyond this basic group of Knowledge Scripts that are universally applicable, each additional server type or application you are monitoring has its own set of recommended Knowledge Scripts. Best Practices For a basic summary of application-specific recommendations and suggestions about the Knowledge Scripts to run, see the Administrator Guide for AppManager. You may also find it useful to poll other AppManager users about their practices. You can subscribe to the AppManager mailing list through the NetIQ Support web site. Setting thresholds for the recommended scripts There are three approaches to setting Knowledge Script properties during the first stage of deployment: Use the default threshold values or your own experience and understanding of your environment to begin monitoring right away. 206 Installation Guide

209 Set all Knowledge Scripts to only collect data (Event parameter set to n) for a week or more to identify normal baseline operating values before setting thresholds for events. Set only those Knowledge Scripts that address critical issues in your environment to check for events and set the remaining Knowledge Scripts to collect data. This approach can be employed enterprise-wide or only on the servers that you have identified as needing immediate attention. If you haven t been doing any type of monitoring and are deploying a large number of Knowledge Scripts (particularly for applications such as Exchange or SQL Server), the second or third approach is recommended. The first approach, however, has the advantage of allowing you to begin actually monitoring the environment right away. If you decide to start monitoring for events right away, keep in mind that all AppManager Knowledge Scripts provide default thresholds and intervals. These defaults are based on research, white papers, tuning guides, and field expertise. If you haven t already determined thresholds on your own, use the default values at this stage of your deployment. In addition, at this stage it is a good practice to track the frequency at which you are seeing events if raising events, or the number of data points if you are collecting data. What you should see You should remain at this stage in your deployment for two to four weeks. The goal of this stage is to keep things simple, so it is recommended that you don t run additional Knowledge Scripts or strictly limit any additional scripts beyond the recommended core set. You should also strictly limit access to the Operator Console and restrict the number of users allowed to perform various activities, such as acknowledging and closing events or starting and stopping jobs. Chapter 11 Staging the deployment 207

210 The purpose of this initial stage is to have a shake-out period that reveals: Serious problems that need immediate attention (for example, computers that are dangerously low on disk space or that have pegged CPU). Any environmental issues you need to address (for example, problems with insufficient privileges, instability, SNMP or other services that need to be installed). Keeping to a core set of Knowledge Scripts also helps you prevent your staff from being overwhelmed by a sudden barrage of events or resource problems. By focusing on a limited number of key Knowledge Scripts early in the deployment, you can develop an understanding of the events generated, begin to develop your methodology for responding to them, and effectively troubleshoot any issues that arise. During this period you also need to begin evaluating your threshold settings and intervals. If you are seeing too many events, it may suggest that the thresholds are set too low for your environment or the interval is too short. Best Practices Controlling the number of events in the early stages of deployment is an important ingredient in a successful implementation. If the operations or administrative staff becomes overwhelmed with events they aren t prepared to handle, they may become frustrated or, even worse, choose to ignore events as redundant or meaningless. For any monitoring system, the key to success is how the people who are supposed to respond react when an alarm is raised. Using the data collected NetIQ recommends that you set your Knowledge Scripts to collect data during the initial stage of your deployment, then run reports associated with the core Knowledge Scripts. From the reports, you can review the high, low, and average values for core statistics in 208 Installation Guide

211 hourly, daily, weekly, or monthly time periods. There are several basic report Knowledge Scripts that you can configure to access and evaluate this information. To run reports about your environment: 1 Install at least one report-enabled agent. 2 Run the Discovery_ReportAgent Knowledge Script on the computer with the report-enabled agent. 3 In the Report view, click through tabs in the Knowledge Script pane to select the reports to run. You may find the following reports particularly useful: NT_Report_CPU Usage of Processes Summary NT_Report_CPU Resource Summary NT_Report_CPU Load Summary NT_Report_Logical Disk Usage Summary NT_Report_Memory Utilization Summary ReportAM_Event Summary ReportAM_PerfOverview ReportAM_NT Logical Disk ReportAM_NT Physical Disk Exchange_Report_IS Private Resource Summary Exchange_Report_IS Public Resource Summary SQL_Report_Data Space Availability and Utilization Summary SQL_Report_DB Space Availability and Utilization Summary SQL_Report_Error Log Summary SQL_Report_User Connections Summary Based on the information you find in these reports, you can begin to adjust threshold settings to more accurately reflect the specific characteristics of your environment. If the maximum value is still Chapter 11 Staging the deployment 209

212 within an acceptable range, reset your threshold to that value or between the average and maximum values. Note Basic AppManager reporting provides detailed information about the computers in a single management site. If you have multiple management sites and multiple AppManager repositories, you may want the more sophisticated reporting available through the Analysis Center. For information about how to configure and view reports, see the Reporting Guide for AppManager. For information about using the Analysis Center to perform more complex or comprehensive data analysis, see the User Guide for Analysis Center. Adjusting thresholds and intervals Throughout the first phase of your deployment you should review the data collected by the core set of Knowledge Scripts. Initially, you may see quite a few events as you stabilize and normalize your environment, but as you solve the serious problems that the core set of Knowledge Scripts are intended to point out, you should begin to develop a sense of your normal operating environment and begin adjusting thresholds and intervals to reflect that environment and the event load you can reasonably handle. Use the information in the reports and your own experience to modify the thresholds for the core scripts. Keep in mind that this is likely to be an ongoing process: as you gain experience or as the organization changes, you need to periodically review your settings. Moving to the next stage of deployment After running the core set of recommended Knowledge Scripts for two to four weeks, you should have a stable environment that is not generating a large number of events. At the end of this stage: 210 Installation Guide

213 You should have been able to identify and resolve any AppManager installation issues, such as problems with domains or account permissions. You should have been able to identify and resolve basic problems such as low disk space or available memory. You should have a clearer picture of your environment, in terms of the health and operation of the computers you are monitoring, the number of events to expect, and appropriateness of the default thresholds and intervals for your organization. The time it will take to achieve this can be impacted by several factors, including the distribution of servers and staff, the condition of your environment before deploying AppManager, and the resources available to you. When you feel comfortable with the core set of Knowledge Scripts you are running and the stability of the operating environment, you are ready to move to the next stage of deployment. Expanding the scope of your deployment Depending on the scope of your initial implementation and the overall size and distribution of your environment, in the second stage you may want to deploy AppManager on additional servers. Typically, very large or widely distributed organizations phase in the deployment of AppManager over a period of time. For example, if your organization is going to monitor a group of servers in the United States, Germany, and Spain, you may decide to deploy first in Germany, stabilize the environment, then expand the deployment to include the servers in Spain and the United States. Alternately, you might decide to expand the deployment to include the servers in Spain, allow time to uncover problems and stabilize that environment, and deploy to the servers in the United States at a later time. Chapter 11 Staging the deployment 211

214 Deploying additional Knowledge Scripts Regardless of the timing you use to widen the deployment to additional servers, in the second stage of deployment, you should also expand the scope of your management policy to include some or all of NetIQ s second tier of suggested Knowledge Scripts. The set of suggested Knowledge Scripts varies according to the applications you are monitoring and your organization s goals, but as a baseline consider running all or some of the following: Knowledge Script General_AsciiLog General_Counter NT_NetworkBusy NT_PagingHigh NT_PrinterHealth NT_PrinterQueue NT_RunAwayProcesses NT_SystemUpTime Reason for running this Knowledge Script You can monitor any text file for a search string, for example, to find error or failure messages. This script is suggested because of the flexibility it provides and because in most environments there are log or text files that should be monitored. You can monitor any Performance Monitor counter. This script is suggested because of the flexibility it provides and because most organizations have specific counters they are interested in that may not already be monitored in other AppManager scripts. You can monitor the percentage of bandwidth being used. You can monitor paging activity per second, which is a good indicator of actual system performance. You can monitor the status of printers and print jobs. Recommended for file and print servers and may be useful for some application servers. You can monitor the printer queue length. Recommended for file and print servers and may be useful for some application servers. You can find and kill runaway processes based on sustained high CPU usage. You can monitor the number of hours that a computer has been operational since last rebooted. Best Practices As with the core set of Knowledge Scripts, you may find it useful to poll other AppManager users about their practices. You can subscribe to the AppManager mailing list through the NetIQ 212 Installation Guide

215 Support web site. Identifying your reporting requirements During this stage of the deployment, you should also focus on your reporting needs. You need to identify: The standard AppManager reports to generate and the Knowledge Scripts required to generate those reports Who should receive the reports and how frequently How reports will be generated. For example, you may want to generate reports automatically on a scheduled basis or manually on demand. Who should be responsible for generating the reports, For example, you may want to restrict who can use the Report view or you may want to assign Exchange reports to an Exchange administrator and SQL Server reports to your DBA group. The format you want for reports. For example, you need to decide whether data should be displayed in table format, in charts, or both. How reports should be delivered. For example, you may choose to deliver reports through , post them on a web site, view them with the Report Viewer, or print them out. There s no standard or recommended set of reports you should run. Some of the common reports to start with are ReportAM_EventSummary, ReportAM_SystemUpTime, ReportAM_CompDeploy, NT_Report_CPULoadSummary, and NT_Report_LogicalDiskUsageSummary, and ReportAM_WatchList. Expanding the use of actions and notification policies During the initial deployment, most organizations do not apply many actions or automated responses. As you expand the deployment and gain experience in using AppManager, you should begin to look for ways to expand the use of responsive and corrective actions. Chapter 11 Staging the deployment 213

216 At this stage, you are ready to begin automating some corrective actions, automating your event notification process, and looking for ways to automate the acknowledgment and closing of events. You may also be ready to begin scripting your own actions and planning for future development. Reviewing and refining the deployment As you deploy AppManager across your organization, it s likely you will continue to refine your management policies and uncover new requirements. Typically, once the basic monitoring program is in place, organizations develop a deeper sense of their environment and can begin to fine-tune thresholds and job intervals, articulate and automate resolution policies, and tailor event handling, notification, data collection, and the user interface to suit their needs. At this stage, you are ready to look beyond job and Knowledge Script properties to how you can configure AppManager for your organization. The tasks to focus on include: Managing events and event notification. Handling data collection jobs and the archiving of data. Controlling communication between managed clients and the management server. Managing security and security roles within AppManager. Adding management servers and configuring primary and secondary management servers for all of your managed clients. Organizing the computers in your network into meaningful groups. Identifying and establishing Knowledge Script Groups, dynamic views, and monitoring policies for the computers in your environment. Note Before you implement any policy-based monitoring in your production environment, you should mimic your implementation in a test environment and be sure you understand the difference between 214 Installation Guide

217 standard monitoring jobs and policy-based jobs. In addition, you should keep the initial implementation of policy-based monitoring as straightforward and restricted in scope as possible until you are comfortable working with policy-based jobs. It is somewhat more difficult to make changes to policy-based jobs than standard jobs. Moving beyond deployment to extend AppManager Even after you have deployed AppManager to all or most of the servers in your environment, you will probably continue to improve and streamline your management process. This is an ongoing process that doesn t end when AppManager is fully deployed. Instead, over time, organizations tend to focus more on extending and customizing AppManager to suit specific needs and on developing more sophisticated monitoring and notification strategies. In addition, it will become increasingly important for you to manage key aspects of the AppManager environment itself to ensure reliability and optimal performance. For example, you need to develop a consistent backup strategy and plan for when and how to perform routine database maintenance. For information and recommendations concerning database maintenance, see the Administrator Guide for AppManager. At this stage and beyond, you will typically concentrate on the following types of tasks: Deploying reports automatically and designing requirements for any customized reporting (for example, to produce custom Service Level Agreement reports). Running additional Knowledge Scripts you have identified as uniquely useful for your environment or for troubleshooting specific problems. Identifying any extensions to your base monitoring program (for example, adding new applications or correlating additional monitoring tasks and responsive actions). Developing custom Knowledge Scripts. Chapter 11 Staging the deployment 215

218 Designing more complex notification or resolution rules. Integrating AppManager with other products. Documenting your extensions to AppManager and your management and resolution policies. Maintaining the AppManager repository. Periodically reviewing and updating the AppManager environment, if necessary (for example, adding or modifying users and roles, or redistributing components). Roadmap for a staged deployment The roadmap on the next page summarizes a typical deployment scenario, including the main focus of each phase of the deployment. It s important to remember that phases tend to overlap and there s a continuous on-going process of refinement. In addition, a key to success for all phases is to document your policies and processes and to communicate those policies and process to others in the organization and make the documentation widely available. Many of the tasks described generally in this chapter and roadmap are expanded or illustrated through examples in either the AppManager User Guide or Administrator Guide. 216 Installation Guide

219 Plan the implementation Weeks 1 to 4 Install AppManager Keys to this stage: Assemble a project team Gather information about the environment Develop a project plan Define basic implementation requirements Document the implementation plan Attend AppManager Administrator training Keys to this stage: Perform a dry-run installation in a test environment Identify where components need to be installed and run setup to install the repository, MS, and console programs Identify the initial group of managed clients and install the AppManager agent and managed objects on those computers Review and Adjust NO Phase 1: Deploy core Knowledge Scripts Weeks 3 to 8 Is the environment relatively stable? Keys to this stage: Deploy the recommended core set of Knowledge Scripts on the initial group of managed clients Find any problems running the core set of jobs (for example, with permissions, accounts, SNMP) and correct them Locate any critical conditions that demand immediate attention Familiarize staff with viewing and responding to events Collect information and identify normal operating environment values Begin assessing thresholds and job intervals YES As the environment stabilizes: Review and adjust job properties Begin defining notification policies Weeks 7 to 12 Phase 2: Expand the deployment Keys to this stage: Deploy Suggested Knowledge Scripts Deploy AppManager to additional servers Identify reporting needs Expand use of responsive and corrective actions Refine thresholds, intervals, resolution policies, notification policies Tailor the user interface Week 12 & beyond Phase 3: Review, customize and refine Keys to this stage: Deploy reports Deploy additional Knowledge Scripts and develop custom Knowledge Scripts Extend your base monitoring program Attend Developer training Chapter 11 Staging the deployment 217

220

221 Appendix A Updating license information This appendix describes how to view and update AppManager license information. The following topics are covered: About AppManager license keys What if you don t know your license key number? Viewing license information Starting License Manager Updating an expired license Adding a license key Requesting licensing information Importing license keys from a file Running a license report About AppManager license keys AppManager comes with an evaluation license key that allows unlimited use of all components for a specific number of days from the date you install AppManager. When you purchase an AppManager component, you are given a permanent 15-digit license key that defines the component and has no expiration date. Some license keys cover more than one component. As you purchase additional components, you ll get new license keys. 219

222 Typically, when you purchase the NetIQ AppManager Suite, you ll receive a number of license keys. For example, there is a key for the AppManager Operator Console and another for the AppManager Operator Web Console, and keys for AppManager monitoring packages (such as AppManager for SQL Server and AppManager for Exchange Server). During the AppManager setup program, when you install the AppManager repository component, you are prompted to enter the license keys of all the AppManager components you have purchased. For example, if you purchased the Operator Console and a 50-server license for monitoring Windows, you would enter two license keys (one for the Operator Console and one for the Windows managed object). It s recommended that you enter all of your license keys at this time; however, you can use the default key, which is automatically entered, and update the license information after you complete the installation process. (The default key allows you to use all AppManager components for a 30-day evaluation period from the date you install the repository component.) For more information about entering license keys during Setup, see Step 3 on page 89. If you didn t enter all of the license keys during Setup, or as you purchase and install additional AppManager components, you ll need to update the license information. Using the example above, if after purchasing the Operator Console and a 50-server license for Windows you then purchase a 20-server license for monitoring Microsoft Exchange Server, you will need to update the license information with the license key for the Microsoft Exchange Server managed object. See Adding a license key on page Installation Guide

223 What if you don t know your license key number? The person installing AppManager might not be the person who purchased it for your organization and, therefore, might not know the license key numbers. To obtain license key numbers for AppManager components you have already purchased, send an to licensekey@netiq.com. Include: Your company name and address A contact person s name, telephone number, and address A list of the AppManager components for which you need license key information We ll get back to you with the license information. Note To purchase AppManager components, contact your authorized NetIQ representative. Viewing license information 30-day evaluation license key for all AppManager components From the AppManager console programs such as the Operator Console, Distributed Event Console, and Security Manager, you can click Help > License Manager to view license information. Quantity and expiration date for the listed components Appendix A Updating license information 221

224 Starting License Manager On computers on which the AppManager console, repository, or Web management server components have been installed, the AppManager License Manager dialog box can also be accessed from the Windows Desktop. To start the License Manager, you must log on to the AppManager repository with a SQL Server login account that has permission to access AppManager. For information about granting access to AppManager to SQL Server login accounts, see Granting users access to AppManager on page Click the Start button and select the Programs folder, then click NetIQ > AppManager > Tools & Utilities > License Manager. 2 At the logon dialog box, enter the user name and password, the name of the server where the AppManager repository resides, and the repository name. For logon information, see License Manager in the Administrator Guide. Updating an expired license If you have installed an evaluation copy of AppManager, you should note the expiration date. The expiration date is displayed in the License Manager and in the About AppManager dialog box when you click Help > About AppManager from any console program. The expiration date displayed in the About AppManager dialog box is for the Operator Console license, but once this key expires, none of the console programs will run. Note The expiration date of the Operator Web Console might be different from that of the console programs. To view the About AppManager dialog box in the Operator Web Console, click About on the navigation bar. 222 Installation Guide

225 If the AppManager evaluation period has expired, click Update license when prompted the next time you log into the Operator Console, and then enter a new license key. For more information, see Adding a license key on page 223. Adding a license key As you convert from an evaluation copy or purchase additional AppManager components, you need to update the AppManager license information. You don t need to re-install AppManager to add a new license key for a component that has already been installed. For example, if you purchase AppManager after the evaluation period, you only need to add the new permanent license key. 1 Start the License Manager from the Start menu or from the AppManager Operator Console, Distributed Event Console, or Security Manager Help menu. 2 Type the 15-digit license key you were given. Use the format nnnnnnnnnn-nnnnn. 3 Click Add. The component and expiration date appear in the list. 4 To add additional keys, repeat Step 2 and Step 3. 5 When you re finished adding license keys, click Close. When updating license information for an AppManager Connector (such as AppManager for Tivoli Enterprise), you must stop and then restart the NetIQ AppManager Management Service (NetIQms) in order for the connector to work in the framework environment. This step is not necessary when updating other license information. For more information about AppManager connectors, see the appropriate connector documentation. You can find the documentation for connectors on the AppManager CD-ROM in the Appendix A Updating license information 223

226 corresponding appmanager\connectors\connector_name\documentation folder. For example, the documentation for the AppManager Connector for Tivoli Enterprise is in the folder: appmanager\connectors\tivoli\documentation Requesting licensing information You can request licenses by calling a toll-free number or by sending an request. To request licenses by 1 Start the License Manager from the Start menu or from the AppManager Operator Console, Distributed Event Console, or Security Manager Help menu. 2 Click Request. 3 Check the Send NetIQ licensing information from your repository option to include information about your current licenses with your request. 4 Type your contact information. For Your name Your address Type Your first and last name. The address that you want licenses sent to. 224 Installation Guide

227 For Your phone number SMTP computer name Type A telephone number where you can be reached in case there is a problem fulfilling your request. The name of your SMTP server. You can enter the host name or the IP address for the server. 5 Click Request Licenses. The License Manager sends your request to NetIQ support. You will receive an response to your request. Importing license keys from a file If you have more than one or two license keys or need to update multiple license keys, you may want to import the information from a file rather than typing the keys manually. When you purchase AppManager or request new licenses, you also receive a text file that contains all of the license keys. To import the license keys from a text file: 1 Start the License Manager from the Start menu or from the AppManager Operator Console, Distributed Event Console, or Security Manager Help menu. 2 Click Import. 3 Locate the license.txt file you received from NetIQ sales. 4 Click Open. The license key information is imported and displayed in the License Manager. Appendix A Updating license information 225

228 Running a license report AppManager includes the AppManager Component License report (CompLic on the ReportAM tab) and the AppManager Component Deployment report (CompDeploy) that provide information about the number of AppManager components you have licensed and installed in your environment. If the number of deployed copies exceeds the number of licensed ones, then you are reminded to purchase additional copies. (Evaluation copies of AppManager are included in the number of deployed copies but are not reflected in the number of licensed ones.) 226 Installation Guide

229 Appendix B Performing a silent installation This appendix explains how to install AppManager components silently over a network using a silent installation file that specifies installation options. Understanding silent installation Performing a silent installation allows you to install any AppManager component without user intervention. Before you can run the setup silently, however, you first need to create the AppManagerInstall.ini file that records all of your installation options for each component you want to install. Once you have created the AppManagerInstall.ini file, you can run the setup program using a special command line option to read the variables in the AppManagerInstall.ini file, and install components accordingly. Creating the installation file The silent installation file AppManagerInstall.ini contains the instructions for installing AppManager components. This file consists of variables and values that define your installation selections for each AppManager component. Each line in the file is either a name=value pair, for example, InstallPath=c:\program files\netiq, or a Boolean value displayed in all capital letters, for example, MC_INSTALL. 227

230 To create the silent installation file: 1 Open a Command Prompt window and run the AppManager setup program using the following command: setup.exe createini 2 Make your selections for each component you want installed with a single silent installation. For example, you may want to create one installation file for installing the management server and repository together and another installation file for installing agents. Note Passwords are encrypted and encoded then written to the file. When you have finished selecting your installation options, the setup program creates a record of your selections in the file AppManagerInstall.ini.Out in the Windows system folder. For an example of what this file looks like, see Sample installation file on page 229. You can manually edit the installation file, if needed. Copying the installation file to a directory After you have created the silent installation file, you need to copy this file to a directory where the AppManager installation files are located. In most cases, you will want to establish a distribution computer on your network where you will save the setup program and all of the installation files. You can then install components by running the setup program from a central location. To perform a silent installation, the silent installation file you create must be in the same directory as all of the AppManager installation files. 228 Installation Guide

231 Running the setup program with the installation file To execute the silent installation either from the command line or using a batch script, run the setup program using the following command: setup.exe -s Alternatively, you can specify the path to the installation file at the command line using the following syntax: setup.exe SILENTINI"full-path-to-ini-file" -s For example: setup.exe SILENTINI"d:\temp\am4silent.ini" -s Sample installation file The silent installation file AppManagerInstall.ini contains the instructions for installing the AppManager components you specify. The following sample AppManagerInstall.ini file illustrates what the file might look like if installing the AppManager repository, management server, and agent on a single computer, as well as the managed objects for Microsoft IIS and Compaq Insight Manager. [GENERAL] InstallPath=C:\Program Files\NetIQ [NetIQ AppManager Repository] REPOSITORY_INSTALL RP_SQLServerName=LOTUS RP_SAPassword=@2`A7%Uf35A92$D<c0Pd&!D(b5151$5044!!%!4$!1`0` RP_NetiqPassword=@9PX>(Pf35A92$D<c0Pd&!D(b5151$5044!!%!4$!1 `0` RP_QDBName=QDB RP_DataName=QDBData RP_DataSize=100 RP_DataPath=C:\Program Files\Microsoft SQL Server\MSSQL\Data RP_LogName=QDBLog RP_LogSize=50 RP_LogPath=C:\Program Files\Microsoft SQL Server\MSSQL\Data [NetIQ AppManager Management Server] MS_INSTALL Appendix B Performing a silent installation 229

232 MS_Dsn=QDBms MS_DatabaseName=QDB MS_RepositoryServerName=LOTUS 1`0` MS_NTAccountDomain MS_NTAccountUser=netiq_nt 0` MS_Security_Level=1 MSUNIX_Port=9001 [NetIQ AppManager Agent] MC_INSTALL MC_AUTODISCOVERY MC_RUNASDOMAINUSER MC_NTAccountDomain=POLAR MC_NTAccountUser=chris jones 0` MC_MdbPath=C:\Program Files\NetIQ\AppManager\db MC_MSMachine=LOTUS MC_Security_Level=1 MC_AccessList=* MC_Mailbox=netiq-LOTUS MC_Profile=netiq-LOTUS MC_ExchServerName=LOTUS MC_REPORT_AGENT [NetIQ AppManager Management Object] MC_INSTALL MO_IIS_INSTALL MO_CIM_INSTALL MO_CommunityString=public [NetIQ AppManager GUI] GUI_INSTALL GUI_WIN32_INSTALL GUI_MMC_INSTALL GUI_SECMGR_INSTALL GUI_DEC_INSTALL GUI_SDK_INSTALL [NetIQ AppManager WebConsole] WEB_INSTALL 230 Installation Guide

233 Creating an installation file manually Typically, you create the silent installation file by running the setup program with the createini option. You can, however, create the file manually, if needed. To create the silent installation file manually, use a text editor and type your entries for the components you want to install. Each entry should be on its own line. The following tables summarize the installation options for each section. Note The section markers ([SECTION]) for each component are not required, but they are recommended. The text you use to delineate the sections can vary. General section The [GENERAL] section should be included if you are installing any component. This option InstallPath=fullpath INI_NOT_ENCRYPTED_ENCODED Does this Specifies the full path to the AppManager installation location on the local computer. If you don t include this entry, the default location is used. Specifies that the password in the installation file is not encrypted. This entry is required when you are manually creating an installation file. If you use the setup.exe createini command, all passwords will be encrypted. Appendix B Performing a silent installation 231

234 AppManager Agent section The [NetIQ AppManager Agent] section should be included if you are installing the AppManager agent on a Windows computer. This option MC_INSTALL MCUPGRADE MC_REPORT_AGENT MC_AUTODISCOVERY MC_MSMachine=computername MC_AccessList=computername MC_MdbPath=fullpath MC_RUNASDOMAINUSER MC_NTAccountDomain=domain MC_NTAccountUser=user MC_NTAccountPwd=password MC_MAPI MC_Mailbox=mailbox MC_Profile=profile Does this Installs the AppManager agent services (NetIQmc and NetIQccm) and local repository. Upgrades an existing local repository. Installs the report agent. Attempts to perform automatic discovery. Identifies the name of the management server. Identifies the management servers authorized to communicate with this computer. Use an asterisk (*) to allow all management severs to communicate with this computer. Identifies the local repository path. Indicates that the agent should run using a Windows domain user account. Specifies the domain for the service account you are running the agent under. Specifies the user name for the service account you are running the agent under. Specifies the password for the service account you are running the agent under. Enables the MAPI mail option. Specifies the name of mailbox for enabling MAPI mail as an action or performing Exchange monitoring. Specifies the name of profile for enabling MAPI mail as an action or performing Exchange monitoring. 232 Installation Guide

235 This option MC_ExchServerName=servername MS_Port=port MC_Port=port Does this Specifies the name of the Exchange Server for enabling MAPI mail as an action or performing Exchange monitoring. Specifies the RPC port number for the management server to listen on. Specifies the RPC port number for the managed client to listen on. MC_Security_Level=level Specifies the security level to use. Set to 0 for Maximum security or to 1 for Standard security. MC_Security_Key_File=fullpath If using Maximum security (MC_Security_Level=0), this option specifies the full path to the key file. MC_Security_Pwd If using Maximum security (MC_Security_Level=0), this option specifies the security password. Managed object section The [NetIQ AppManager Management Object] section should be included if you are installing any managed objects on a managed Windows computer. This option MO_ACTIVEDIRECTORY_INSTALL MO_ANTIGEN_INSTALL MO_ASYNC_INSTALL MO_BACKUPEXEC_INSTALL MO_BIZTALK_INSTALL MO_BLACKBERRY_INSTALL MO_CIM_INSTALL Does this Installs the Active Directory managed object. Installs the Sybari Antigen managed object. Installs the Async managed object. Installs the Backup Exec managed object. Installs the BizTalk Server managed object. Installs the Blackberry Server managed object. Installs the CIM managed object. Appendix B Performing a silent installation 233

236 This option MO_CommunityString=public MO_COMMERCE_INSTALL MO_CONF_INSTALL MO_DELL_INSTALL MO_EXCH_INSTALL MO_CREAT BOX MO_STARTEXCH Does this Specifies the community name string for monitoring hardware (for example, CIM, Dell, HPNS, Siemens, Netfinity). Installs the Commerce Server managed object. Installs the Exchange Conferencing Server managed object. Installs the Dell managed object. Installs the Exchange Server 5.5 managed object. Enables AppManager to automatically create the Exchange mailbox. Enables AppManager to automatically start the Exchange Directory service. MO_EXCH2K_INSTALL Installs the Exchange Server 2000 managed object. MO_FWALL1_INSTALL MO_HIS_INSTALL MO_HPNS_INSTALL MO_IIS_INSTALL MO_ISA_INSTALL MO_MFXP_INSTALL MO_MQSERIES_INSTALL MO_MSCS_INSTALL MO_MSMQ_INSTALL MO_Msmq_Sa_Password=sa MO_MTS_INSTALL Installs the Check Point FireWall-1 managed object. Installs the Host Integration Server managed object. Installs the HP NetServer (HPNS) managed object for HP TopTools. Installs the IIS managed object. Installs the ISA managed object. Installs the MetaFrame XP managed object. Installs the MQSeries managed object. Installs the Microsoft Cluster Service managed object. Installs the Microsoft Message Queue Server (MSMQ) managed object. Specifies the password for the MSMQ SQL Server. Installs the Microsoft Transaction Server (MTS) managed object. 234 Installation Guide

237 This option MO_NETBACKUP_INSTALL MO_NETFIN_INSTALL MO_NETFINITYDIR_INSTALL MO_NETSHIELD_INSTALL MO_NETWORKER_INSTALL MO_NOTES_INSTALL MO_NOTES_CONFIG MO_ORACLE_INSTALL MO_Oracle_User=user MO_Oracle_Password=password MO_PROXY_INSTALL MO_SAP_INSTALL MO_SIEMENS_INSTALL MO_SITE_INSTALL MO_SMEX_INSTALL MO_SMS_INSTALL MO_SMS_Password=password MO_SNA_INSTALL MO_SQL_INSTALL MO_SQL_Password=password Does this Installs the NetBackUp managed object. Installs the IBM Netfinity Server managed object. Installs the IBM Netfinity Director managed object. Installs the Netshield managed object. Installs the Networker managed object. Installs the Lotus Domino managed object. Enables AppManager to configure Domino monitoring automatically. Installs the Oracle RDBMS managed object. Specifies the user name for discovering Oracle databases. Specifies the password for discovering Oracle databases. Installs the Proxy Server managed object. Installs the SAP R/3 managed object. Installs the Siemens ServerView managed object. Installs the Microsoft Site Server managed object. Installs the Trend Micro ScanMail for Exchange managed object. Installs the SMS managed object. Specifies the sa password for discovering thesmssqlserver. Installs the Microsoft SNA Server managed object. Installs the Microsoft SQL Server managed object. Specifies the sa password for discovering SQL Server. Appendix B Performing a silent installation 235

238 This option MO_WLBS_INSTALL MO_WMI_INSTALL MO_WTS_INSTALL Does this Installs the Microsoft Windows Load Balancing Service (WLBS) managed object. Installs the Microsoft Windows Management (WMI) managed object. Installs the Microsoft Windows Terminal Server (WTS) managed object. Response time module section The [NetIQ AppManager Response Time] section should be included if you are installing any AppManager response time modules. This option RTM_AD_INSTALL RTM_DOMINO_INSTALL RTM_EXCHANGE_INSTALL RTM_SQL_INSTALL RTM_NETWORKS_INSTALL RTM_WEB_INSTALL Does this Installs the NetIQ AppManager Response Time for Active Directory module. Installs the NetIQ AppManager Response Time for Domino module. Installs the NetIQ AppManager Response Time for Exchange Server module. Installs the NetIQ AppManager Response Time for SQL Server module. Installs the NetIQ AppManager Response Time for Networks module. Installs the NetIQ AppManager Response Time for Web module. 236 Installation Guide

239 Management server section The [NetIQ AppManager Management Server] section should be included if you are installing the AppManager management server. This option MS_INSTALL MS_Dsn=NetIQms MS_DatabaseName=database Does this Installs the NetIQ AppManager Management Service (NetIQms). Specifies the Data Source Name for connecting to the repository. If you don t include this entry, the default name is used. Specifies the name of AppManager repository database. MS_RepositoryServerName=computer Specifies the name of AppManager repository server. MS_NetIQ_Password=password MS_DOMAINUSER MS_NTAccountDomain=domain MS_NTAccountUser=user MS_NTAccountPwd=password MS_Security_Level=level MS_Security_Key_File=fullpath MS_Security_Pwd=netiq Specifies the password for the netiq database user. Indicates that the management server should run using a Windows domain user account. Specifies the domain for the service account you are running the management server under. Specifies the user name for the service account you are running the management server under. Specifies the password for the service account you are running the management server under. Specifies the security level to use. Set to 0 for Maximum security or to 1 for Standard security. If using Maximum security (MS_Security_Level=0), this option specifies the full path to the key file. If using Maximum security (MS_Security_Level=0), this option specifies the security password. Appendix B Performing a silent installation 237

240 This option MS_UPGRADE MS_Port=port MC_Port=port MSUNIX_Port=port Does this Upgrades the existing management server registry keys. Specifies the RPC port number for the management server to listen on. Specifies the RPC port number for the managed client to listen on. Enables Unix agent support and specifies the port number for the management server to listen on for communication from Unix agents. Repository section The [NetIQ AppManager Repository] section should be included if you are installing the AppManager repository. This option REPOSITORY_INSTALL @RP_LogName=QDBLog Does this Installs the AppManager repository. Specifies the name of the SQL Server computer. Specifies the sa password for SQL Server. Specifies the name of the AppManager repository database. Specifies the name of the AppManager repository data file. Specifies the path to the AppManager repository data file. Specifies the size of AppManager repository data file. Specifies the name of the AppManager repository log file. Specifies the path to the AppManager repository log file. Specifies the size of AppManager repository log file. 238 Installation Guide

241 This option RP_NetiqPassword=password RP_UPGRADE Does this Specifies the password for netiq database user. Upgrades an existing AppManager repository. Console programs (GUI) section The [NetIQ AppManager GUI] section should be included if you are installing any AppManager console programs, such as the Operator Console or Distributed Event Console. This option GUI_INSTALL GUI_WIN32_INSTALL GUI_MMC_INSTALL GUI_SECMGR_INSTALL GUI_DEC_INSTALL GUI_SDK_INSTALL Does this Enables the installation of AppManager console programs. Installs the standard Windows user interface Operator Console. Installs the Operator Console MMC Snap- In. Installs the AppManager Security Manager. Installs the Distributed Event Console. Installs the Developer s Console Utilities. Web management server section The [NetIQ AppManager WebConsole] section should be included if you are installing the Web management server. This option WEB_INSTALL Does this Installs the Web management server components. Appendix B Performing a silent installation 239

242 Performing a silent installation of the UNIX agent Performing a silent installation allows you to install AppManager UNIX agents without interactively running the installation script. Like the silent installation of other AppManager components, the silent installation of the UNIX agent uses an installation file that records the information required for completing the installation. Each line in the file is a name=value pair that provides the required information, for example, HOME=/usr/netiq. Creating the installation file The installation file consists of several required parameters in the form name=value pairs with each parameter in a separate line. The following parameters are required for silent installation. Use this parameter HOME AGREEMENT INFRASTRUCTURE MSIP MSPORT OWNER To set Installation home directory. For example: HOME=/usr/netiq Acceptance of the licensing agreement (y or n). For example: AGREEMENT=y Management environment identifier to specify AppManager as the monitoring environment for the agent to work with. For example: INFRASTRUCTURE=AppManager The IP address for the AppManager management server. For example: MSIP= The port number the AppManager Management server listens on for communication from the UNIX agent. For example: MSPORT=9001 User name that runs the UNIX agent. For example: OWNER=root 240 Installation Guide

243 Use this parameter INSTALLMO AUTOSTART AUTODISCOVERY MACHINENAME To set The installation options for any UNIX-based application management modules. If set to y, you may need to include additional entries for each AppManager for UNIX module you want to install. If you are only installing the agent, you can leave this parameter out of the installation file or set it to n. For example: INSTALLMO=n Automatic restart of the UNIX agent after installation (y or n). For example: AUTOSTART=y Automatic discovery of the UNIX computer resources after installation (y or n). For example: AUTODISCOVERY=y Name of the UNIX computer to be displayed in the Operator Console TreeView. The name should be the full host name for the computer and must be a name or address the management server can resolve for discovery to succeed. MACHINENAME=Full_host_name For example, a simple installation file might look similar to this: HOME=/usr/netiq AGREEMENT=y INFRASTRUCTURE=AppManager MSIP= MSPORT=9001 OWNER=root INSTALLMO=n AUTOSTART=y AUTODISCOVERY=y MACHINENAME=ajax.redrock.local Appendix B Performing a silent installation 241

244 If you are upgrading from a previous release, you need to include some additional parameters in the installation file. Use this parameter BACKUPUA INHERITCFG To set Handling of the backup copy of your previous UNIX agent installation. If you set this parameter to y, the backup copy of your old installation is savedinanewdirectorycalled $INSTALLPATH_v1backup. If you set this parameter to n, the backup copy is deleted after the installation upgrade is verified. For example: BACKUPUA=n Handling of your current UNIX agent configuration file. If you set this parameter to y, you don t need to specify many of the other parameters, such as the management server port number, because the values are inherited from your current configuration. If you set this parameter to n, you need to include all of the parameters in the installation file. For example: INHERITCFG=y Executing the UNIX agent installation script Once you have created the installation file, you can execute the silent installation either from the command line or in a script by using the command line option -s and the installation file name. For example:./netiq_agent_install -s /tmp/silent.cfg. Note The installation file name must be specified as an absolute path. The script will then extract information from the installation file and install the agent according to the values you have specified. 242 Installation Guide

245 Appendix C Uninstalling AppManager This chapter describes your options for uninstalling AppManager. The following topics are covered: Deciding to uninstall AppManager Before uninstalling AppManager Using Add/Remove Programs to uninstall Uninstalling AppManager on a remote computer Uninstalling the UNIX agent Deciding to uninstall AppManager Uninstalling AppManager removes all AppManager components from a computer. You cannot select individual components to uninstall. For example, if a computer has the management server, AppManager repository, and Operator Console installed, uninstalling removes not only the management server from a computer, but also the Operator Console and AppManager repository. Note Be especially careful not to mistakenly run the Uninstall program on a computer containing an AppManager repository with data that you still need. Doing so permanently deletes the repository, including all of its stored data and jobs. 243

246 If you decide to uninstall all of the AppManager components on a computer, you can: Use the Add/Remove Programs Control Panel to uninstall directly from a local computer. Run a Knowledge Script job to uninstall AppManager on one or more remote computers. Before uninstalling AppManager Typically, AppManager components are installed on various computers in your environment. When AppManager components reside on more than one computer, before running the uninstall program, be sure to: Stop the NetIQ AppManager Management Service (NetIQms). Disconnect any users and applications that are accessing the AppManager repository. For example, close all AppManager console programs (such as the Operator Console or Security Manager) and the Operator Web Console. Note If all AppManager components are installed on a single computer, as in a test environment, then the uninstall takes care of stopping the NetIQ AppManager Management Service and disconnecting users from the repository. Using Add/Remove Programs to uninstall You can use the Add/Remove Programs Control Panel to uninstall AppManager. The uninstall removes all AppManager components from a computer. For example, the Uninstall program removes not only the management agent from a computer, but also AppManager programs, such as the Operator Console, and components such as the AppManager repository. 244 Installation Guide

247 You can run the Uninstall program in two ways: You can uninstall directly from a local computer. You can run a Knowledge Script job to uninstall AppManager on one of more remote computers. In both cases, the same Uninstall program runs. The only difference is where and how you start the Uninstall program. 1 From the Windows Desktop, click the Start button, then click Settings > Control Panel. 2 Open Add/Remove Programs. 3 Select NetIQ AppManager from the list of installed programs. 4 When you are asked to confirm if you want to uninstall AppManager on the current computer, click Yes. If the computer contains an AppManager repository, the confirmation message informs you of this fact. If you click No, the Uninstall program stops without uninstalling any AppManager components. A progress bar indicates when the Uninstall program has finished. Note The AppManager Response Time for Networks module installs a NetIQ Endpoint that is separate from AppManager components. Therefore, uninstalling AppManager does not remove the NetIQ Endpoint. If you have installed the AppManager Response Time for Networks module and want to remove it, you need to uninstall the NetIQ Endpoint separate from uninstalling AppManager components. Appendix C Uninstalling AppManager 245

248 Uninstalling AppManager on a remote computer To uninstall AppManager on a remote computer, you run a Knowledge Script job on that computer. You can run the job from either the AppManager Operator Console or the AppManager Operator Web Console. The following instructions explain how to run the job from the Operator Console. See the User Guide for information on running jobs from the Operator Web Console. 1 In the TreeView pane of the AppManager Operator Console, locate the computers or groups where you need to uninstall AppManager. 2 In the Knowledge Script pane, click the AMADMIN tab. 3 From the AMADMIN tab, drag the Knowledge Script named AppManagerUninstall and drop it on the computers or groups you located in the TreeView pane. 4 In the Schedule tab of the Knowledge Script Properties dialog box, make sure Run Once is selected. 246 Installation Guide