Server Management 2.0

Transcription

1 Server Management 2.0 Installation and Configuration Guide Server Management 2.0 and Higher May 2008

2 .

3 unisys imagine it. done. Server Management 2.0 Installation and Configuration Guide Server Management 2.0 and Higher May

4 NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Unisys is a registered trademark of Unisys Corporation in the United States and other countries. Cisco is a registered trademark of Cisco Systems, Inc. NetIQ is a registered trademark of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. AppManager and Knowledge Scripts are registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their respective holders.

5 Server Management 2.0 Installation and Configuration Guide Server Management 2.0 and Higher Server Management 2.0 Installation and Configuration Guide Server Management 2.0 and Higher Bend here, peel upwards and apply to spine.

6 .

7 Contents Section 1. Introduction 1.1. Documentation Updates Understanding Server Management Software Understanding AppManager Software Understanding Setup Assistant Server Management Setup Assistant Types of Data Collected User-Provided Data Section 2. Management Server Requirements 2.1. Hardware, Software, and Media Requirements Configuring the SNMP Service Verifying the Security Policy for Windows XP Installing Interim Corrections on Systems You Want to Manage Section 3. Preparing to Upgrade an Existing Sentinel Management Server 3.1. Isolating the Management Server During Software Installation Uninstalling the Cisco Security Agent Uninstalling the AppManager Program or Server Director on the Management Server Stopping the Call Home Generator Service Section 4. Installing or Upgrading Software on the Management Server 4.1. Setting Internet Explorer Security Options Configuring Databases for AppManager Software Installing AppManager Software Installing AppManager 6.0 Software Installing AppManager 7.0 Software Firewall Configuration Information Installing Server Management Software Reconnecting the Management Server to the Network iii

8 Contents Section 5. Initially Configuring the Management Server 5.1. Understanding User Roles Defining Users Using an Internet Proxy Server with Server Management Software Using a Modem Connection for Call Home Configuring and Testing the Modem Modifying the Hosts File to Use a Modem Connection Modifying the Management Server Hosts File Accessing the Infrastructure Solutions Console Verifying and Completing Software Settings Section 6. Installing or Upgrading AppManager Software on Windows Servers and Partitions Section 7. Configuring ES7000 Model 7405R G1 Systems 7.1. ES7000 Model 7405R G1 System Requirements Configuring Windows Servers and Partitions Configuring the SNMP Service on Servers and Partitions Configuring Internet Explorer Options Firewall Configuration Information Installing Server Management Software Modifying the Server or Partition Hosts File Installing and Configuring on Linux and VMware ESX Server Servers and Partitions Running Setup Assistant Configuring Server and Partition Force Dumps Optional Workgroup and Domain Configuration Section 8. Completing the Management Server Configuration 8.1. Using Configuration Assistant for Virtual Machines Adding Additional Systems to be Monitored Completing Server and Partition Configuration for Non- Windows Operating Systems Verifying and Completing AppManager Setup Verifying Communication with Integrated Lights Out Manager (ILOM) Configuring Call Home Generator Services Defining the Call Home Central Service Verifying Call Home Readiness for New Systems Introduction to Sending a Call Home RFU Packet iv

9 Contents Prerequisites to Use the Internet for Transmissions Identifying the Central Service Connection Method Sending a Call Home RFU Packet Verifying Call Home Updating Port Numbers for Server Management Software Communication Changing the Server Management Services Account Credentials Obtaining Updates Registering for Notification of Software Updates Installing Virus Protection Software Submitting the Arrival Quality Report Section 9. Installing and Configuring Client Workstations 9.1. Client Workstation Requirements Setting Internet Explorer Security Options Firewall Configuration Information Installing Server Management Software Modifying the Client Workstation Hosts File Configuring for AppManager Software Defining a User Account for the AppManager Operator Console Installing the AppManager Operator Console Viewing Product Documentation Installing Virus Protection Software Obtaining Updates Appendix A. Firewall Considerations A.1. Understanding Firewall Requirements A 1 A.2. Firewall Requirements for the Management Server A 1 A.3. Firewall Requirements for AppManager Management Server Software A 2 A.4. Firewall Requirements for Service Processors A 3 A.5. Firewall Requirements for Servers and Partitions You Want to Manage A 4 A.6. Firewall Requirements for Client Workstations A 5 Appendix B. Installing Unisys Software in an Existing AppManager Infrastructure B.1. Integrating Unisys Software into an Existing AppManager Installation B v

10 Contents vi

11 Tables 1 1. AppManager 6.0 and 7.0 Management Server Software Requirements vii

12 Tables viii

13 Section 1 Introduction This guide provides the information necessary to install and configure Server Management software on each of the following hardware components: Management server Servers and partitions you want to manage Client workstations In addition, this guide provides information on upgrading a Sentinel Management Server to run the latest Server Management software. Before you begin the Server Management software installation, you must initially configure your hardware components, as follows: For management servers and client workstations, configuration means that you must install the appropriate operating system. For servers and partitions you want to manage, configuration means that you must complete the steps in the appropriate hardware and software installation guides to install and configure your servers and their operating systems. This guide is intended for system administrators and Unisys service representatives who are responsible for installing and administering servers. Depending on your particular configuration, some procedures or steps in this guide might not apply. Skip the unnecessary procedures and continue with those procedures that apply to your system or situation Documentation Updates This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE) To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site: Note: If you are not logged into the Product Support site. you will be asked to do so

14 Introduction 1.2. Understanding Server Management Software Server Management software helps you monitor and manage the systems in your enterprise. The Server Management Infrastructure Solutions Console provides an easy-touse and convenient interface for managing both the physical and virtual components of your environment. Server Management software can be installed on management servers and on servers and partitions you want to manage. This software can also be installed on client workstations, which provide remote access to your management environment. You can use the Infrastructure Solutions Console to manage servers running the latest version of Server Management software as well as servers running older versions of Unisys software, for example, managed servers running Server Sentinel software. This means you can use the Infrastructure Solutions Console to manage new ES R G1 systems and existing ES7000/one systems and also to monitor other ES7000 and ClearPath systems in your environment. However, when you select a managed server running Server Sentinel software, a new window is launched with the individual Server Sentinel page for that server displayed. If you decide to upgrade a management server running Server Sentinel software to run the latest Server Management software, the Infrastructure Solutions Console becomes the entry point for managing systems from that management server. If you want to continue using the familiar Server Sentinel navigation to manage your older servers as a group, you can configure a new management server to run Server Management software. The following figure shows the components that run Server Management software:

15 Introduction 1.3. Understanding AppManager Software AppManager software, versions 6.0 and 7.0, is provided for free with your purchase of Server Management software. You might want to install this software to take advantage of its centralized event management, powerful scripting, historical data analysis, and automated response to event-driven actions. For more information about AppManager software, see the Server Management 2.0 Software Release Announcement. If you decide to install and use the AppManager software, you must first determine whether you want to install version 6.0 or 7.0. Note: You should use the same level of AppManager for the AppManager Management Server, agent, and Operator Console. (Use either AppManager 6.0 in your environment or use AppManager 7.0.) The AppManager 6.0 agent cannot be installed on servers and partitions running Windows Server If you want to monitor Windows Server

16 Introduction servers and partitions, then you should use the 7.0 version for all AppManager components. See the following table for differences between these two software versions: Table 1 1. AppManager 6.0 and 7.0 Management Server Software Requirements AppManager 6.0 AppManager 7.0 Database Information Operating System Information Supports either Microsoft SQL Server 2000 with Service Pack 3 or later or Microsoft SQL Server 2000 Desktop Engine (MSDE) with Service Pack 3 or later. If you do not have a SQL Server database, you can download and install MSDE for free from the Microsoft Web site. Runs on Windows Server 2003 and on Windows XP operating systems. Supports either Microsoft SQL Server 2000 with Service Pack 3 or later or Microsoft SQL Server Note: Neither MSDE nor SQL Server Express is supported by AppManager 7.0. Runs on Windows Server 2003 operating systems. Processor Type Runs on 32-bit processors only. The AppManager software includes the following three major components: AppManager management server software (includes the Repository Database, Management Server software, Agent, Monitoring Modules, Web Management Server software, Control Center and Deployment Service, and Operator Console) Install this software set on your management server or on a different server, depending on your needs. Note: The Server Management software can run on operating systems that AppManager does not support. Therefore, if you plan to run any other operating system than those listed in the previous table, you must install the AppManager software on a separate server. AppManager Operator Console - Only if you install the AppManager management server software on a separate server, then you must install the AppManager Operator Console on your management server. The Server Management software uses components of the AppManager Operator Console to remotely query the AppManager management server. - If you configure one or more client workstations, then you can install the AppManager Operator Console on one or all of the client workstations to connect directly to the AppManager management server. This is optional. AppManager agent Install this software on Windows servers and partitions you want to manage

17 Introduction Note: If you are a current customer of NetIQ Corporation and you want to integrate Server Management software with your existing AppManager infrastructure, see Appendix B for more information Understanding Setup Assistant An important requirement of the Server Management software installation and configuration process is using Setup Assistant. Read the following topics to learn more about Setup Assistant. You are instructed to run this application later in the configuration process Server Management Setup Assistant Before you implement your network, you need to plan your LAN configuration and assign network values. Setup Assistant enables you to collect this data and place it in a single configuration information file that the system uses when the configuration information file is installed. Setup Assistant has the following capabilities: Collect configuration and network values. Save configuration data and complete later. Print a summary page. Import and modify an existing configuration. Deploy the system configuration to applicable components. Running Setup Assistant ensures you have the data required to configure the system. Print and save the summary page of the final configuration for future reference. During deployment, the configuration information file is saved to the management server, and used to configure Server Management components and automate the system installation and configuration process Types of Data Collected The following types of data are collected by Setup Assistant: Customer information The customer and contact information you provide is used by the server health monitoring facilities of Server Management. System information The system information you define here is used to configure your Service Processor and networking components. Server or partition information The information you define here is used to configure your server or partition

18 Introduction Management Server information The information you define here establishes how system components are to communicate with each other and is used by the various networking components of your system User-Provided Data You might be asked to provide some or all of the following data during a Setup Assistant session: System name Company name Address City and state or province Postal code Country Console phone Remote phone Primary contact information: - Name - Department - Phone - For the Service Processor: - Service Processor name, IP address, or both - Subnet mask if fixed IP address is used - Default gateway if fixed IP address is used For the server or partition: - Operating system type - Computer name - Maintenance LAN IP address For Call Home Central Services: - Transportation means: Internet/LAN or modem - Computer name or IP address for primary Central Service location - Computer name or IP address for secondary Central Service location - Management server communication port numbers The default values can be used

19 Introduction For AppManager software: - Management server computer name or IP address This is usually the management server. - Repository name - Web reporting location: computer name or IP address This is usually the management server. SNMP read-only community name The default is public. alert information: - Mail server method for sending SMTP or Exchange - Mail server computer name or IP address - Sender name - Sender address

20 Introduction

21 Section 2 Management Server Requirements A management server running Server Management 2.0 software must be an independent server in your environment; you can provide your own hardware, or you can purchase one or more qualified servers from Unisys. If you are using VMware ESX Server in your environment, you can install the management server software onto a virtual machine, as long as that VMware ESX Server host (also known as the virtual machine monitor) is not being managed by the management server. You cannot install the management server software on any system server or partition, whether physical or virtual, or on any system external Service Processor Hardware, Software, and Media Requirements Note: Management servers running Server Management software do not operate correctly when Microsoft Terminal Services is used, except for Terminal Services in the Remote Administration mode. Hardware Requirements All management servers require the following minimum hardware configuration: 2.4-GHz Xeon processor (single processor) with at least 512 megabytes (MB) of memory 1 gigabyte free disk space Super VGA color monitor with a display area of at least 1024 x 768 pixels; a 1280 x 1024 display area is recommended Fast Ethernet network interface card (NIC) Connection to the network through a network segment that can access the server and partition operating systems and Service Processors Software Requirements A management server can run any of the following Windows operating systems. Note: The following are the latest supported Service Packs for each operating system

22 Management Server Requirements Windows Server 2003 R2, Standard Edition, with Service Pack 2, 32-bit and x64 editions Windows Server 2003 R2, Enterprise Edition, with Service Pack 2, 32-bit and x64 editions Windows XP Professional, with Service Pack 3 for 32-bit editions and Service Pack 2 for x64 editions Note: AppManager management server software cannot run on x64 operating systems. Therefore, if you use an x64 operating system for your management software, you must install the AppManager management server software on a different server. See Section 1 for more information. All management servers require the following software configuration: Internet Explorer 6.0 and higher TCP/IP Each management server must be configured to run TCP/IP with either static or dynamic IP addressing. SNMP service SNMP must be configured on the management server and on all servers, partitions, and Service Processors that it manages. Note: For information on how to configure SNMP on servers, partitions, and Service Processors, refer to your system installation and configuration documentation. Valid administrator group privileges on the system User authentication requirements User authentication on all of the components of each system you plan to manage (including Service Processors, servers, partitions, and client workstations) must be the same as the management server. Unisys systems are initially installed using the Microsoft workgroup model, meaning that you must configure the same user name, password, and group membership on each component. After installation, your environment can be configured to use domain credentials instead. See your system planning documentation for more information. For security reasons, it is highly recommended that all users have strong passwords. Some Unisys server management software does not accept users without passwords. Internet Information Services (IIS) If you intend to configure the Call Home Central Service from your management server, hardware and software that enables you to connect to the Internet (either a modem or a network interface card) Media Requirements The Server Management Services Software CD-ROM is required for installation and is provided with your order

23 Management Server Requirements The AppManager 6.0 Supplement Software CD-ROM and the AppManager 7.0 Supplement Software CD-ROM are included with your order so that you can optionally install AppManager software Configuring the SNMP Service To support system management software that uses SNMP, you must configure SNMP. Configuring the SNMP community and defining SNMP traps enables communication between the management server and your environment. Note: You can add and remove SNMP trap destinations at any time as required. If your environment includes other management servers or third-party management frameworks, configure them as SNMP trap destinations; otherwise, you will not receive all of the applicable data. To configure SNMP or verify that your current configuration is defined to support this software, perform the following steps: 1. Access the Computer Management window. 2. In the left pane, expand Services and Applications and click the Services icon. 3. In the list of services in the right pane, right-click SNMP Service and click Properties. The SNMP Service Properties dialog box appears. 4. Select the Agent tab. 5. Type a value in the Contact box. This string value indicates the person to contact if an error is found with the system. 6. Type a value in the Location box. This string value indicates the physical and logical location of the system. 7. Select the Traps tab. Note: Most SNMP-enabled management frameworks expect the value public by default. 8. If you want to use public for a community name, verify that it is entered in the Community name list. If it is not listed, enter it and then click Add to list. 9. If you want to use a value other than public for a community name, enter it in the Community name list and then click Add to list. If public is present by default and you do not want to use it, delete it. 10. Select the Security tab. 11. Ensure that the Send authentication trap check box is selected. If the SNMP agent receives traps from an unknown IP address and community string pair, it generates an authentication failure trap to all the remote management servers

24 Management Server Requirements 12. Ensure that the community name that you specified previously is listed as READ ONLY. If it is not, do the following: a. Click Add in the Accepted community names box. b. Type the community name in the Community Name box. c. Select READ ONLY from the Community rights list. d. Click Add. 13. Enter a community name with a READ WRITE value as follows: Note: Do not specify a value of READ WRITE for the community name whose value you previously specified as READ ONLY; you should use two different community names for security reasons. a. Click Add in the Accepted community names box. b. Type a community name in the Community Name box. (This value is specific for your site, and it is case-sensitive.) c. Select READ WRITE from the Community rights list. d. Click Add. 14. Decide whether to accept SNMP packets from any host or from only selected hosts, depending on your desired security and level of network traffic. If you selected Accept SNMP packets from any host, the configuration is complete. Click OK. If you selected Accept SNMP packets from these hosts, do the following: Note: Repeat the following steps to add the value localhost and the computer name for each server, partition, and Service Processor being monitored by this management server. a. Click Add below the Accept SNMP packets from these hosts value. The SNMP Service Configuration dialog box appears. b. In the Host name, IP, or IPX Address box, type the appropriate computer name or IP address. c. Click Add. d. Click OK. 15. Locate SNMP Service in the right pane of the Computer Management window, right-click it, and click Restart to restart the service and save your settings. 16. If you are prompted to restart other services, click Yes. 17. Close the Computer Management window Verifying the Security Policy for Windows XP Note: Perform the following procedure only if your management server is running Windows XP

25 Management Server Requirements In Windows XP, the default security policy is set to Guest only. This setting only enables you to log on to the management server remotely using guest privileges. (You cannot log on with administrative privileges.) To verify that the security policy is set properly, perform the following steps: 1. On the Start menu, point to Settings, and then click Control Panel. Control Panel is displayed. 2. Double-click Administrative Tools. The Administrative Tools window is displayed. 3. Double-click Local Security Policy. The Local Security Settings window is displayed. 4. In the left pane, expand Local Policies if it is not already expanded. 5. In the left pane, select Security Options if it is not already selected. 6. In the right pane, right-click Network access: Sharing and security model for local accounts and click Properties. The Network access: Sharing and security model for local accounts Properties dialog box is displayed. 7. Verify that the value in the drop-down menu is set to Classic - local users authenticate as themselves. If it is not, update the setting. 8. Click OK to close the Properties dialog box. 9. Close the Local Security Settings window. 10. Close the Administrative Tools window Installing Interim Corrections on Systems You Want to Manage Before you install Server Management software on the management server, ensure that all of your existing Unisys systems are running the latest Interim Corrections (ICs) and quick-fix releases (QFRs), which are replacement modules containing fixes for your software or platform firmware. To access the latest updates and apply them to your systems, use EZupdate to discover and download any required updates. Alternatively, perform the following steps: 1. Access the Unisys Product Support Web site at 2. Sign on to entitled support with your user name and password. If you do not have a user name and password, click Register and then follow the on-screen directions to register. After you sign on, the Product Support page appears. 3. Select a system type and click Go. The support page for that system is displayed

26 Management Server Requirements 4. Click Releases. The releases for the system are displayed. 5. Find the appropriate fixes for both your software and your platform firmware. 6. Follow the on-screen instructions to download the available fixes for your systems

27 Section 3 Preparing to Upgrade an Existing Sentinel Management Server You can upgrade an existing Sentinel Management Server to run the Server Management software. However, if you perform this upgrade, the Infrastructure Solutions Console becomes the entry point for managing systems from that management server. If you want to continue using the familiar Server Sentinel navigation to manage your older servers as a group, you can configure a new management server to run Server Management software. Note: If you are upgrading a Sentinel Management Server running Server Sentinel 4.3 or earlier, do not delete any instances of MSDE until you have completed all of the procedures in this document. After you have finished the installation and configuration, open the Infrastructure Solutions Console and verify that all of your systems, servers, and partitions are present. After you complete this verification, you can delete the MSDE instances, if you choose. If you are not upgrading a Sentinel Management Server, or if you are upgrading a Sentinel Management Server running Server Sentinel 4.x or higher, skip this section. If you are upgrading a Sentinel Management Server that is running Server Sentinel 2.x or 3.x, perform the procedures in this section. Note: If your current Service Processor also acts as a Sentinel Management Server, you must provide a new management server; you cannot install the Server Management software on a Service Processor Isolating the Management Server During Software Installation If you are upgrading an existing management server, you must isolate it from any Service Processors on the network. Isolate the existing management server by disconnecting all network cables or by disabling all network interface cards (NICs)

28 Preparing to Upgrade an Existing Sentinel Management Server 3.2. Uninstalling the Cisco Security Agent Perform the following procedure: 1. On the Start menu, point to Settings and click Control Panel. 2. Double-click Add/Remove Programs and remove Cisco Security Agent. 3. Close the Add/Remove Programs window. 4. Restart the server and log on Uninstalling the AppManager Program or Server Director on the Management Server If you are preparing for an upgrade, read the information under Before Uninstalling the AppManager Program or Server Director. Otherwise, proceed with the information under Uninstalling the Software. Before Uninstalling the AppManager Program or Server Director If you are upgrading a management server running Server Sentinel 2.1 or earlier software, you must uninstall Server Director. This is necessary because a Server Director repository gives undefined results if it is upgraded to the AppManager program. If you are upgrading a management server running Server Sentinel 2.2 through Server Sentinel 3.4 software, then the AppManager software is at an earlier level (5.0). Use the procedures described in 4.3 Installing AppManager Software to upgrade the existing AppManager software to a later level. Optionally, you can uninstall in advance the earlier version of the AppManager software. Consider the following factors in deciding whether to uninstall the AppManager program: Advantage: The new management software is installed quickly because the installation of a new AppManager management server and repository takes only about 30 minutes. Upgrading an existing installation usually takes 3 hours or longer. Disadvantages - Customized scripts and graph data are deleted. - After the new AppManager program is installed, you must add all your managed servers to the tree view and run the Discover_NT and Discover_Unisys scripts on each server or partition. Uninstalling the Software To uninstall the AppManager program or Server Director on a management server, perform the following steps: 1. On the Start menu, point to Settings, and then click Control Panel. 2. Double-click Administrative Tools and then double-click Services. The Services window is displayed

29 Preparing to Upgrade an Existing Sentinel Management Server 3. Right-click one of the following services, depending on whether you are uninstalling the AppManager program or Server Director: NetIQ AppManager Management Service (NetIQms) Server Director Management Service (NetIQms) 4. Click Stop. 5. Right-click the Enterprise Server Directory service and then click Stop. This service is started automatically during the software installation. 6. Disconnect any users and applications that are accessing the AppManager or Server Director repository. For example, close all console programs (such as the Operator Console, Security Manager, or License Manager) and the Operator Web Console. 7. On the Start menu, point to Settings, and then click Control Panel. 8. Double-click Add/Remove Programs and uninstall NetIQ AppManager or Server Director. 9. After the uninstallation process is complete, delete any existing QDB repository database by using the SQL Server Enterprise Manager. If you do not have the SQL Server Enterprise Manager, enter the following command from a command prompt: osql -E -q drop database qdb Cold-Starting the AppManager Agent Cold-start the AppManager agent on each server or partition to remove cache information related to the old QDB repository database. 1. On the Start menu, point to Settings, and then click Control Panel. 2. Double-click Administrative Tools and then double-click Services. The Services window is displayed. 3. Right-click NetIQ AppManager Client Resource Monitor Service and click Properties. The Properties dialog box for the service is displayed. 4. Click Stop. 5. Type -o (hyphen, lowercase letter o) in the Start Parameters box. 6. Click Start. Note: You must click Start, not OK. The OK button does not start the service. 7. Click OK to close the Properties dialog box

30 Preparing to Upgrade an Existing Sentinel Management Server 3.4. Stopping the Call Home Generator Service Before upgrading, you should stop the Call Home Generator Service on the management server by doing the following: 1. From the Computer Management window, select Services and Applications. 2. Right-click Call Home Generator Service and then click Stop. 3. Verify that the Startup Type is Manual. If the Startup Type is not Manual, do the following: a. Right-click Call Home Generator Service and then click Properties. The Call Home Generator Service Properties dialog box is displayed. b. On the General tab, select Manual from the Startup type list

31 Section 4 Installing or Upgrading Software on the Management Server Use the procedures in this section to install, reinstall, or upgrade the software on your management server Setting Internet Explorer Security Options Note: Internet Explorer settings only affect the current user account. If you log on as a different user, you must repeat these configuration steps. Use these steps to set and verify the proper Microsoft Internet Explorer settings: 1. Launch Internet Explorer. For Windows Server 2008, you must be logged on to a user account in the Administrators group. If this account is not the built-in Administrator account, then launch Internet Explorer by right-clicking the Internet Explorer shortcut icon and clicking Run As Administrator. 2. Click Internet Options on the Tools menu. The Internet Options dialog box appears. 3. Select the Security tab. 4. Select the Trusted sites icon. 5. Click Sites. The Trusted sites dialog box appears. 6. Make sure the Require server verification ( for all sites in this zone check box is not selected. 7. Add a URL for each Service Processor, management server, and Windows server and partition. If a Service Processor, management server, or Windows server or partition is in a different Domain Name System (DNS) domain than the computer on which you are performing this procedure, use fully qualified host names instead of the URL for that component. a. In the Add this Web site to the zone box, enter one URL, for example, b. Click Enter or Add. c. Repeat steps a and b until you have added each URL

32 Installing or Upgrading Software on the Management Server Note: If you are running Internet Explorer on a management server or Service Processor, repeat steps a and b to add the URL 8. Add an IP address for any components that use fixed IP addresses rather than DHCP addresses. These components might include the Service Processor, management server, partition, and Console Manager (if applicable). a. In the Add this Web site to the zone box, enter one IP address, for example, b. Click Enter or Add. c. Repeat steps a and b until you have added each IP address. 9. Add the Unisys Product Support Web site using the IP address and the host name Click Close or OK to close the dialog box. 11. Click Custom Level under Security level for this zone. The Security Settings dialog box appears. 12. In the Settings list, ensure that the following settings are selected. Note: Not all of these settings are available in every Internet Explorer and Windows operating system combination. If you do not see a setting in your environment, simply disregard that setting. Category Option Setting ActiveX controls and plug-ins Allow previously unused ActiveX controls to run without prompt Automatic prompting for ActiveX controls Binary and script behaviors Download signed ActiveX controls Download unsigned ActiveX controls Initialize and script ActiveX controls not marked as safe Run ActiveX controls and plug-ins Script ActiveX controls marked safe for scripting Enable Enable Enable Enable Enable or Prompt Enable Enable Enable Miscellaneous Access data sources across domains Enable Navigate sub-frames across different domains Submit nonencrypted form data Enable Enable or Prompt Scripting Active scripting Enable or Prompt

33 Installing or Upgrading Software on the Management Server Note: If the computer accessing the management software is not in the same intranet zone as the management server or Service Processor being accessed, select Automatic Logon with current username and password under User Authentication to avoid being prompted for credentials. 13. Click OK. If you receive a warning message, click Yes. 14. Do the following to allow active content to run: Notes: After you install the software, return these security settings to their previous values. Not all security settings are available in every Internet Explorer and Windows operating system combination. If you do not see a setting in your environment, simply disregard the instruction to change it. a. Select the Advanced tab in the Internet Options dialog box. b. Scroll down and select the following two check boxes under Security: Allow active content from CDs to run on My Computer Allow active content to run in files on My Computer 15. If you are configuring a client workstation, and your client workstation and management server are part of the same Internet Explorer security zone, skip to the next step. Otherwise, do the following: Note: After you install the software, return these settings to their previous values. a. Select the Internet icon on the Security tab. b. Click Custom Level under Security levels for this zone. The Security Settings dialog box appears. c. In the Settings list, ensure that the following settings are selected: Category Option Setting ActiveX controls and plug-ins Allow previously unused ActiveX controls to run without prompt Initialize and script ActiveX controls not marked as safe Enable Prompt d. Click OK. If you receive a warning message, click Yes. 16. Click OK in the Internet Options dialog box. 17. Close Internet Explorer. Note: Pop-up blockers prevent this software from operating properly. To avoid this problem, allow pop-ups from the management server, Service Processor, and client workstation. For information on allowing pop-ups, refer to the documentation for Internet Explorer or for your third-party software

34 Installing or Upgrading Software on the Management Server 4.2. Configuring Databases for AppManager Software Notes: Use the following guidelines if you intend to install AppManager software in your environment. If you do not plan to install the AppManager software, you can skip this topic. These guidelines apply to the server on which you install the AppManager management server software; this can be the same as the management server or a different server. Both AppManager 6.0 and AppManager 7.0 have specific database requirements, as follows: AppManager 6.0 Requires a default instance of Microsoft SQL Server 2000 with Service Pack 3 or later or Microsoft SQL Server 2000 Desktop Engine (MSDE). (If you do not have a SQL Server database, you can download and install MSDE for free from the Microsoft Web site.) AppManager 7.0 Requires a default instance of Microsoft SQL Server 2000 with Service Pack 3 or later or Microsoft SQL Server For both AppManager versions Configure the default database instance to use SQL Server and Windows authentication mode (also known as mixed mode). You can configure this setting during installation or use SQL Server Enterprise Manager to change the authentication mode. Set the sa account password to a non-empty value. Make a note of this value, which you must use later when you configure the Infrastructure Solutions Console to communicate with the AppManager repository, as described in Verifying and Completing Settings in Section 5. If you are using an MSDE instance that was installed with an earlier level of Unisys management software, the sa account might still have the initial default value of SentinelPasswordForSA Installing AppManager Software If you choose to install the optional AppManager software, you must choose The software level to be installed Whether to install the AppManager management server software on a server running the Server Management software or on a different server. These installation choices are discussed in Section

35 Installing or Upgrading Software on the Management Server If you install the AppManager management server software on a different server, you must still install the AppManager Operator Console on the same server that is running the Server Management software. The Server Management software uses components of the AppManager Operator Console to communicate with the AppManager management server. The AppManager Operator Console and the AppManager management server must be at the same version level. Therefore, your choices are as follows: Install the AppManager 6.0 management server software on the server running the Server Management software. Install the AppManager 6.0 Operator Console on the server running the Server Management software and the AppManager 6.0 management server software on a separate system. Install the AppManager 7.0 management server software on the server running the Server Management software. Install the AppManager 7.0 Operator Console on the server running the Server Management software and the AppManager 7.0 management server software on a separate system. Refer to the following guidelines when installing AppManager components Installing AppManager 6.0 Software To install AppManager 6.0, perform the following steps: 1. For installation instructions, refer to the NetIQ AppManager Installation Guide, which is included on the AppManager 6.0. Supplement Software CD-ROM at \appmanager\documentation\install.pdf. 2. Refer to the following guidelines for suggestions about the messages and options that you might encounter. Your installation options depend on the AppManager components that you select. Installation Guidelines for the AppManager 6.0 Management Server AppManager 6.0 requires Microsoft SQL Server 2000 with Service Pack 3 or later or Microsoft SQL Server 2000 Desktop Engine (MSDE) with Service Pack 3 or later. Accept the default values unless the following guidelines indicate otherwise

36 Installing or Upgrading Software on the Management Server When prompted with What AppManager components do you want to install, select All the available components. If you are upgrading from an earlier version of the AppManager software, you might be asked whether to upgrade or replace existing components. For most components, the difference is not important. You must choose the upgrade option if you want to retain data, jobs, and any customized scripts in the repository. However, the repository upgrade option substantially increases the installation time because upgrading a repository typically takes 3 hours or longer. Installing a new repository usually takes 30 minutes or less. When prompted with Select the applications and systems you want to monitor on this server, disable all the listed options except for AppManager Asynchronous Event Receiver. (Licenses for these options expire within 30 days.) When the Response Time Module Selection dialog box appears, clear all the check boxes in this dialog box. (These modules are not included in the basic AppManager license.) When prompted with Select the agent options you want, clear the Enable reporting capability check box. If this check box is selected, you must specify a user account for the agent service. It is preferable to run the agent under the default Local System account. At the end of the AppManager installation, click No when prompted to register the product. Your registration is through Unisys, so it is not appropriate to register directly with NetIQ. After the installation is complete, ensure that the World Wide Web service is running. If the service is not running, or if you cannot start it, reboot the system. Installation Guidelines for the AppManager 6.0 Operator Console Only if you are installing the AppManager Operator on a Windows Server 2008 operating system, perform the following steps. 1. If the AppManager Suite Version window appears, close it. 2. Open a command prompt. 3. Type the drive letter of the CD-ROM followed by a colon. For example, type D: 4. Type the following command: cd appmanager\setup 5. Press Enter. 6. Type the following command: setup SKIPINSTALLATIONCHECK 7. Press Enter. 8. Follow the on-screen directions and note the following guidelines. When prompted with What AppManager components do you want to install, select only the AppManager Operator Console component

37 Installing or Upgrading Software on the Management Server After the installation is complete, if Internet Information Services (IIS) is installed on your system, ensure that the World Wide Web service is running. If the service is not running, or if you cannot start it, reboot the system Installing AppManager 7.0 Software To install AppManager 7.0, perform the following steps: 1. For installation instructions, refer to the NetIQ AppManager Installation Guide, which is included on the AppManager 7.0. Supplement Software CD-ROM at \appmanager\documentation\install.pdf. 2. Refer to the following guidelines for suggestions about the messages and options that you might encounter. Your installation options depend on the AppManager components that you select. Installation Guidelines for the AppManager 7.0 Management Server If you are upgrading from an earlier version of the AppManager software, you might be asked whether to upgrade or replace existing components. For most components, the difference is not important. You must choose the upgrade option if you want to retain data, jobs, and any customized scripts in the repository. However, the repository upgrade option substantially increases the installation time because upgrading a repository typically takes 3 hours or longer. Installing a new repository usually takes 30 minutes or less. If you have MSDE or SQL Server 2005 Express Edition installed, you must upgrade to the Standard Edition or Enterprise Edition of SQL Server 2000 (Service Pack 3 or later) or SQL Server If you do not have a version of SQL Server installed, you must install one. When prompted to choose between Evaluation or Production mode 1. Click Production. 2. Select all the component check boxes except for the Monitoring Modules check box. Your license does not include any of the monitoring modules. During the AppManager agent installation, if you are prompted with Reporting and Discovery Options, clear the Enable reporting capability check box. If this check box is selected, you must specify a user account for the agent service. It is preferable to run the agent under the default Local System account. At the end of the AppManager installation, click No when prompted to register the product. Your registration is through Unisys, so it is not appropriate to register directly with NetIQ. After the installation is complete, ensure that the World Wide Web service is running. If the service is not running, or if you cannot start it, you must reboot the system