Sentinel Management Server

(1)

Sentinel Management Server

Installation, Reinstallation, and Upgrade Guide

Server Sentinel 4.4.3 and Higher

April 2007

(2)

(3)

Sentinel Management Server

Installation, Reinstallation, and Upgrade Guide

Server Sentinel 4.4.3 and Higher

unisys

imagine it. done.

April 2007 3850 8024–005

(4)

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

(5)

Sentinel Management

Server

Installation, Reinstallation, and Upgrade Guide

Server Sentinel 4.4.3 and Higher

3850 8024–005

Sentinel Management Server Installation, Reinstallation, and Upgrade Guide

Server Sentinel 4.4.3 and Higher

3850 8024–005

Bend here, peel upwards and apply to spine.

(6)

(7)

Service Processor, Windows Partition, or Workstation . . . 5–7 Installing Remote Desktop . . . 5–8 Using an Internet Proxy Server with Server Sentinel . . . 5–9 Using a Modem Connection for Call Home . . . 5–10 Configuring and Testing the Modem . . . 5–10 Modifying the Hosts File to Use a Modem Connection . . 5–11 Obtaining Updates . . . 5–12

Section 6. Adding Systems to Be Monitored

Modifying the Sentinel Management Server Hosts File . . . 6–1 Verifying and Completing Server Sentinel Settings . . . 6–2 Adding and Configuring Systems to Be Monitored . . . 6–3 Adding Monitored Systems . . . 6–3 Verifying and Completing System Definition . . . 6–4 Verifying and Completing AppManager Setup . . . 6–5 Verifying Server Configuration . . . 6–5

Section 7. Completing the Server Sentinel Configuration

Verifying Server Sentinel Communication . . . 7–1 Configuring Server Sentinel Communications . . . 7–1 Call Home Configuration for Server Sentinel 4.x Systems . . . 7–2 Configuring Call Home Generator Services . . . 7–2 Defining the Call Home Central Service Computer . . . 7–3 Introduction to Sending a Call Home RFU Packet . . . 7–3

Prerequisites to Use the Internet for

Transmissions. . . 7–4 Identifying the Central Service Connection

Method . . . 7–4 Sending a Call Home RFU Packet . . . 7–4 Verifying Call Home . . . 7–5 Changing the Server Sentinel Services Account Password . . . 7–6

Changing the Account Key Password on a Sentinel

Management Server . . . 7–6 Installing Virus Protection Software . . . 7–6 Upgrading Client Workstations . . . 7–7

(9)

Creating Additional Sentinel Management Servers . . . 7–7

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 . . . 1 Contents

(10)

(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)

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)

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.

Introduction

(14)

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)

• 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.

Introduction

(16)

(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)

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 6.0.2 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)

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 theComputer Management window.

2. In the left pane, expandServices and Applications and click the Services icon.

3. In the list of services in the right pane, right-clickSNMP Service and click Properties.

TheSNMP Service Properties dialog box appears.

4. Select theAgent tab.

5. Type a value in theContact box.

This string value indicates the person to contact if an error is found with the system.

6. Type a value in theLocation box.

This string value indicates the physical and logical location of the system.

7. Select theTraps 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 theSecurity tab.

11. Ensure that theSend 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. ClickAdd in the Accepted community names box.

b. Enter the community name in theCommunity Name box.

c. Select READ ONLY from theCommunity rights list.

d. ClickAdd.

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.

Requirements

(20)

a. ClickAdd in the Accepted community names box.

b. Type a community name in theCommunity Name box. (This value is specific for your site, and it is case-sensitive.)

c. Select READ WRITE from theCommunity rights list.

d. ClickAdd.

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 selectedAccept SNMP packets from any host, the configuration is complete. ClickOK.

If you selectedAccept 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. ClickAdd below the Accept SNMP packets from these hosts value.

TheSNMP Service Configuration dialog box appears.

b. In theHost name, IP, or IPX Address box, type the appropriate computer name.

c. ClickAdd.

d. ClickOK.

15. LocateSNMP Service in the right pane of the Computer Management window and right-click.

16. SelectRestart to restart the service and save your settings.

17. If you are prompted to restart other services, clickYes.

18. Close theComputer 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 theStart menu, point to Settings, and then click Control Panel.

TheControl Panel displays.

2. Double-clickAdministrative Tools.

(21)

TheAdministrative Tools window displays.

3. Double-clickLocal Security Policy.

TheLocal Security Settings window displays.

4. In the left pane, expandLocal Policies if it is not already expanded.

5. In the left pane, selectSecurity Options if it is not already selected.

6. In the right pane, right-clickNetwork access: Sharing and security model for local accounts and select Properties.

TheNetwork access: Sharing and security model for local accounts Properties dialog box displays.

7. Verify that the value in the drop-down menu is set toClassic - local users authenticate as themselves. If it is not, update the setting.

8. ClickOK to close the Properties dialog box.

9. Close theLocal Security Settings window.

10. Close theAdministrative 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 1.0.5 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.)

Requirements

(22)

(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 theStart menu, point to Settings and click Control Panel.

2. Double-clickAdd/Remove Programs and remove Cisco Security Agent.

3. Close the Add/Remove Programs window.

4. Restart the server and log on.

(24)

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:

2. Double-clickAdministrative 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. ClickStop.

5. Right-click the Enterprise Server Directory service and then clickStop.

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.

8. Double-clickAdd/Remove Programs and uninstall NetIQ AppManager or Server Director.

(25)

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.

3. Double-clickAdministrative Tools and then double-click Services.

The Services window is displayed.

4. Right-clickNetIQ AppManager Client Resource Monitor Service and click Properties.

TheProperties dialog box for the service is displayed.

5. ClickStop.

6. Type-o (hyphen, lowercase letter o) in the Start Parameters box.

7. ClickStart.

Note: You must click Start, not OK. The OK button does not start the service.

8. ClickOK 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 theComputer Management window, select Services and Applications.

2. Right-click theCall Home Generator Service and then click Stop.

3. Verify that the Startup Type isManual. If the Startup Type is not Manual, do the following:

a. Right-click theCall Home Generator Service and then click Properties.

TheCall Home Generator Service Properties dialog box displays.

b. On the General tab, selectManual from the Startup type list.

Preparing to Upgrade a Sentinel Management Server

(26)

(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 6.

(28)

3. FromControl 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).

TheAppManager 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 theProduction tab.

8. ClickBegin AppManager Setup.

TheWelcome dialog box appears.

9. ClickNext.

TheInstall AppManager dialog box appears.

10. SelectInstall Products only.

11. ClickNext.

TheChoose Destination Location dialog box appears.

12. Accept the default destination folder, or clickBrowse to select a new folder.

13. ClickNext.

TheAppManager Components dialog box appears.

14. Select only theAppManager management agent check box and then click Next.

TheAppManager 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 theAppManager 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. ClickNext.

TheResponseTime Module Selection dialog box appears.

(29)

16. Clear all the check boxes in this dialog box. (These modules are not included in the basic AppManager license.) ClickNext.

TheAppManager 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. ClickNext.

TheAppManager Agent Configuration dialog box appears with introductory text that starts with “Configure the local repository.″

20. Accept the default destination folder, or clickBrowse to select a new folder. Click Next.

TheAppManager Agent Configuration dialog box appears with introductory text that starts with “Type the domain, user name, and password for the Windows account.”

21. Ensure thatUse local system account is selected and then click Next.

TheWindows 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 clickNext.

TheAppManager Agent Configuration dialog box appears with introductory text that starts with “Specify the management servers you want.″

23. SelectI 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. ClickYes 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. ClickOK when the Information: Setup is complete dialog box appears.

Preparing to Manage Systems Running Server Sentinel 3.x and Previous

(30)

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. ClickFinished to close Installation Assistant.

3. Double-click the following file on the CD/DVD drive in Windows Explorer:

AppManager\OEM\UnisysExtensions.exe

TheUnisys 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 clickInstall 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.)

TheInstallation Status dialog box appears.

5. ClickDone.

The Installation Assistant status bar message changes toDone.

6. ClickReturn 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, clickInternet Options on the Tools menu.

TheInternet Options dialog box appears.

2. Select theSecurity tab.

3. Select theTrusted sites icon.

4. ClickSites.

TheTrusted sites dialog box appears.

5. Make sure theRequire server verification (https:) 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 theAdd this Web site to the zone box, enter one URL, for example, http://computername.

b. ClickEnter or Add.

c. Repeat steps a and b until you have added each URL.

(32)

Note: If you are running Internet Explorer on a management server or Service Processor, repeat steps a and b to add the URL http://localhost/.

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 theAdd this Web site to the zone box, enter one IP address, for example, http://192.168.1.100.

b. ClickEnter or Add.

c. Repeat steps a and b until you have added each IP address.

8. ClickClose or OK to close the dialog box.

9. ClickCustom Level under Security level for this zone.

TheSecurity Settings dialog box appears.

10. In theSettings 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 plug- ins

Automatic prompting for ActiveX controls

Enable

Binary and script behaviors Enable Download signed ActiveX controls Enable Download unsigned ActiveX

controls

Enable or Prompt Initialize and script ActiveX controls

not marked as safe

Enable

Run ActiveX controls and plug-ins Enable Script ActiveX controls marked safe

for scripting

Enable

Miscellaneous Access data sources across domains

Enable

Navigate sub-frames across different domains

Enable

Submit nonencrypted form data Enable or Prompt

Scripting Active scripting Enable or

Prompt

(33)

Note: If the computer accessing Server Sentinel is not in the same intranet zone as the management server or Service Processor being accessed, selectAutomatic Logon with current username and password under User Authentication to avoid being prompted for credentials.

11. ClickOK. 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 underSecurity:

• 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 theInternet icon on the Security tab.

b. ClickCustom Level under Security levels for this zone.

TheSecurity Settings dialog box appears.

c. In theSettings list, ensure that the following setting is selected:

Category Option Setting

ActiveX controls and plug- ins

Initialize and script ActiveX controls not marked as safe

Prompt

d. ClickOK. If you receive a warning message, click Yes.

15. ClickOK 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.

Installing, Reinstalling, or Upgrading a Sentinel Management Server

(34)

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 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 theSentinel 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. UnderSelect 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, clickYes. After the reboot is complete, access the Installation Assistant interface.

(36)

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 clickingCustom Installation.

A dialog box that states installation was successful appears.

6. Click OK.

7. ClickFinished to close the Installation Assistant interface.

8. If you are prompted to reboot, clickYes. 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)

After you complete this procedure, you can view the product documentation for your enterprise server or for Server Sentinel by clickingStart, pointing to Programs, and then pointing toUnisys CD-ROM Library, and then clicking CD-ROM Library. From the CDLib Manager, you can access documentation libraries by clickingOpen 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 theStart menu, click Run, and then click Browse.

2. Double-clickCopyCD.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, clickYes.

4. ClickOK 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, clickHelp, 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)

1. On the desktop, right-clickMy Computer, and then click Manage.

The Computer Management window opens.

2. In the left pane, expandLocal Users and Groups.

3. SelectUsers.

4. Right-click in the right pane of the window and clickNew User.

5. In theNew User dialog box, enter information as appropriate for your Server Sentinel user role. Clear theUser must change password at next logon check box and select thePassword never expires check box.

Note: Nonblank passwords are required.

6. ClickCreate.

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 theNew User dialog box.

9. In the left pane, selectGroups.

10. Define the users for the following Server Sentinel groups by selecting the group in the right pane, right-clicking it, and then clickingAdd 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

TheProperties dialog box for the selected Server Sentinel group appears.

11. To add a user to the Server Sentinel group, clickAdd.

ASelect Users dialog box appears.

12. Type a valid user name in theEnter the object names to select box and click OK.

13. ClickApply in the Properties dialog box.

14. Repeat steps 10 through 13 for each Server Sentinel group and then clickOK.

15. ClickOK 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 www.microsoft.com and follow the Microsoft installation instructions.

(39)

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 theStart menu, point to Programs, point to Unisys Server Sentinel, and then clickConfigure Proxy Server Credentials.

2. SelectUse the following credentials.

3. Type the appropriate usercode in theEnter 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 theEnter proxy password box.

5. ClickUpdate.

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.

Control Panel is displayed.

3. Double-clickInternet Options.

(40)

4. Select theConnections tab.

5. ClickLAN Settings.

TheLocal Area Network (LAN) Settings dialog box is displayed.

6. Configure the settings in the dialog box to match your network configuration.

7. ClickOK to close the Local Area Network (LAN) Settings dialog box.

8. ClickOK 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 theStart menu, point to Programs, Unisys Server Sentinel, and then click Create Call Home Dial-up.

TheCreate Phonebook Entry dialog box appears.

2. Select a modem from theModems list.

3. Select your country from theLocation list.

4. Type a prefix in thePrefix box if you need to enter a number to access an external line.

5. ClickGenerate String.

A Unisys Support Center telephone number appears in theDial String box.

6. Verify that the dial string is correct for your environment.

7. ClickCreate Entry.

(41)

The dial-up connection is created.

8. ClickOK to close the confirmation window.

9. Test the connection you just created by clickingTest Dial-up Connection.

10. From the Connect Support Center window, clickDial.

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 theCreate Phonebook Entry dialog box, click Show Dial-up Connections.

b. From the Network Connections window, selectView/Refresh.

If a connection is made, you can see a new connection labeled SupportCenter in the Network Connections window.

c. Right-clickSupportCenter and click Disconnect.

d. ClickView/Refresh to verify that you are disconnected from the Support Center.

12. Close theNetwork Connections dialog box.

13. ClickClose 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 theStart menu on your Service Processor or Sentinel Management Server, click Run.

TheRun dialog box appears.

3. Type the following line:

notepad ″%systemroot%\system32\drivers\etc\hosts.″ 4. ClickOK.

The Hosts file opens.

5. Add the following line to the end of the file:

129.225.192.40 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)

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.

Access required.

4.0 and 4.1 Access required. Not supported;

use the Product Support Web site.

Access required only if no management server is available.

4.2 and higher 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)

Alternatively, to access EZupdate from Service Processors, client workstations, monitored servers, or management servers, click theStart 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, theEZupdate 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 followingConfiguration Summary icon:

The Configuration Summary page appears.

SelectSystem Tools, and click EZupdate.

• Click theEZupdate Available icon.

Depending on your system, the View Latest Report page or the System Report page appears.

2. ClickTask 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.

(44)

3. Sign on to entitled support with your user name and password. If you do not have a user name and password, clickRegister.

The Product Support page appears.

4. Select a system type and clickGo.

The support page for that system is displayed.

5. ClickReleases.

The releases for the system are displayed.

6. In theFixes 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 labeledView Profile of IC to get a description of the update and installation instructions. ClickBack to return to the Download Interim Correction page.

9. Click the link underFile 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 theStart menu, click Run.

TheRun dialog box appears.

2. Type the following:

notepad “%systemroot%\system32\drivers\etc\hosts”

3. ClickOK.

The hosts file opens.

4. Modify or add information for each Service Processor using the static address and host name. For example:

192.168.222.1 sp-123456789-0.

5. Add information for each partition using the assigned static IP address and the partition host name. For example:

192.168.222.201 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.