Sentinel Management Server

Transcription

1 Sentinel Management Server Installation, Reinstallation, and Upgrade Guide Server Sentinel and Higher April 2007

2 .

3 unisys imagine it. done. Sentinel Management Server Installation, Reinstallation, and Upgrade Guide Server Sentinel and Higher April

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. AppManager is a registered trademark of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. Knowledge Scripts is a registered trademark 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 Sentinel Management Server Installation, Reinstallation, and Upgrade Guide Server Sentinel and Higher Sentinel Management Server Installation, Reinstallation, and Upgrade Guide Server Sentinel and Higher Bend here, peel upwards and apply to spine.

6 .

7 Contents Section 1. Introduction Procedures in This Guide Understanding Server Sentinel Installation Scenarios Advantages to Using a Server Sentinel Management Server Servers That Can Host Sentinel Management Server Software Section 2. Requirements Management Server Requirements Required Media Configuring the SNMP Service Verifying the Security Policy for Sentinel Management Servers Running Windows XP Professional Cabling the Management Server Required Fixes for Systems Running Server Sentinel 3.x Section 3. Preparing to Upgrade a Sentinel Management Server Isolating the Sentinel 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. Preparing to Manage Systems Running Server Sentinel 3.x and Previous Installing or Upgrading the AppManager Agent on a Partition Installing AppManager Extensions Section 5. Installing, Reinstalling, or Upgrading a Sentinel Management Server Setting Internet Explorer Security Options iii

8 Contents Satisfying Firewall Configuration Requirements Configuring a Default Instance of SQL Server Installing the Management Server Software Installing the Server Sentinel Software Installing Product Documentation and Documentation Tools Reconnecting the Sentinel Management Server to the Network Defining Server Sentinel Users Using Windows on an External Service Processor, Windows Partition, or Workstation Installing Remote Desktop Using an Internet Proxy Server with Server Sentinel Using a Modem Connection for Call Home Configuring and Testing the Modem Modifying the Hosts File to Use a Modem Connection Obtaining Updates Section 6. Adding Systems to Be Monitored Modifying the Sentinel Management Server Hosts File Verifying and Completing Server Sentinel Settings Adding and Configuring Systems to Be Monitored Adding Monitored Systems Verifying and Completing System Definition Verifying and Completing AppManager Setup Verifying Server Configuration Section 7. Completing the Server Sentinel Configuration Verifying Server Sentinel Communication Configuring Server Sentinel Communications Call Home Configuration for Server Sentinel 4.x Systems Configuring Call Home Generator Services Defining the Call Home Central Service Computer Introduction to Sending a Call Home RFU Packet Prerequisites to Use the Internet for Transmissions Identifying the Central Service Connection Method Sending a Call Home RFU Packet Verifying Call Home Changing the Server Sentinel Services Account Password Changing the Account Key Password on a Sentinel Management Server Installing Virus Protection Software Upgrading Client Workstations iv

9 Contents Creating Additional Sentinel Management Servers Appendix A. Firewall Considerations Firewall Requirements for Server Sentinel A 1 Firewall Requirements for Sentinel Management Server A 1 Firewall Requirements for AppManager Management Server A 3 Firewall Requirements for Service Processors A 3 Firewall Requirements for Windows Partitions A 4 Firewall Requirements for Client Workstations A 5 Firewall Requirements for Monitored Servers A 5 Appendix B. Supporting Server Sentinel Software Downloading Server Sentinel Batch Files for Windows Operating Systems B 1 Appendix C. Installing Server Sentinel AppManager Extensions in an Existing AppManager Infrastructure Integrating Server Sentinel into an Existing AppManager Installation C 1 Index v

10 Contents vi

11 Section 1 Introduction This guide provides the information necessary to install, reinstall, and upgrade management server software. This guide is intended for system administrators and Unisys service representatives who are responsible for installing and administering servers. Depending on your particular server model and configuration, some of the procedures or steps in this guide may not apply. Skip the unnecessary procedures and continue with those procedures that apply to your system or situation. Procedures in This Guide This guide enables you to complete the following procedures: Install Sentinel Management Server software and AppManager management server software to create a new Sentinel Management Server and gain the full benefits of Server Sentinel management. Reinstall a previously configured Sentinel Management Server. Upgrade the software on existing Sentinel Management Servers (known as management servers in previous releases). Note: If your current Service Processor also acts as a Sentinel Management Server, you cannot upgrade the management software running on it. You must provide an independent server to act as the Sentinel Management Server if you want to monitor systems running Server Sentinel 4.x. Install the applicable software and fixes to existing systems running earlier versions of Server Sentinel to enable them to be managed by a Server Sentinel 4.x Sentinel Management Server. Understanding Server Sentinel Server Sentinel is a centralized operations environment that provides world-class data center system management capabilities for greater business continuance and system resiliency. Server Sentinel provides management of multiple qualified systems in your environment through the use of Sentinel Management Servers

12 Introduction Note: Earlier releases of Server Sentinel referred to Sentinel Management Servers simply as management servers. A Sentinel Management Server is simply an independent server that is running Sentinel Management Server software. You can have one or more independent servers acting as Sentinel Management Servers in your environment. You can provide your own servers or purchase them from Unisys. (See the Requirements section for more information.) Note that to access the full range of Server Sentinel management capabilities, your environment must also include AppManager management server software. Installation Scenarios There are four basic scenarios that you can follow to obtain the full benefits of a Server Sentinel management: Note: Only one instance of AppManager management server software should be installed in your environment. Install Sentinel Management Server software and AppManager management server software on one independent server in your environment. This option produces one Sentinel Management Server and conserves your hardware resources. Install Sentinel Management Server software on one independent server, and install AppManager management server software on another independent server in your environment. You might want to choose this option, for example, if you are a current customer of NetIQ Corporation and you already have a dedicated server running AppManager software. This option produces one Sentinel Management Server

13 Introduction Note: If you are a current customer of NetIQ Corporation and you want to integrate Server Sentinel with your existing AppManager infrastructure, see Appendix C for more information. Install Sentinel Management Server software and AppManager management server software on one independent server, and install Sentinel Management Server software only on another independent server in your environment. This option produces two Sentinel Management Servers for redundancy. Install AppManager management server software on one independent server, and install Sentinel Management Server software on two independent servers in your environment. You might want to choose this option, for example, if you are a current customer of NetIQ Corporation and you already have a dedicated server running AppManager software. This option produces two Sentinel Management Servers for redundancy. For even greater redundancy or for environments with a large number of systems, you can add any number of Sentinel Management Servers

14 Introduction Advantages to Using a Server Sentinel Management Server A Sentinel Management Server is an optional component, but using a Sentinel Management Server can provide the following advantages: Including a Sentinel Management Server in your environment enables you to obtain the benefits of full Server Sentinel functionality. If you do not include a Sentinel Management Server, only a core set of Server Sentinel functionality is provided by default for platform management. Each Sentinel Management Server can manage up to 50 qualified systems (or 200 operating system instances) that are running Server Sentinel releases 2.0 and higher. Notes: - If a selected system is running a Server Sentinel version prior to 3.0, a new browser instance will open for that system when it is selected. - Systems running different releases of Server Sentinel (3.x versus 4.x) might display the same features in different ways; however, there is no loss of functionality. You can manage systems - Locally, by using Internet Explorer on the Sentinel Management Server to view the status of the systems in your environment - Remotely, by using Internet Explorer on one or more client workstations to connect to the Sentinel Management Server and view the status of the systems in your environment

15 Introduction The Server Sentinel home page offers at-a-glance notification of the status of each monitored system in your enterprise and enables you to conveniently access each system. There is no limit to the number of Sentinel Management Servers that can be included in your environment, and different Sentinel Management Servers can be used to monitor different types of systems. For example, if your current systems are already being managed adequately by an existing Sentinel Management Server, you can create a new Sentinel Management Server to manage only your new systems. For information about the features provided by Server Sentinel when a Sentinel Management Server is not present in your environment, see the Server Sentinel Software Release Announcement. Servers That Can Host Sentinel Management Server Software You can install Sentinel Management Server software and AppManager management server software on any independent server in your environment that meets the appropriate requirements. (See the Requirements section for more information.) You can provide your own hardware, or you can purchase one or more qualified servers from Unisys. If you already have an independent Sentinel Management Server (which might have been referred to simply as a management server in a previous release), you will be able to upgrade its software and use it to manage systems running Server Sentinel 4.x as well as systems running earlier releases of Server Sentinel. Caution If your current Sentinel Management Server is also your external Service Processor, you will have to provide a new Sentinel Management Server if you want to manage systems running Server Sentinel 4.x. You cannot install the 4.x version of Sentinel Management Server software and AppManager management server software on a Service Processor

16 Introduction

17 Section 2 Requirements Management Server Requirements 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 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 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. Windows 2000 Server, with Service Pack 4 Windows 2000 Advanced Server, with Service Pack 4 Windows Server 2003 R2, Standard Edition, with Service Pack 2 Windows Server 2003 R2, Enterprise Edition, with Service Pack 2 Windows XP Professional, with Service Pack 2 Note: If, after you complete the Sentinel Management Server configuration, you decide to upgrade the management server operating system, see Appendix B for information about batch files that you might be required to download. 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

18 Requirements SNMP must be configured on the Sentinel Management Server and on all partitions and Service Processors that it manages. Note: For information on how to configure the SNMP service on 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, partitions, and client workstations) must be the same as the Sentinel Management Server. Unisys systems are installed using the Microsoft workgroup model, meaning that you must configure the same user name, password, and group membership on each component. See your system planning documentation for more information. Internet Information Services (IIS) If you intend to configure the Call Home Central Service from your Sentinel Management Server, hardware and software that enables you to connect to the Internet (either a modem or a network interface card) If a default instance of SQL Server is present, it must be SQL Server 2000 or Microsoft SQL Server Desktop Engine (MSDE). The default instance must be configured to use SQL Server and Windows authentication mode (also known as mixed mode). You can use SQL Server Enterprise Manager to change the authentication mode for a SQL instance. Note: If you do not have SQL Server installed on your system, the Sentinel Management Server installation program installs MSDE, properly configured to use SQL Server and Windows authentication. Required Media The following media are required. Server Sentinel CD/DVD One of the following product documentation CD/DVDs, depending on your enterprise server: - Getting Started CD/DVD - Product Documentation CD/DVD AppManager Supplement CD/DVD 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

19 Requirements 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 an SNMP trap destinations; otherwise, you will not receive all of the applicable data. To configure SNMP, 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: It is recommended that you use public for a community name because most SNMP-enabled management frameworks expect this value. 8. If you want to use public for a community name, verify that it is entered in the Community names 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 names 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. 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. Enter 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

20 Requirements 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 local host and the computer name for each 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. c. Click Add. d. Click OK. 15. Locate SNMP Service in the right pane of the Computer Management window and right-click. 16. Select Restart to restart the service and save your settings. 17. If you are prompted to restart other services, click Yes. 18. Close the Computer Management window. Verifying the Security Policy for Sentinel Management Servers Running Windows XP Professional Note: Perform the following procedure only if your Sentinel Management Server is running Windows XP Professional. In Windows XP Professional, the default security policy is set to Guest only. This setting only enables you to log on to the Sentinel Management Sever 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. The Control Panel displays. 2. Double-click Administrative Tools

21 Requirements The Administrative Tools window displays. 3. Double-click Local Security Policy. The Local Security Settings window displays. 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 select Properties. The Network access: Sharing and security model for local accounts Properties dialog box displays. 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. Cabling the Management Server Antivirus software and Microsoft required hotfixes must be installed on the management server before it is connected to the LAN. After the software and hotfixes are installed, cable the server to the LAN and power it up. Required Fixes for Systems Running Server Sentinel 3.x If you want to manage a system running Server Sentinel 3.x with a 4.x Sentinel Management Server, ensure that your Service Processor is running Firmware Web Services version or higher. If it is not, install the latest Server Sentinel Interim Correction (IC) from the Unisys Support Web page for the Server Sentinel 3.x release that you are currently running. (For example, if your system is currently running Server Sentinel 3.4, install the latest IC from the Server Sentinel 3.4 Support Web page.)

22 Requirements

23 Section 3 Preparing to Upgrade a Sentinel Management Server If you are installing a new Sentinel Management Server in your environment, or if you are reinstalling software on an existing management server running Server Sentinel 4.x software, proceed to the next section. If you are planning to upgrade an existing Sentinel Management Server that is running Server Sentinel 2.x or 3.x software, perform the procedures in this section and then proceed to the next section. Note: If your current Service Processor also acts as a Sentinel Management Server, you must provide a new Sentinel Management Server and follow the installation procedure in the next section; you cannot install the 4.x version of Sentinel Management Server software and AppManager management server software on a Service Processor. Isolating the Sentinel Management Server During Software Installation If you are upgrading an existing Sentinel Management Server, you must isolate it from any Service Processors on the network. If you do not isolate the Sentinel Management Server from these Service Processors, the AppManager software upgrade could fail. Isolate the existing Sentinel Management Server by disconnecting all network cables or by disabling all network interface cards (NICs). Uninstalling the Cisco Security Agent If you are upgrading a management server running Server Sentinel 2.x or 3.x software, 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

24 Preparing to Upgrade a Sentinel Management Server 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, consider the following factors in deciding whether to uninstall the AppManager program: Advantage: The new Server Sentinel 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. Disadvantage: Customized scripts and graph data are deleted. 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. 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 installation of Server Sentinel. 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

25 Preparing to Upgrade a Sentinel Management Server 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 partition and on each available Service Processor to remove cache information related to the old QDB repository database. 1. Ensure that the AppManager agent has been upgraded with the same level of AppManager software running on the management server. 2. On the Start menu, point to Settings, and then click Control Panel. 3. Double-click Administrative Tools and then double-click Services. The Services window is displayed. 4. Right-click NetIQ AppManager Client Resource Monitor Service and click Properties. The Properties dialog box for the service is displayed. 5. Click Stop. 6. Type -o (hyphen, lowercase letter o) in the Start Parameters box. 7. Click Start. Note: You must click Start, not OK. The OK button does not start the service. 8. Click OK to close the Properties dialog box. 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 the 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 the Call Home Generator Service and then click Properties. The Call Home Generator Service Properties dialog box displays. b. On the General tab, select Manual from the Startup type list

26 Preparing to Upgrade a Sentinel Management Server

27 Section 4 Preparing to Manage Systems Running Server Sentinel 3.x and Previous To enable systems running Server Sentinel 3.4 or earlier software to be managed by a 4.x Sentinel Management Server, perform the procedures in this section on each Windows partition. AppManager 6.0 management server software can coexist temporarily with AppManager 4.3 and 5.0.x agents; however, Unisys recommends that you upgrade your AppManager agents at your earliest convenience (for example, as part of a staged roll-out). Upgrading the AppManager agents on all your managed client computers enables you to use the new features included with the latest version of the AppManager program and to obtain the best performance and functionality. Installing or Upgrading the AppManager Agent on a Partition Note: Perform this procedure only on a partition. If the AppManager agent and Operator Console are present on a Service Processor, remove them. Server Sentinel does not support the monitoring of AppManager agents and Operator Consoles on Service Processors. If you remove the AppManager agent, you must also disable the Unisys Health Monitor service if installed. Complete the following steps to install the AppManager agent on a system running an earlier level of Server Sentinel, Server Management Tools, or Enterprise Server Software. Caution To ensure a successful installation, you must follow these instructions step by step. 1. Log on to the Windows environment using a user account that has Administrator privileges on the management server. 2. Verify if any previous version of Server Director or AppManager software is installed on your system by using Control Panel. If a previous version of this software is installed, continue with step 3; otherwise, continue with step

28 Preparing to Manage Systems Running Server Sentinel 3.x and Previous 3. From Control Panel, click Add or Remove Programs and uninstall Any previous version of Server Director or AppManager software that is present The Unisys Server Sentinel managed object, if present 4. Wait until Server Director or the AppManager program is removed completely. 5. Reboot the system. 6. Insert the Unisys Server Sentinel AppManager Supplement Software Version CD-ROM. Note: Do not use the Server Sentinel CD-ROM to install the AppManager agent because Installation Assistant automatically updates the Server Sentinel version at the same time. This action can cause problems when you later install Interim Corrections (ICs). The AppManager Suite screen appears. If this screen does not appear, use Windows Explorer to navigate to the CD-ROM drive, and double-click the file setup.exe. 7. Select the Production tab. 8. Click Begin AppManager Setup. The Welcome dialog box appears. 9. Click Next. The Install AppManager dialog box appears. 10. Select Install Products only. 11. Click Next. The Choose Destination Location dialog box appears. 12. Accept the default destination folder, or click Browse to select a new folder. 13. Click Next. The AppManager Components dialog box appears. 14. Select only the AppManager management agent check box and then click Next. The AppManager Agent Configuration dialog box appears with introductory text that starts with Select the applications and systems you want to monitor on this server. 15. Complete the following steps: a. Ensure that the AppManager Asynchronous Event Receiver check box is selected. b. Clear all the other check boxes in this dialog box. (Licenses for these options expire within 30 days.) c. Click Next. The ResponseTime Module Selection dialog box appears

29 Preparing to Manage Systems Running Server Sentinel 3.x and Previous 16. Clear all the check boxes in this dialog box. (These modules are not included in the basic AppManager license.) Click Next. The AppManager Agent Configuration dialog box appears with introductory text that starts with Select the agent options you want. 17. Accept the following default values: Perform Discovery Use computer name in the Operator Console display Use default RPC port number 18. Clear the following check boxes if selected: Enable MAPI mail as an action Enable Report Agent Enable Remote Agent Capability 19. Click Next. The AppManager Agent Configuration dialog box appears with introductory text that starts with Configure the local repository. 20. Accept the default destination folder, or click Browse to select a new folder. Click Next. The AppManager Agent Configuration dialog box appears with introductory text that starts with Type the domain, user name, and password for the Windows account. 21. Ensure that Use local system account is selected and then click Next. The Windows Security Level Configuration dialog box appears with introductory text that starts with Select the level of security you want to use. 22. Accept the default values and then click Next. The AppManager Agent Configuration dialog box appears with introductory text that starts with Specify the management servers you want. 23. Select I will do this later and then click Next. The installation program begins to copy and install files. During the installation, you might see messages about components that you chose not to install for example, response time modules. Ignore these messages. 24. Click Yes when the following message appears: After you designate a primary and optionally, a secondary management server, do you want to restrict management server communication with this agent? 25. Click OK when the Information: Setup is complete dialog box appears

30 Preparing to Manage Systems Running Server Sentinel 3.x and Previous Installing AppManager Extensions Complete the following steps to install the AppManager extensions: 1. Insert the Server Sentinel CD-ROM that contains the same level of Server Sentinel software running on the partition. The Server Sentinel Software screen of Installation Assistant appears. 2. Click Finished to close Installation Assistant. 3. Double-click the following file on the CD/DVD drive in Windows Explorer: AppManager\OEM\UnisysExtensions.exe The Unisys AppManager Enhancements dialog box appears. The default values displayed in this dialog box vary depending on which AppManager components are already installed on the system. 4. Accept the default values, and click Install even if none of the check boxes are selected. (The program installs other extensions, such as the Unisys managed object, even if no check boxes are selected.) The Installation Status dialog box appears. 5. Click Done. The Installation Assistant status bar message changes to Done. 6. Click Return and then Finished to close Installation Assistant

31 Section 5 Installing, Reinstalling, or Upgrading a Sentinel Management Server Use the procedures in this section to install, reinstall, or upgrade your Sentinel Management Server. Note: If you are upgrading a Sentinel Management Server, ensure that you completed the required procedures in the previous sections, Preparing to Upgrade a Sentinel Management Server and Preparing to Manage Systems Running Server Sentinel 3.x and Previous, before you continue. See Section 1 for more information on installation considerations (for example, whether to install the Sentinel Management Server software and the AppManager management server software on the same server or on different servers). Setting Internet Explorer Security Options Use these steps to set and verify the proper Microsoft Internet Explorer settings: 1. From Internet Explorer, click Internet Options on the Tools menu. The Internet Options dialog box appears. 2. Select the Security tab. 3. Select the Trusted sites icon. 4. Click Sites. The Trusted sites dialog box appears. 5. Make sure the Require server verification ( for all sites in this zone check box is not selected. 6. Add a URL for each Service Processor, management server, and Windows partition. If a Service Processor, management server, or Windows partition is in a different 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, Reinstalling, or Upgrading a Sentinel 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 7. Add an IP address for each Service Processor, management server, partition, and Console Manager (if applicable). Be sure to add an IP address for each Service Processor public LAN (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. 8. Click Close or OK to close the dialog box. 9. Click Custom Level under Security level for this zone. The Security Settings dialog box appears. 10. In the Settings list, ensure that the following settings are selected. Note: Not all of the settings in the following table 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 plugins Miscellaneous 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 Access data sources across domains Navigate sub-frames across different domains Submit nonencrypted form data Enable Enable Enable Enable or Prompt Enable Enable Enable Enable Enable Enable or Prompt Scripting Active scripting Enable or Prompt

33 Installing, Reinstalling, or Upgrading a Sentinel Management Server Note: If the computer accessing Server Sentinel 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. 11. Click OK. If you receive a warning message, click Yes. 12. If you are installing software on Windows XP Service Pack 2 or Windows Server 2003 with Service Pack 1, continue with this step; otherwise, skip to step 14. Select the Advanced tab in the Internet Options dialog box. 13. 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 Note: After you have completed installing software, return these settings to their previous values. 14. 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, perform the following: 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 setting is selected: Category Option Setting ActiveX controls and plugins Initialize and script ActiveX controls not marked as safe Prompt d. Click OK. If you receive a warning message, click Yes. 15. Click OK in the Internet Options dialog box. 16. Close Internet Explorer. Note: Pop-up blockers prevent Server Sentinel from operating properly. To avoid this problem, allow pop-ups from the management server and service processor. For information on allowing pop-ups, refer to the documentation for Internet Explorer or for your third-party software. Satisfying Firewall Configuration Requirements If you do not plan to use a hardware or a software firewall to protect your system connection to the Internet, skip this subsection

34 Installing, Reinstalling, or Upgrading a Sentinel Management Server If you are using the software firewall provided by Windows known as the Windows Firewall you should verify that it is enabled now. The Windows Firewall is available with Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and later operating systems. During the Server Sentinel software installation, the Windows Firewall is automatically configured. If you are using any other hardware or software firewall to protect your system connection to the Internet, refer to Appendix A for prerequisites. Configuring a Default Instance of SQL Server If a default instance of SQL Server is present, it must be SQL Server 2000 or Microsoft SQL Server Desktop Engine (MSDE). The default instance must be configured to use SQL Server and Windows authentication mode (also known as mixed mode). You can use SQL Server Enterprise Manager to change the authentication mode for a SQL instance. Note: If you do not have SQL Server installed on your system, the Sentinel Management Server installation program installs MSDE, properly configured to use SQL Server and Windows authentication. Installing the Management Server Software Use the following procedures to install the management server software. Note that you can install the Sentinel Management Server software and the AppManager management server software on the same server or on different servers, as appropriate for your environment. See Section 1 for more information on possible installation scenarios. Note: If you are a current customer of NetIQ Corporation and you want to integrate Server Sentinel with your existing AppManager infrastructure, see Appendix C for more information. Caution If you previously installed the Sentinel Management Server software and the AppManager management server software on the same physical server, you must upgrade the software together by selecting both of the appropriate checkboxes in the Installation Assistant interface. In Server Sentinel 3.1 and earlier releases, the Sentinel Management Server software and AppManager management server software were installed together by default and therefore must be upgraded together. If you do not install the software together, errors will occur during the installation

35 Installing, Reinstalling, or Upgrading a Sentinel Management Server Installing the Server Sentinel Software Note: Do not install the Server Sentinel software on domain controllers; the software is not qualified for such installation. Prerequisites Prior to installing the Server Sentinel software using Installation Assistant, ensure that the following prerequisites have been met: Internet Explorer security options have been configured. You are logged on to Windows under a user account that has administrator privileges. All clustered Microsoft SQL Server instances are offline. Clustered SQL Server instances interfere with the installation of the SQL Server 2000 Desktop Engine (MSDE). Installation Procedure To access the Installation Assistant interface, either double-click the Sentinel Install Assistant icon if it is available on the desktop or insert the Server Sentinel CD-ROM into the CD/DVD drive. Note: If the autorun option is not set for your CD/DVD, use Windows Explorer to navigate to the CD/DVD drive and double-click the setup.exe file. Install the Server Sentinel software using the following procedure. Note: During the installation process, Installation Assistant attempts to enable the Windows Firewall if it is not already enabled. If Installation Assistant cannot enable the Windows Firewall, you are prompted to enable it. You can either follow the on-screen instructions to enable the Windows Firewall, or you can click OK to continue with the software installation. 1. Ensure that system software requirements for the software that you want to install have been met. System functions that have requirements yet to be satisfied are listed in the right pane and marked with a red triangle. Refer to the Installation help in the left pane of the interface for assistance. 2. Under Select Software to Install, select the appropriate check boxes to specify which Server Sentinel software components to install. You can select more than one of the listed components as appropriate for your environment. Note: Some system functions are automatically detected and selected for installation. 3. If any requirements have not been met, a dialog box appears. Click the red triangles in the right pane and then install the appropriate software. Refer to the Installation help for assistance. 4. If you are prompted to reboot, click Yes. After the reboot is complete, access the Installation Assistant interface

36 Installing, Reinstalling, or Upgrading a Sentinel Management Server 5. Install the Server Sentinel software by clicking one of the following: Recommended Installation The recommended installation procedure automatically installs all appropriate Server Sentinel software using default settings. Refer to the Installation help in the left pane for additional information. Custom Installation If you need to install a subset of the Server Sentinel software or redistributable software manually, such as when reinstalling software, use the custom installation procedure. The custom installation screen enables you to select specific software components to install as well as define a minimal or interactive installation. Refer to the Installation help in the left pane for additional information. Note: If you click Custom Installation, the Installation Assistant does not warn you if installation requirements for the software you are installing have not been met. Ensure that all requirements have been met before clicking Custom Installation. A dialog box that states installation was successful appears. 6. Click OK. 7. Click Finished to close the Installation Assistant interface. 8. If you are prompted to reboot, click Yes. If a reboot does not occur after installation is complete, reboot the system. Installing Product Documentation and Documentation Tools Note: Server Sentinel product documentation is installed automatically when you install the Server Sentinel software using the recommended procedure; this subsection describes how to Install tools that enable you to access and view documentation directly from the desktop of your Sentinel Management Server. Install the product documentation for your enterprise server so that it is accessible from the Server Sentinel interface. To install the applications that enable you to access product documentation from the Sentinel Management Server Windows Start menu, do the following: 1. Insert the CD-ROM that contains your product documentation (depending on your enterprise server, either the Getting Started CD-ROM or Product Documentation CD-ROM) into the CD/DVD drive. Note: On the Getting Started interface, click Related Documents. 2. Follow the on-screen instructions to install or upgrade Adobe Reader and Unisys CDLib Manager. 3. After installing the documentation, exit the installation interface

37 Installing, Reinstalling, or Upgrading a Sentinel Management Server After you complete this procedure, you can view the product documentation for your enterprise server or for Server Sentinel by clicking Start, pointing to Programs, and then pointing to Unisys CD-ROM Library, and then clicking CD-ROM Library. From the CDLib Manager, you can access documentation libraries by clicking Open on the File menu and navigating to the appropriate.mdb file. To install the product documentation for your enterprise server so that it is accessible from the Server Sentinel interface, do the following: 1. On the Start menu, click Run, and then click Browse. 2. Double-click CopyCD.exe. Note: On the Getting Started CD-ROM, the CopyCD.exe file is located in the docs\documentationlibrary directory. The path to the executable file is displayed in the Run dialog. 3. If you receive a message asking if you want to copy the files, click Yes. 4. Click OK when you receive a message that the files have been copied successfully. After you complete this procedure, you can view the product documentation for your enterprise server in addition to the Server Sentinel documentation from the Server Sentinel interface. To do so, starting from the upper-left of the Server Sentinel interface, click Help, click Libraries and tours, and then, under Other Resources, click the product documentation library you want to view. Reconnecting the Sentinel Management Server to the Network Note: Perform this procedure only if you are upgrading an existing Sentinel Management Server. In preparation for upgrading an existing Sentinel Management Server, you were instructed to isolate the management server from all Service Processors on the network by disconnecting all network cables or disabling all network interface cards (NICs). At this time, reconnect the Sentinel Management Server to the network by reconnecting the network cables or enabling all NICs. Defining Server Sentinel Users Using Windows on an External Service Processor, Windows Partition, or Workstation To define Server Sentinel users (administrators, operators, and observers) on an external Service Processor, Windows Partition, or workstation, perform the steps that follow. For more information on Server Sentinel users, refer to the Server Sentinel User s Guide. Perform this procedure on each Windows computer from which you plan to access Server Sentinel

38 Installing, Reinstalling, or Upgrading a Sentinel Management Server 1. On the desktop, right-click My Computer, and then click Manage. The Computer Management window opens. 2. In the left pane, expand Local Users and Groups. 3. Select Users. 4. Right-click in the right pane of the window and click New User. 5. In the New User dialog box, enter information as appropriate for your Server Sentinel user role. Clear the User must change password at next logon check box and select the Password never expires check box. Note: Nonblank passwords are required. 6. Click Create. 7. Repeat steps 5 through 6 to add all the users that will be placed in the Server Sentinel administrators, operators, and observers groups. 8. Close the New User dialog box. 9. In the left pane, select Groups. 10. Define the users for the following Server Sentinel groups by selecting the group in the right pane, right-clicking it, and then clicking Add to Group. Note: You can add users to the following local groups directly or create domain groups to help manage user access: Administrators Sentinel Observers Sentinel Operators The Properties dialog box for the selected Server Sentinel group appears. 11. To add a user to the Server Sentinel group, click Add. A Select Users dialog box appears. 12. Type a valid user name in the Enter the object names to select box and click OK. 13. Click Apply in the Properties dialog box. 14. Repeat steps 10 through 13 for each Server Sentinel group and then click OK. 15. Click OK in the Properties dialog box. 16. Close the Computer Management window. Installing Remote Desktop Remote Desktop is required to gain access to the embedded Service Processor desktop. If your system does not have Remote Desktop, download the Remote Desktop Connection Client from and follow the Microsoft installation instructions

39 Installing, Reinstalling, or Upgrading a Sentinel Management Server Using an Internet Proxy Server with Server Sentinel Several components of Server Sentinel including Call Home, Health Advisor, and EZupdate require access to the Internet. If you are using a proxy server (for example, Microsoft Internet Security and Acceleration (ISA) Server), Server Sentinel must be able to use that proxy server to access Unisys Web sites. If your proxy server supports Web Proxy Autodiscovery (WPAD) and does not require authentication, Server Sentinel can automatically use it to access the Internet. If your proxy server does not support WPAD, or if it requires authentication, you must do the following: Specify the user account that Server Sentinel will use to authenticate itself to the proxy server. Configure the specific proxy server connection settings. Specifying an Account to Authenticate Server Sentinel If your proxy server does not support WPAD, or if it requires authentication, use the Server Sentinel Account Maintenance utility as follows to configure an account to authenticate Server Sentinel: 1. On the Start menu, point to Programs, point to Unisys Server Sentinel, and then click Configure Proxy Server Credentials. 2. Select Use the following credentials. 3. Type the appropriate usercode in the Enter proxy usercode box. This usercode can be either a local machine account (for example, Bob) or a domain account (for example, MyDomain\Bob). 4. Type the appropriate password for the usercode in the Enter proxy password box. 5. Click Update. Note: If the password for this account changes, you must repeat this procedure to update the account information. Configuring the Proxy Server Connection Settings After you use the Server Sentinel Account Maintenance utility to configure an account to authenticate Server Sentinel, do the following to configure the proxy server connection settings: 1. Log on to your Sentinel Management Server using the account you specified through the Server Sentinel Account Maintenance utility. 2. On the Start menu, point to Settings, and then click Control Panel. Control Panel is displayed. 3. Double-click Internet Options. The Internet Properties dialog box is displayed

40 Installing, Reinstalling, or Upgrading a Sentinel Management Server 4. Select the Connections tab. 5. Click LAN Settings. The Local Area Network (LAN) Settings dialog box is displayed. 6. Configure the settings in the dialog box to match your network configuration. 7. Click OK to close the Local Area Network (LAN) Settings dialog box. 8. Click OK to close the Internet Properties dialog box. 9. Close Control Panel. Note: The Sentinel Management Server provides Internet access through the proxy server only for systems that it is managing (Service Processors, partitions, and the management server itself). To determine whether updates are required for systems that are not managed by the Sentinel Management Server, such as Server Sentinel monitored servers or client workstations, you must log on to those systems with credentials that are acceptable to the proxy server so that you can access the Internet. After you have access to the Internet, you can run EZupdate from the Start menu. Using a Modem Connection for Call Home If you are using the Call Home Central Service on the Sentinel Management Server you are configuring, and if you plan to use a modem connection, perform the steps in the following subsection. Note: The preferred method for Call Home to access the Unisys Support Center is through an Internet connection. Configuring and Testing the Modem If you are using a modem connection for Call Home, do the following steps to configure and test your modem. Ensure the USB modem is connected to your USB port before performing this procedure. If you are using an Internet connection, skip this procedure. 1. On the Start menu, point to Programs, Unisys Server Sentinel, and then click Create Call Home Dial-up. The Create Phonebook Entry dialog box appears. 2. Select a modem from the Modems list. 3. Select your country from the Location list. 4. Type a prefix in the Prefix box if you need to enter a number to access an external line. 5. Click Generate String. A Unisys Support Center telephone number appears in the Dial String box. 6. Verify that the dial string is correct for your environment. 7. Click Create Entry

41 Installing, Reinstalling, or Upgrading a Sentinel Management Server The dial-up connection is created. 8. Click OK to close the confirmation window. 9. Test the connection you just created by clicking Test Dial-up Connection. 10. From the Connect Support Center window, click Dial. Do not change the User name or Password; otherwise, the dial-up will fail. 11. Verify that the connection is made by doing the following: a. From the Create Phonebook Entry dialog box, click Show Dial-up Connections. b. From the Network Connections window, select View/Refresh. If a connection is made, you can see a new connection labeled SupportCenter in the Network Connections window. c. Right-click SupportCenter and click Disconnect. d. Click View/Refresh to verify that you are disconnected from the Support Center. 12. Close the Network Connections dialog box. 13. Click Close in the Create Phonebook Entry dialog box. Modifying the Hosts File to Use a Modem Connection Perform the following steps prior to sending a Call Home ready-for-use (RFU) packet and service request packets through a USB modem. Depending on where Call Home Central Service is installed, such as the Service Processor or Sentinel Management Server, modify the Hosts file so that Call Home uses the modem connection. 1. On a workstation, maximize the Remote Desktop window for either the Service Processor or the Sentinel Management Server. 2. On the Start menu on your Service Processor or Sentinel Management Server, click Run. The Run dialog box appears. 3. Type the following line: notepad %systemroot%\system32\drivers\etc\hosts. 4. Click OK. The Hosts file opens. 5. Add the following line to the end of the file: callhome.unisys.com Note: This line starts in column one. There is no space between call and home. 6. Save the file and close Notepad

42 Installing, Reinstalling, or Upgrading a Sentinel Management Server Obtaining Updates If updates to the Server Sentinel software and platform firmware are available, you can download them by using the Server Sentinel EZupdate feature or by using the Unisys Product Support Web site. Internet Access Requirements Depending on your system, Internet access is required to obtain updates through EZupdate, as summarized in the following table. Server Sentinel Level Management Server, Client Workstation, and Monitored Server Service Processor Partition 3.x Access required. Access required. 4.0 and 4.1 Access required. Not supported; use the Product Support Web site. 4.2 and higher Access required. Access required only if no management server is available. Access required. Access required only if no management server is available. Access not required. If you access EZupdate from the Start menu, the system must have Internet access. EZupdate Support for Partitions EZupdate is supported on partitions running the following Intel processors and Server Sentinel levels: Itanium processor family and Server Sentinel 4.3 and higher Itanium 2 processor and Server Sentinel 4.3 and higher Xeon processor x86 and any supported level of Server Sentinel Xeon processor x64 and Server Sentinel 4.0 and higher Obtaining Updates Using EZupdate EZupdate periodically checks the Unisys Product Support Web site for available updates to Server Sentinel and platform firmware and notifies you if updates are available. You can access EZupdate from the Server Sentinel user interface on all systems as outlined in the preceding table. This is the preferred method

43 Installing, Reinstalling, or Upgrading a Sentinel Management Server Alternatively, to access EZupdate from Service Processors, client workstations, monitored servers, or management servers, click the Start menu, point to Programs and then Unisys Server Sentinel, and click EZupdate. Internet access is required if you use this method. If updates are available on client workstation or monitored server desktops, the EZupdate icon is displayed in the system tray, and a balloon message appears periodically until you download the available updates or choose to be reminded at another time. If updates are available on the Server Sentinel user interface, the EZupdate Available icon is prominently displayed. Perform the following steps to download the available updates using the EZupdate feature of Server Sentinel: 1. Perform one of the following steps: Click the following Configuration Summary icon: The Configuration Summary page appears. Select System Tools, and click EZupdate. Click the EZupdate Available icon. Depending on your system, the View Latest Report page or the System Report page appears. 2. Click Task Help in the upper-right corner for more information on downloading and installing the updates. 3. Copy the files to all systems that need software or firmware updates. 4. Be sure to update all partitions when you update the software and platform firmware on Service Processors, client workstations, monitored servers, and management servers. Obtaining Updates Using the Unisys Product Support Web Site If your system does not include access to the Internet, you can download Server Sentinel software and platform firmware updates from the Unisys Product Support Web site by using a workstation that is connected to the Internet. Updates to Server Sentinel software and platform firmware are available in the form of Interim Corrections (ICs) and quick-fix releases (QFRs). ICs and QFRs are replacement modules that contain fixes for your software or platform firmware. Any customer with a maintenance agreement is entitled to use these modules. To access the latest updates and apply them to your system, perform the following steps: 1. If necessary, close all Server Sentinel windows before installing Server Sentinel updates. 2. Access the Unisys Product Support Web site at

44 Installing, Reinstalling, or Upgrading a Sentinel Management Server 3. Sign on to entitled support with your user name and password. If you do not have a user name and password, click Register. The Product Support page appears. 4. Select a system type and click Go. The support page for that system is displayed. 5. Click Releases. The releases for the system are displayed. 6. In the Fixes column, select the relevant release. A list of the latest available updates appears. 7. Select the appropriate update from the list. The Download Interim Correction page appears. 8. Click the link labeled View Profile of IC to get a description of the update and installation instructions. Click Back to return to the Download Interim Correction page. 9. Click the link under File Description to download the update

45 Section 6 Adding Systems to Be Monitored Follow the procedures in this section to add systems to be monitored by your 4.x Sentinel Management Server. Note that if you simply upgraded the software on your Sentinel Management Server and you do not have additional systems that you want to monitor, you can skip this section. Modifying the Sentinel Management Server Hosts File Note: Perform the following steps only if your system does not use DNS. Perform the following procedure to modify the Sentinel Management Server hosts file: 1. On the Start menu, click Run. The Run dialog box appears. 2. Type the following: notepad %systemroot%\system32\drivers\etc\hosts 3. Click OK. The hosts file opens. 4. Modify or add information for each Service Processor using the static address and host name. For example: sp Add information for each partition using the assigned static IP address and the partition host name. For example: partition0. Note: If you intend to change the partition host name and IP address later in this configuration, use the new host name and IP address for the partition when modifying the hosts file. Repeat this step for each partition. 6. Save the hosts file and close Notepad

46 Adding Systems to Be Monitored Verifying and Completing Server Sentinel Settings Note: If you configured your system using the Server Sentinel Setup Assistant, and if your initial configuration has not changed, you do not need to perform this procedure; it will be performed automatically when you monitor a system. Perform the following procedure to verify and complete the Server Sentinel settings. 1. If the Server Sentinel user interface is not already open, on the Start menu of the Sentinel Management Server, point to Programs, point to Unisys Server Sentinel, and then click Navigation. 2. If you are prompted, accept the Sun Microsystems license agreement and click Submit. 3. From the upper left of the Server Sentinel user interface, click the Configuration Summary icon: 4. Select Server Sentinel Settings from the Configure menu. The Server Sentinel Settings page appears. 5. Ensure that the following settings have the correct values assigned to them as applicable to your environment. Update the settings as required. Server Sentinel Settings SNMP ReadOnly Community String EZupdate Transport Protocol AppManager User Logon Name AppManager User Logon Password Value The default ReadOnly community string for your environment. This value is typically public. The transport protocol that you want EZupdate to use. The choices are http (Hypertext Transport Protocol) or https (Hypertext Transport Protocol Secure sockets). The user name that you want to use to log on to the AppManager repository (the SQL or MSDE default instance). The default user name is sa. Ensure that this is the same user name you assigned when installing the AppManager software. The password you want to use to log on to the AppManager repository (the SQL or MSDE default instance). The default password for a new installation is SentinelPasswordForSA. If you previously installed AppManager, ensure that this is the same password you assigned when installing the AppManager software

47 Adding Systems to Be Monitored Server Sentinel Settings Confirm AppManager User Logon Password AppManager Location AppManager Repository Name AppManager Web Management Server Location Value Confirm the password you want to use to log on to AppManager. Ensure that this is the same password you assigned when installing the AppManager software. The location of the AppManager repository that was defined when you installed the AppManager software. The name of the AppManager repository that was defined when you installed the AppManager software. This value is typically QDB. The location of the AppManager Web Management server. This is usually the same as the AppManager repository location. 6. If you made any changes, click Update. Adding and Configuring Systems to Be Monitored Perform the procedures in this subsection to add and configure a system to be monitored by your Sentinel Management Server. You should repeat these procedures, beginning with Adding Monitored Systems, for each system that you want to monitor. Adding Monitored Systems Note: Refer to the Task Help available from the Server Sentinel interface for assistance with completing this procedure. Use the following procedure to specify which systems you want the Sentinel Management Server to monitor: 1. If the Server Sentinel user interface is not already open, open Internet Explorer from a management server or a workstation and type <Management Server host name>/sentinel in the Address box. 2. If prompted, enter your Administrator user name and password. 3. If prompted, accept the Sun Microsystems license agreement and click Submit. 4. From the upper left of the Server Sentinel user interface, click the Configuration Summary icon: The Configuration Summary window appears. 5. On the toolbar, select Configure and then select Systems List. The Configured Systems Information window appears

48 Adding Systems to Be Monitored 6. Click Add a System. The Add Monitored System dialog box appears. 7. Type the master Service Processor name or IP address, and click Add. 8. If prompted, enter your Administrator user name and password. 9. On the toolbar, select Configuration Summary and then select Server Sentinel Settings. Verify that the Server Sentinel settings are correct. If the settings are not correct, update them as applicable for your environment. 10. Close the Configuration Summary window. Verifying and Completing System Definition Note: Partitions running MCP, OS 2200, and Linux operating systems and 64 bit partitions will not have their component information automatically discovered; you must enter information for those partition types manually using the following procedure. Perform the following procedure to verify, and if necessary complete, the Server Sentinel software configuration: 1. If the Server Sentinel navigation interface is not already open, on the Start menu of the Sentinel Management Server, point to Programs, point to Unisys Server Sentinel, and then click Navigation. 2. Click the system name. 3. Select System Configuration. 4. Select System definition. 5. Verify the following for each partition: a. Computer name b. IP address c. Console Manager IP address, if applicable d. SNMP ReadOnly Community String 6. If you need to correct any information or add missing information, do the following: Note: The component information that you can edit or delete is identified by Edit and Delete links in the Options column of the tables. After you click Edit, information fields that you can edit or delete are identified by an asterisk (*). a. Click Edit in the Options column. b. Enter your changes. c. Click Save Changes. Note: Anytime you change the network configuration for a partition for example, the IP address, host name, or SNMP settings you should verify and complete the System Definition settings as described previously

49 Adding Systems to Be Monitored Verifying and Completing AppManager Setup Perform the following procedures to verify, and if necessary complete, AppManager setup: 1. On the Start menu (on the management server that contains the AppManager repository), point to Programs, NetIQ, AppManager, and then click Operator Console. 2. Log on to the AppManager Operator Console. 3. On the Master tab, ensure that all Windows partitions appear and that they have the Unisys server object included (when each is expanded). If necessary, add a computer by performing the following steps: a. Right-click Master in the TreeView pane. b. Click Add Computer. The Add Computer dialog box appears. c. Type the computer name. d. Ensure that the Discover Windows objects automatically check box is selected. e. Click OK. The discovery process might take several minutes. 4. For each added computer, ensure that Windows objects such as CPU, memory, and others appear. If these objects are not present, then run the NT discovery script by completing the following steps: a. In the right pane, select the Discovery tab. b. Select the NT script in the right pane, and drag it to the desired computer object in the TreeView pane. 5. For each added computer, ensure that a Unisys Server object appears. If this object is not present, then run the Unisys discovery script by completing the following steps: a. In the right pane, select the Discovery tab. b. Select the Unisys script in the right pane, and drag it to the desired computer object in the TreeView pane. 6. Close the AppManager Operator Console window. Verifying Server Configuration The Server Sentinel Configuration Verification can be used to display a report of your server configurations and report potential problems with software installation, configuration, and networking

50 Adding Systems to Be Monitored To verify configuration of your server, use the following procedure: 1. If the Server Sentinel navigation interface is not already open, on the Start menu of the Sentinel Management Server, point to Programs, point to Unisys Server Sentinel, and then click Navigation. 2. Click the system name. 3. From the navigation interface, select Health Reporting. 4. Select Configuration verification. A report is displayed, summarizing the configuration of your server and noting where potential problems could occur. Review the report and correct any problems as applicable for your environment

51 Section 7 Completing the Server Sentinel Configuration Perform the procedures in this section to complete the Server Sentinel configuration when you are installing, reinstalling, or upgrading a Sentinel Management Server. Verifying Server Sentinel Communication If you configured your system using the Server Sentinel Setup Assistant (a configuration tool available with some enterprise sever models that include Server Sentinel 4.x), and if your initial configuration has not changed, you do not to verify the Server Sentinel communication. If your initial configuration did not include the Server Sentinel Setup Assistant or if your configuration has changed since your initial installation, verify that the following services are running in the Computer Management window: Sentinel Communication Channel Sentinel Remote Library Configuring Server Sentinel Communications Use this procedure to configure ports that enable communications between Server Sentinel components. Note: Execute this procedure on Windows partitions, Service Processors, and Sentinel Management Servers running Server Sentinel 4.0 and higher. A firewall might be installed between one or more of these components. If a firewall exists, the ports must also be opened in the firewall. 1. Navigate to C:\Program Files\Unisys\Server Sentinel\Infrastructure. 2. Double-click the file configure_ports.vbs to run the script. The Server Sentinel Communication Channel window appears. The current port value or the default port value 182 appears in the edit box. 3. If you do not use the default port value, enter a port value between 0 to 65535, and click OK. This port number must be identical for all systems in the enterprise. The Server Sentinel Remote Library window appears. The current port value or the default port value appears in the edit box

52 Completing the Server Sentinel Configuration 4. If you do not use the default port value, enter a port value between 0 to 65535, and click OK. This port number must be identical for all systems in the enterprise. 5. If either port value is changed, the corresponding service is updated and restarted. Messages appear confirming the restart of one or both of the following services: Sentinel Communication Channel Sentinel Remote Library 6. Click OK to acknowledge the notification. Call Home Configuration for Server Sentinel 4.x Systems Using the Sentinel Management Server, perform the procedures in the following subsection to configure Call Home on systems running Server Sentinel 4.x. Note: You must repeat this procedure for each system running Server Sentinel 4.x. Configuring Call Home Generator Services Perform the following steps to configure the installed Generator services: 1. Use Server Sentinel to access the Call Home Service Request Status page for your system. 2. Ensure that All Systems is select in the Show Service Requests from list. 3. Click Generator and then List of Generator Services. 4. From the List of Generator Service Computers page, click Update List. This refreshes the list of computers to ensure that the computers being installed is correctly listed. 5. On the List of Generator Service Computer page, click the name of the computer where the Generator Service is installed. The Configure the Generator Service page appears. Note: If the message Connect() failed is displayed, wait a couple of minutes and then repeat this step. 6. Fill in the required Generator Service information fields, each of which is marked with an asterisk (*). You can refer at any time to the Call Home online help for information you might need on fields or other elements of the interface. Notes: The System Information, Customer Information, and Central Service Information fields must be filled in. For the Central Service Information fields, supply the correct primary computer name. Type in the name of the Sentinel Management Server as the primary computer if a Sentinel Management Server is part of your system; otherwise, type in the name of the master Service Processor as the primary computer

53 Completing the Server Sentinel Configuration 7. Click Submit. Defining the Call Home Central Service Computer The Call Home Central Service records service request packet information in a database and delivers the packets to the Unisys Support Center. The Central Service can be installed on both the Service Processor and the Sentinel Management Server; however, one Central Service must be identified as the primary and the other as the secondary. It is recommended that the Central Service on the Sentinel Management Server be identified as primary for all systems running Server Sentinel 4.0 or higher. Note: Do not perform this procedure on systems running versions of Server Sentinel prior to Service Sentinel 4.0. To identify or change the Central Service primary location, do the following: 1. Using Server Sentinel, select a system from the Systems list. 2. Click Call Home to expand the list of Call Home options. 3. Click Send test service request. The List of Generator Service Computers page appears. 4. Click the name of a listed computer. The Configure the Generator Service page appears. 5. Scroll down to the Central Service Information group. Verify that the name of the Sentinel Management Server is in the Primary box and the name of the Service Processor is in the Secondary box. If those names are not present, add them. 6. Repeat steps 4 and 5 until you have identified the primary and secondary Central Service for all of the listed computers. 7. Click Submit. The identity of the primary Central Service is important because the history and status of service request packets are sent only to the primary Central Service. If the primary Central Service was initially on the Service Processor and then changed to the Sentinel Management Server, the history and status of service request packets sent from the Service Processor would not be visible from the Central Service on the Sentinel Management Server. Introduction to Sending a Call Home RFU Packet Sending a Call Home ready-for-use (RFU) packet ensures that the Call Home communication is working and enables you to verify whether the test packet was received by the Support Center. Use the Internet connection (the recommended method) or a modem to send a Call Home RFU packet. Ensure that the following conditions are met for the selected connection method

54 Completing the Server Sentinel Configuration Prerequisites to Use the Internet for Transmissions For Call Home, Call Home Health Advisor, EZupdate, and Remote Support to access the Unisys Product Support Web site using the Internet, the following ports must be opened: Call Home Health Advisor protocol HTTPS: - Port IP address Call Home protocol HTTPS and SSL: - Hostname: callhome.unisys.com o Port 443 o IP address Hostname: o Port 5700 o IP address EZupdate protocol (select one) - If using HTTPS: port 443 and IP address If using HTTP: port 80 and IP address Remote support protocol HTTPS: - Port IP address Note: Ports can be set to outbound only for Unisys purposes. Identifying the Central Service Connection Method Perform the following steps to identify the Central Service connection method through Call Home Central Service. 1. Use Server Sentinel to access the Call Home Service Request Status page for your system. 2. Click the Central Service tab and select Configure Central Service. 3. On the Connection Method group, choose a connection method (Internet or USB modem) and click Apply. For more configuration information, refer to the task specific help available for this page. Sending a Call Home RFU Packet After meeting the conditions for the Internet or for the modem connection, perform the following steps to send the Call Home RFU packet:

55 Completing the Server Sentinel Configuration 1. Use Server Sentinel to access the Call Home Service Request Status page for your system. 2. Click List of Generator Services on the Generator menu. The List of Generator Service Computers page appears. 3. Click Update List. Wait a few seconds before proceeding with the next step. 4. Click Ready. This action routes RFU packets to the Unisys Support Center for the partitions and Service Processors. 5. Click Status. The Call Home Service Request Status page appears. 6. Verify that the RFU packet was received by the Unisys Support Center and that a success acknowledgment (SACK) message has been returned. RFU packet status is indicated in the Status column. The page refreshes periodically to update the displayed status. If the packet does not transfer correctly, ensure that the information for each generator service is complete. Select the Diagnostics tab on the Call Home page for more information. Verifying Call Home Verify the overall Call Home operations on the enterprise server by sending a test packet from each computer with a Generator Service installed. 1. Using Server Sentinel, select a system from the Systems list. 2. Click Call Home to expand the list of Call Home options. 3. Click Send test service request. The list of Generator Service Computers page appears. 4. For each of the computers listed on this page, click Send Test Packet. Wait for the progress bar to complete before clicking Send Test Packet for the next generator computer. 5. Click Status. 6. Verify that the test packet was sent to the support center and that a SACK response has been received. Test packet status is indicated in the Status column. For example, a notation in the Status column for the test packet should indicate that the send process has been completed and that a SACK message was returned by the support center

56 Completing the Server Sentinel Configuration Changing the Server Sentinel Services Account Password The Server Sentinel Services Account is created and configured as part of the recommended Server Sentinel installation on computers running Server Sentinel 4.0 and higher. After the initial Server Sentinel installation, the account is configured with a default key and password. Some Server Sentinel components installed as Windows services are configured to run under this account and use the credentials of this account to communicate with components on other systems. The account key is used to programmatically generate a secure password. When you update the account key, you are indirectly changing the password on the account. You are strongly encouraged to change this default key as soon as possible. For Server Sentinel components to successfully authenticate components on other systems, the account key must be identical on all computers that include the Server Sentinel Services Account feature. Changing the Account Key Password on a Sentinel Management Server Note: The Server Sentinel Services Account feature is available only on computers running Server Sentinel 4.0 and higher. 1. From the upper left of the Server Sentinel navigation, click the Configuration Summary icon. The Configuration Summary screen appears. 2. Click Configure Server Sentinel Services Account on the System Tools menu. The Change Password screen appears. 3. For more instructions on changing the default key, click Task Help in the upper-right corner. Installing Virus Protection Software Virus protection software is not provided with the operating system of your server components. You can purchase and install any virus protection software you prefer. Virus protection software and Microsoft required hotfixes must be installed before connecting to the public LAN IP address (DHCP server). Once they are installed, cable your server component to the public LAN. Some virus protection software can interfere with the installation of other software. If you encounter problems with the installation of any software, disable virus protection before you retry the installation. Be sure to enable virus protection again after you complete installation

57 Completing the Server Sentinel Configuration Upgrading Client Workstations If your environment includes any Server Sentinel client workstations, you should ensure that they are running the same version of Server Sentinel as the Sentinel Management Server. If they are not, refer to the Server Sentinel Client Workstation Installation and Reinstallation Guide for more information about how to install the latest Server Sentinel client workstation software. Creating Additional Sentinel Management Servers Repeat the applicable procedures in this document to install, reinstall, or upgrade additional Sentinel Management Servers. Note: Only one instance of AppManager management server software should be installed in your environment. See Section 1 for more information

58 Completing the Server Sentinel Configuration

59 Appendix A Firewall Considerations Use the information in this appendix to configure any hardware or software firewall other than the Windows Firewall. Firewall Requirements for Server Sentinel To ensure that Server Sentinel functions properly, configure your software or hardware firewall such that traffic is not blocked between system components where Server Sentinel is installed. If you use Windows Firewall, the Server Sentinel Installation Assistant automatically configures the firewall. If you install Windows Firewall after installing Server Sentinel, download the Server Sentinel batch files from the Unisys Product Support Web site to update your firewall rules. If you use a firewall from another vendor, ensure that your firewall is configured for Server Sentinel network traffic. If multiple types of Server Sentinel software (for example, Sentinel Management Server software and Server Sentinel client workstation software) are installed on the system, adhere to the firewall requirements for all installed Server Sentinel software. Note that the client workstation is defined as any terminal used to access Server Sentinel remotely. Notes: The firewall requirements are for incoming traffic; most outgoing traffic use dynamic ephemeral ports, and these requirements are not documented. %Program Files% is a path variable to the file location, for example: C\Program Files\... Firewall Requirements for Sentinel Management Server The following firewall requirements apply to your Server Sentinel software: Allow HTTP traffic through port 80. Traffic comes from client workstations. Allow file and print sharing. Traffic comes from client workstations A 1

60 Firewall Considerations Allow remote desktop connections. Traffic comes from client workstations. Allow a ping request for network diagnostics. Allow remote procedure call (RPC) on TCP port 135. Traffic comes from partitions. Allow the following applications, or open SNMP and SNMP trap User Datagram Protocol (UDP) ports 161 and 162: %Program Files%\Unisys\Server Sentinel \Management Server\System Management\SAServer.exe %Windows%\system32\snmptrap.exe Traffic comes from partitions and Service Processors. Allow the following Server Sentinel authenticated communication applications, or open TCP ports 182 and 62182: %Program Files%\Unisys\Server Sentinel \Infrastructure\Datapath.Service.exe %Program Files%\Unisys\Server Sentinel \Infrastructure\RemoteLibrary.Server.exe Note: Default port values might have been overridden during installation. If the default values are not used, be sure to use the port values that were specified during installation. Traffic comes from all managed Windows partitions and Service Processors. Traffic might also come from client workstations accessing the navigation Web interface. Allow the following application: %Program Files%\Unisys\Server Sentinel \Processor Autonome\GroupManager.exe Traffic is bidirectional with the Windows partition or partitions that the application is configuring. If the management server has a Call Home Central Service receiving data from systems running Server Sentinel 3.x, allow the following application or open TCP port 7896: %Program Files%\Unisys\Server Sentinel \Call Home\Central Service\CHCS.exe Traffic comes from Call Home Generator Services running Server Sentinel 3.x on partitions or Service Processors. A

61 Firewall Considerations Firewall Requirements for AppManager Management Server The following firewall requirements apply to your AppManager software: Allow HTTP traffic through TCP port 80. Traffic comes from client workstations. Allow the following AppManager application or open TCP port 9998: %Program Files%\NetIQ\AppManager\bin\NetIQms.exe Traffic comes from managed Windows partitions and Service Processors running Server Sentinel 3.x. Allow the following AppManager application or open TCP port 8996: %Program Files%\NetIQ\AppManager\bin\NetIQctrl.exe Traffic comes from client workstations. Allow the following AppManager repository or open TCP port 1433: %Program Files%\Microsoft SQL Server\Mssql\ Binn\MSSQL\Binn\SqlServer.exe Traffic comes from client workstations. Firewall Requirements for Service Processors The following firewall requirements apply to your Server Sentinel software: Allow HTTP traffic through port 80. Traffic comes from client workstations and management servers. Allow file and print sharing. Traffic comes from client workstations. Allow remote desktop connections. Traffic comes from client workstations. Allow a ping request for network diagnostics and failover. Allow RPC from TCP port 135. Traffic is bidirectional between master and standby Service Processors. Allow the following Server Sentinel authenticated communication applications, or open TCP ports 182 and 62182: %Program Files%\Unisys\Server Sentinel\ Infrastructure\Datapath.Service.exe %Program Files%\Unisys\Server Sentinel\ Infrastructure\RemoteLibrary.Server.exe A 3

62 Firewall Considerations Note: Default port values might have been overridden during installation. If the default values are not used, be sure to use the port values that were specified during installation. Traffic comes from management servers managing the Service Processor and Windows partitions. Traffic might also come from client workstations accessing Server Sentinel. Firewall Requirements for Windows Partitions The following firewall requirements apply to your Server Sentinel software: Note: All requirements apply to IA-32, x64, and Itanium 2-based partitions, except where noted. Allow remote desktop connections. Traffic comes from client workstations. Allow file and print sharing. Traffic comes from client workstations. Allow a ping request for network diagnostics. Allow the following Server Sentinel authenticated communication applications, or open TCP ports 182 and 62182: %Program Files%\Unisys\Server Sentinel \Infrastructure\Datapath.Service.exe %Program Files%\Unisys\Server Sentinel \Infrastructure\RemoteLibrary.Server.exe Note: Default port values might have been overridden during installation. If the default values are not used, be sure to use the port values that were specified during installation. Traffic comes from the Service Processor and from any management servers managing this partition. It might also come from client workstations. Allow the following application, or open SNMP and SNMP trap UDP ports 161 and 162: %WINDOWS%\system32\snmp.exe Traffic comes from localhost and management servers. Allow platform tools RPC traffic by opening TCP ports 7970 through Set the following registry keys under HKLM\Software\Microsoft\RPC\Internet: - Ports (REG_MULTI_SZ) = PortsInternetAvailable (REG_SZ) = Y - UseInternetPorts (REG_SZ) = Y Traffic comes from client workstations. A

63 Firewall Considerations Allow the following Resource Manager engine application or open port (IA-32 partitions only): %Program Files%\Common Files\Unisys \Resource Manager\ResourceManager20.Host.exe Traffic comes from client workstations and management servers that are configuring processor affinity. Allow the following application (IA-32 partitions only): %Program Files%\Unisys\Server Sentinel \Processor Autonome\GroupManager.exe Traffic is bidirectional with the Windows partition or partitions that the application is configuring. Allow the following AppManager application or open TCP port 9998: %Program Files%\NetIQ\AppManager\bin\NetIQmc.exe Traffic comes from the AppManager management server. Allow the following AppManager application or open TCP port 8996: %Program Files%\NetIQ\AppManager\bin\NetIQctrl.exe Traffic comes from the AppManager management server and client workstations. Firewall Requirements for Client Workstations Allow the following executable file: %Program Files%\Unisys\Server Sentinel\ Processor Autonome\GroupManager.exe Traffic is bidirectional with the Windows partition or partitions that the application is configuring. Firewall Requirements for Monitored Servers The following firewall requirements apply to your Server Sentinel software: Allow remote desktop connections. Traffic comes from client workstations. Allow the following Server Sentinel authenticated communication applications, or open TCP ports 182 and %Program Files%\Unisys\Server Sentinel\ Infrastructure\Datapath.Service.exe %Program Files%\Unisys\Server Sentinel\ Infrastructure\RemoteLibrary.Server.exe Note: Default port values might have been overridden during installation. If the default values are not used, be sure to use the port values that were specified during installation A 5

64 Firewall Considerations Traffic comes from the computer hosting the Call Home Central Service that is managing this server. A

65 Appendix B Supporting Server Sentinel Software If you install Server Sentinel software and later install Microsoft Windows Professional XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1, you must complete the following procedure. Downloading Server Sentinel Batch Files for Windows Operating Systems On any component that already has Server Sentinel software installed, if you install or reinstall a Windows operating system that supports the Windows Firewall, you must then download the Server Sentinel batch files. (The Windows Firewall was first supported with Windows XP Professional with Service Pack 2 and Windows 2003 with Service Pack 1.) The batch files automatically update the required registry and Windows firewall settings. If you do not ever plan to use the Windows Firewall, you do not need to download the batch files. Do not perform this procedure if a Windows operating system that supports the Windows Firewall is installed and the Windows Firewall is enabled prior to installing Server Sentinel. You can download the required batch files and a readme file containing the batch file installation instructions from the Unisys Product Support Web site by performing the following steps: 1. Access the Unisys Product Support Web site at 2. Log in with your user name and password. The Product Support page is displayed. 3. Select Server Sentinel in the Systems Management list under the Solutions products. The Server Sentinel Support page is displayed. 4. Click Releases. The Releases page is displayed. 5. Click your Server Sentinel release in the Release column. The Release page for the release you selected is displayed. 6. Click Batch Files under the Software tab to display the available batch files. 7. Click your release level in the Level column. The Batch Files page for the release level you selected is displayed B 1

66 Supporting Server Sentinel Software 8. Click the link labeled Downloadable Files under Download Information. A File Download dialog box is displayed. 9. Click Save and specify a location where you want to save the batch files. 10. Open the downloaded file, specify a location to unzip the files, and then click Unzip. The batch files and a readme file are copied to the location that you specified. 11. Follow the instructions in the readme file to run the batch files. B

67 Appendix C Installing Server Sentinel AppManager Extensions in an Existing AppManager Infrastructure If you are a current customer of NetIQ Corporation with an AppManager management server, use the following information to help you install the required Server Sentinel AppManager extensions in your environment. Note that you must also install the Sentinel Management Server software in your environment, either to your AppManager management server or to another server that meets the software requirements. See Section 5 for more information about installing this software. Integrating Server Sentinel into an Existing AppManager Installation If you are adding a system that supports the AppManager program to a data center that includes servers that are not Unisys servers but are already managed by the AppManager software program, then the new system can be managed by your existing AppManager management server. However, the AppManager management server must be running AppManager version 6.0. The following steps describe how to integrate Server Sentinel into an existing AppManager installation. 1. Insert the Server Sentinel CD-ROM in the CD/DVD drive of your existing AppManager management server. The Server Sentinel Software screen appears. 2. Under Software to Install, click Custom Installation C 1

68 Installing Server Sentinel AppManager Extensions in an Existing AppManager Infrastructure Caution Do not choose a recommended installation of the AppManager management server. Such a choice permanently deletes your existing repository and any custom Knowledge Scripts or changed parameters that you have stored in the repository. 3. Click the documentation icon (?) next to AppManager Extensions. The Installing AppManager Extensions help topic appears. 4. Follow the instructions in the help topic to install the AppManager extensions. 5. Optionally, you can perform a recommended installation of the Sentinel Management Server on the same system, as long as the system prerequisites are satisfied. For information on recommended installations, click the documentation icon (?) next to Recommended Installation. 6. Perform recommended installations of AppManager components on your external Service Processor (if appropriate) and partitions. 7. When asked for the name of the AppManager management server, type the name of your existing AppManager management server. 8. If you have other systems that are running the AppManager Operator Console, then complete the following steps for each system: a. Close the AppManager Operator Console, if it is running. b. Insert the Server Sentinel CD-ROM into the CD/DVD drive. The Server Sentinel Software screen appears. c. Under Software to Install, click Custom Installation. d. Under Sentinel Software, click AppManager Extensions. This action installs the Unisys extensions to the AppManager Operator Console. e. Respond to any message as documented in the associated help topic. Tip: To open the help topic, click the documentation icon (?). C

69 Index A account key password changing, 7 6 adding monitored systems, 6 3 Sentinel Management Server, 6 3 additional Sentinel Management Servers, 7 7 AppManager firewall requirements, A 3 installing agent on partition, 4 1 installing extensions, 4 4 uninstalling from management server, 3 2 upgrading agent on partition, 4 1 verifying setup on Service Processor, 6 5 B batch files for Windows downloading, B 1 C cabling the management server, 2 5 Call Home Central Service connection method, 7 4 configuring Generator Services, 7 2 defining the Central Service computer, 7 3 firewall prerequisites to use the Internet, 7 4 modify the Hosts file for using a modem, 5 11 sending RFU packet, 7 3, 7 4 verifying, 7 5 Central Service defining, 7 3 changing password Server Sentinel Services Account, 7 6 Cisco Security Agent uninstalling, 3 1 client workstation firewall requirements, A 5 completing System Definition, 6 4 configuring Internet proxy server, 5 9 configuring SNMP, 2 2 D defining Server Sentinel users, 5 7 documentation installing, 5 6 downloading updates, 5 12 E extensions, AppManager installing, 4 4 EZupdate obtaining updates with, 5 12 F firewall AppManager requirements, A 3 client workstation requirements, A 5 monitored server requirements, A 5 requirements, 5 3 Sentinel Management Server requirements, A 1 Server Sentinel requirements, A 1 Service Processor requirements, A 3 Windows partition requirements, A 4 G Generator Services configuring on the Sentinel Management Server, 7 2 I installing AppManager extensions, 4 4 installing management server software, 5 4 installing product documentation, 5 6 installing QFR, Index 1

70 Index installing Server Sentinel, 5 5 Internet Explorer setting security options, 5 1 Internet firewall requirements, 5 3 Internet proxy server, 5 9 M management server cabling, 2 5 installing, 5 4 requirements, 2 1 uninstalling AppManager, 3 2 uninstalling Server Director, 3 2 modem configuring and testing, 5 10 modifying Sentinel Management Server hosts file, 6 1 monitored server firewall requirements, A 5 P partition upgrading agent, 4 1 partition monitoring, 6 4 password change Server Sentinel Services account, 7 6 pop-up windows allowing, 5 1 product documentation installing, 5 6 proxy server, 5 9 Q QFR installing, 2 5 R Remote Desktop installing, 5 8 required media, 2 2 requirements firewalls, 5 3 management server, 2 1 security, 2 4 server, 1 5 S security policy, 2 4 Sentinel Management Server adding monitored systems, 6 3 defining the Call Home Central Service computer, 7 3 requirements, 2 1 Sentinel Management Server hosts file modifying, 6 1 Sentinel Management Servers creating additional, 7 7 server configuration verifying, 6 5 Server Director uninstalling from management server, 3 2 server requirements, 1 5 Server Sentinel configuring communication ports, 7 1 defining users, 5 7 firewall requirements, A 1 firmware updates, 5 12 installing, 5 5 software updates, 5 12 using with a proxy server, 5 9 verifying server configuration, 6 5 Server Sentinel Services Account changing password, 7 6 Service Processor firewall requirements, A 3 verifying AppManager setup, 6 5 verifying Call Home, 7 5 SNMP configuring, 2 2 support obtaining updates, 5 12 System Definition, 6 4 U understanding Server Sentinel, 1 1 uninstalling AppManager management server, 3 2 uninstalling Cisco Security Agent, 3 1 uninstalling Server Director management server, 3 2 upgrading AppManager agent on partition, 4 1 users defining, 5 7 Index

71 Index V verifying and completing AppManager setup, 6 5 verifying server configuration Server Sentinel, 6 5 virus protection software installing, 7 6 W Windows downloading batch files, B 1 firewall requirements, A 4 Windows XP Professional requirements, Index 3

72 Index Index

73 .

74 2007 Unisys Corporation. All rights reserved. * *