Dell OpenManage Server Administrator Version 7.0 Installation Manual

Download

Page 1

Dell OpenManage Server

Administrator

Version 7.0

Installation Guide

Page 2

Notes and Cautions

NOTE: A NOTE indicates important information that helps you make better use of

your computer.

CAUTION: A CAUTION indicates potential damage to hardware or loss of data if

instructions are not followed.

___________________

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell™, the DELL™ logo, PowerEdge™, and OpenManage™ are trademarks of Dell Inc. Microsoft

are either trademarks or registered trademarks of Microsoft Corporation in the United States

Server and/or other countries. Java

are registered trademarks of Novell, Inc. in the United States and other countries. Red Hat®and

SUSE Red Hat Enterprise Linux countries. VMware Server™ is a trademark of VMware Inc in the United States and/or other jurisdictions. Citrix and XenServer States and/or other countries. Altiris™ is a trademark of Altiris, Inc.

Server Administrator includes software developed by the Apache Software Foundation (apache.org). Server Administrator utilizes the OverLIB JavaScript library.

Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

2012 –

is a registered trademark and VMware vSphere, ESX Server™ and ESXi

are either registered trademarks or trademarks of Citrix Systems, Inc. in the United

, Windows®, Internet Explorer®, Active Directory® and, Windo ws

is a registered trademark of Oracle and/or its affiliates. Novell® and

are registered trademarks of Red Hat, Inc. in the United States and other

, Xen®,

Page 3

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9

Dell OpenManage Systems Management Software . . . 9

Security Features

. . . . . . . . . . . . . . . . . . . . 13

Other Documents You Might Need . . . . . . . . . . . 13

Getting Technical Assistance

. . . . . . . . . . . . . . 15

2 Preinstallation Setup. . . . . . . . . . . . . . . . 17

Prerequisite Checker . . . . . . . . . . . . . . . . . . 17

Installation Requirements . . . . . . . . . . . . . . . . 21

Supported Operating Systems and Web Browsers

Multilingual User Interface Support

. . . . . . . . 21

Viewing Localized Versions of the Web-Based Interface

System Requirements. . . . . . . . . . . . . . . . 22

Digital Certificates

. . . . . . . . . . . . . . . . . 24

Enabling Windows Installer Logging Service

Microsoft Active Directory . . . . . . . . . . . . . 26

Configuring the SNMP Agent . . . . . . . . . . . . . . 26

Secure Port Server and Security Setup

Setting User and Server Preferences

X.509 Certificate Management

. . . . . . . . . 26

. . . . . . . 27

. . . . . . . . . . . 29

. . . 25

Remote Enablement Requirements

. . . . . . . . . . . 29

Contents 3

Page 4

Installing WinRM . . . . . . . . . . . . . . . . . . 30

Certificate Authority — Signed/Self-Signed Certificate 30

Dependent RPMs for Remote Enablement

Post-Installation Configuration for Remote Enablement

. . . . . 36

Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems

. . . . . . . . . . . 40

Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating System

. . . . . . . . . . . 42

Workaround for the Libssl Issue

. . . . . . . . . . . . . 42

3 Installing Managed System Software on Microsoft

Windows Operating Systems . . . . . . . . . 45

Deployment Scenarios for Server Administrator. . 45

Installing Server Administrator . . . . . . . . . . . . . 47

Typical Installation

Custom Installation . . . . . . . . . . . . . . . . . 48

Server Administrator Installation With Citrix Application Server 50

Performing an Unattended Installation of Managed System Software

. . . . . . . . . . . . . . . . . . . . . . 51

Managed System Software Installation Using Third-Party Deployment Software

System Recovery on Failed Installation

Failed Updates

Upgrading Managed System Software . . . . . . . . . 61

Upgrading Guidelines

Upgrade

Modify

Repair

. . . . . . . . . . . . . . . . . . . . . . . 62

. . . . . . . . . . . . . . . . . . . . . . . . 62

. . . . . . . . . . . . . . . . . . . . . . . . 64

. . . . . . . . . . . . . . . . . 47

. . . . . . . . . . . . . . . . 59

. . . . . . . . . 59

. . . . . . . . . . . . . . . . . . . 60

. . . . . . . . . . . . . . . . 61

4 Contents

Page 5

Uninstalling Managed System Software . . . . . . . . 64

Uninstalling Managed System Software Using Dell-Provided

. . . . . . . . . . . . . . . . . . . . . . . . 65

Media

Uninstalling Managed System Software Features Using the Operating System

. . . . . . . . . . . . . . . . . . 66

Unattended Uninstall Using the Product GUID. . . 66

Unattended Uninstallation of Managed System Software

4 Installing Managed System Software on

Supported Linux and VMware ESX . . . . . 69

Software License Agreement . . . . . . . . . . . . . . 71

Server Administrator Device Drivers

Dynamic Kernel Support

. . . . . . . . . . 71

. . . . . . . . . . . . . . 72

OpenIPMI Device Driver. . . . . . . . . . . . . . . . . 75

Degradation of Functionality When the Server Administrator Instrumentation Service is Started

Installing Managed System Software

. . . . . . . . . 75

. . . . . . . . . . 76

Prerequisites for Installing Managed System Software

Installing Managed System Software Using Dell-Provided Media 77

Server Administrator Custom Installation Utility . . 82

Managed System Software Installation Using Third-Party Deployment Software

Uninstalling Managed System Software

. . . . . . . . . . . . . . . 85

. . . . . . . . 85

Uninstalling Managed System Software Using the Uninstall

. . . . . . . . . . . . . . . . . . . . . . . . 85

Script

Uninstalling Managed System Software Using the RPM Command

. . . . . . . . . . . . . . . . . . . . . . 85

Contents 5

Page 6

5 Installing Managed System Software On

Microsoft Windows Server 2008 Core and

Microsoft Hyper-V Server . . . . . . . . . . . . 87

Running Prerequisite Checker In CLI Mode . . . . 87

Installing Managed System Software in CLI Mode

Uninstalling Systems Management Software

. . . 88

. . . . . . 88

6 Installing Dell OpenManage Software on VMware

ESXi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Using the vSphere CLI . . . . . . . . . . . . . . . 89

Using the VMware vSphere Management Assistant (vMA) 90

Enabling Server Administrator Services on the Managed System 91

Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi4.0/ESXi 4.1)

Enabling CIM OEM Providers Using vSphere CLI (for VMware ESXi 4.0/ESXi 4.1)

Enabling CIM OEM Providers Using vMA (for VMware ESXi

4.0/ESXi 4.1) . . . . . . . . . . . . . . . . . . . . . 93

Configuring the SNMP Agent on Systems Running VMware ESXi

Configuring Your System to Send Traps to a Management Station Using the vSphere CLI

Troubleshooting

. . . . . . . . . . . . . . . . . . 92

. . . . . . . . . . . . . . . . . . 93

. . . . . . . . . . . . . . . 94

. . . . . . . . . . . . . . . . . . . . . 96

7 Installing Dell OpenManage Software on Citrix

XenServer . . . . . . . . . . . . . . . . . . . . . . . . 97

6 Contents

Post Installation Tasks . . . . . . . . . . . . . . . . . . 99

Page 7

8 Using Microsoft Active Directory . . . . . 101

Controlling Access to Your Network . . . . . . . . . . 101

Active Directory Schema Extensions

Overview of the Active Directory Schema Extensions

. . . . . . . . . . 101

102

Extending the Active Directory Schema . . . . . . . . 109

Using the Dell Schema Extender

. . . . . . . . . . 110

Active Directory Users and Computers Snap-In . . 115

Adding Users and Privileges to Active Directory

Configuring Your Systems or Devices

. . . . . . . 119

. 117

9 Frequently Asked Questions . . . . . . . . . 121

General. . . . . . . . . . . . . . . . . . . . . . . . . . 121

Microsoft Windows

. . . . . . . . . . . . . . . . . . . 122

Red Hat Enterprise Linux or SUSE Linux Enterprise Server 130

A Dell OpenManage Linux Installer Packages 145

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Contents 7

Page 8

8 Contents

Page 9

Introduction

This guide provides information on:

• Installing Dell OpenManage Server Administrator (OMSA) on managed systems.

• Installing and using the Remote Enablement feature.

• Managing remote systems using OpenManage Server Administrator Web Server.

• Configuring your system before and during a deployment or upgrade.

NOTE: If you are installing management station and managed system software on

the same system, install identical software versions to avoid system conflicts.

Dell OpenManage Systems Management Software

Dell OpenManage systems management software is a suite of applications that enables you to manage your Dell systems with proactive monitoring, notification, and remote access.

Dell OpenManage systems management software comprises of three DVDs:

•

Dell Systems Management Tools and Documentation

•

Dell OpenManage Server Update Utility

•

Dell Management Console

NOTE: For more information on these DVDs, see the Dell OpenManage

Management Station Software Installation Guide at

support.dell.com/support/edocs/software/omswrels/index.htm.

Server Administrator Components on a Managed System

The setup program provides the following options:

•

Custom Setup

•

Ty p ic al Se tu p

Introduction 9

Page 10

The custom setup option enables you to select the software components you want to install. Table 1-1 lists the various managed system software components that you can install during a custom installation. For more information, see "Custom Installation."

Table 1-1. Managed System Software Components

Component What is installed Deployment scenario Systems on which

to be installed

Server Administrator Web Ser v e r

Server Instrumentation

Web-based systems management functionality that enables you to manage systems locally or remotely

Server Administrator CLI and Instrumentation Service

Install only if you want to remotely monitor the managed system. You need not have physical access to the managed system.

Install to use your system as the managed system. Installing Server Instrumentation and the Server Administrator Web Server installs Server Administrator. You can use Server Administrator to monitor, configure, and manage your system.

NOTE: If you choose to

install only Server Instrumentation (without selecting Remote Enablement), you must also install the Server Administrator Web Server.

Any system. For example, laptops, desktops, or Dell PowerEdge systems.

Supported Dell PowerEdge systems. For a list of supported Dell PowerEdge systems, see the

Dell Systems Software Support Matrix at

support.dell.com/ support/edocs/ software/ omswrels.

10 Introduction

Page 11

Table 1-1. Managed System Software Components

Component What is installed Deployment scenario Systems on which

Storage Management

Remote Enablement

Server Administrator Storage Management

Server Administrator CLI and Instrumentation Service and CIM Provider

Install to implement hardware RAID solutions and configure the storage components attached to your system. For more information on Storage Management, see the

Dell OpenManage Server Administrator Storage Management User’s Guide

in the docs directory or at support.dell.com/support/ edocs/software/omswrels.

Install to perform remote systems management tasks. You can install Remote Enablement on your system and install only the Server Administrator Web Server on another system (say, system X). You can then use system X to remotely monitor and manage your system. You can use system X to manage any number of systems on which Remote Enablement is installed.

(continued)

to be installed

Only those systems on which you have installed Server Instrumentation or Remote Enablement.

Supported Dell PowerEdge systems. For a list of supported Dell PowerEdge systems, see the

Dell Systems Software Support Matrix at

support.dell.com/ support/edocs/ software/ omswrels.

Introduction 11

Page 12

Table 1-1. Managed System Software Components

Component What is installed Deployment scenario Systems on which

Remote Access Controller

Intel SNMP Agent

Broadcom SNMP Agent

Server Administrator CLI and Instrumentation Service and iDRAC or DRAC 5, or DRAC 4 (depending on the type of your Dell PowerEdge system)

Intel Simple Network Management Protocol (SNMP) Agent

Broadcom SNMP Agent

Install to receive e-mail alerts for warnings or errors related to voltage, temperature, and fan speed. Remote Access Controller also logs event data and the most recent crash screen (available only on systems running Microsoft Windows operating system) to help you diagnose the probable cause of a system crash.

Install to enable Server Administrator to obtain information about Network Interface Cards (NICs).

Install to enable Server Administrator to obtain information about NICs.

(continued)

to be installed

Only those systems on which you have installed Server Instrumentation or Remote Enablement.

Only on Dell PowerEdge systems on which Server Instrumentation is installed and which are running on Microsoft Windows operating system.

12 Introduction

Page 13

Security Features

Dell OpenManage systems management software components provide the following security features:

• Authentication for users through hardware-stored user IDs and passwords, or by using the optional Microsoft Active Directory.

• Support for Network Information Services (NIS), Winbind, Kerberos, and Lightweight Directory Access Protocol (LDAP) authentication protocols for Linux operating systems.

• Role-based authority that allows specific privileges to be configured for each user.

• User ID and password configuration through the web-based interface or the command line interface (CLI), in most cases.

•SSL encryption (

NOTE: Telnet does not support SSL encryption.

• Session time-out configuration (in minutes) through the web-based interface.

• Port configuration to allow Dell OpenManage systems management software to connect to a remote device through firewalls.

NOTE: For information about ports that the various Dell OpenManage systems

management components use, see the User Guide for that component.

For information about the Security Management, see the Dell OpenManage Server Administrator User’s Guide at support.dell.com/manuals.

Auto Negotiate

and

128-bit or higher

Getting Technical Assistance

For customers in the United States, call 800-WWW-DELL (800-999-3355).

NOTE: If you do not have an active Internet connection, you can find contact

information on your purchase invoice, packing slip, bill, or Dell product catalog.

For information on technical support, visit dell.com/contactus.

Additionally, Dell Enterprise Training and Certification is available at dell.com/training.

Introduction 15

Page 16

16 Introduction

Page 17

Preinstallation Setup

Ensure that you perform the following before installing Server Administrator:

• Read the installation instructions for your operating system.

• Read the "Installation Requirements" to ensure that your system meets or exceeds the minimum requirements.

• Read the applicable Dell OpenManage readme files and the

Software Support Matrix

support.dell.com/support/edocs/software/omswrels

• Close all applications running on the system before installing Server Administrator applications.

On Linux, ensure that all operating system RPM packages required by the Server Administrator RPMs are installed. If your system had VMware ESX factory-installed, Red Hat Enterprise Linux, or SUSE Linux Enterprise Server, see the "Dependent RPMs for Remote Enablement" section for information on any RPMs that you need to manually install prior to installing managed system software. Typically, you do not have to manually install any RPMs.

located at

Prerequisite Checker

Dell Systems

The setup.exe (located at \SYSMGMT\srvadmin\windows) starts the prerequisite checker program. The prerequisite checker program examines the prerequisites for software components without launching the actual installation. This program displays a status window that provides information about your system’s hardware and software that may affect the installation and operation of software features.

NOTE: If you want to use supporting agents for the Simple Network Management

Protocol (SNMP), you must install the operating system support for the SNMP standard before or after you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system.

Preinstallation Setup 17

Page 18

You can run the prerequisite checker silently by executing runprereqchecks.exe /s from the

SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD.

After running the prerequisite checker, a HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check. The Te mp directory is located at X:\Documents and Settings\username\Local Settings\Temp. To find %TEMP%, go to a command line prompt and type echo %TEMP%.

The results are written under the following key for a managed system:

HKEY_LOCAL_MACHINE\Software\Dell Computer Corporation\OpenManage \PreReqChecks\MN\

While running the prerequisite checker silently, the return code from runprereqchecks.exe is the number associated with the highest severity condition for all the software products. The return code numbers are the same as those used in the registry. Table 2-1 details the return codes.

Table 2-1. Return Codes While Running the Prerequisite Checker Silently

Return Code

0 No condition, or conditions, is associated with the software.

1 An informational condition, or conditions, is associated with the software.

2 A warning condition, or conditions, is associated with the software. It is

3 An error condition, or conditions, is associated with the software. You

-1 A Microsoft Windows Script Host (WSH) error. The prerequisite checker

-2 The operating system is not supported. The prerequisite checker does not

Description

It does not prevent a software product from being installed.

recommended that you resolve the conditions causing the warning before proceeding with the installation of the software. If you decide to continue, you can select and install the software using the custom installation.

must resolve the conditions causing the error before proceeding with the installation of the software. If you do not resolve the issues, the software is not installed.

does not run.

run.

18 Preinstallation Setup

Page 19

Table 2-1. Return Codes While Running the Prerequisite Checker Silently

(continued)

Return Code

-3 The user does not have Administrator privileges. The prerequisite checker

-4 Not an implemented return code.

-5 The prerequisite checker does not run. The user failed to change the

-6 The destination directory does not exist. The prerequisite checker does

-7 An internal error has occurred. The prerequisite checker does not run.

-8 The software is already running. The prerequisite checker does not run.

-9 The WSH is corrupted, is a wrong version, or is not installed. The

-10 An error has occurred with the scripting environment. The prerequisite

Description

does not run.

working directory to %TEMP%.

not run.

prerequisite checker does not run.

checker does not run.

NOTE: A negative return code (-1 through -10) indicates a failure in running the

prerequisite checker tool. Probable causes for negative return codes include software policy restrictions, script restrictions, lack of folder permissions, and size constraints.

NOTE: If you encounter a return code of 2 or 3, it is recommended that you inspect

the omprereq.htm file in the windows temporary folder %TEMP%. To find %TEMP%, run

echo %TEMP% .

Common causes for a return value of 2 from the prerequisite checker:

• One of your storage controllers or drivers has outdated firmware or driver.

firmwaredriverversions_

See

language) To f in d

firmwaredriverversions.txt

%TEMP%

, run

<lang>

.html

echo %TEMP%

(where <lang> stands for

found in the

%TEMP%

folder.

• RAC component software version 4 is not selected for a default install unless the device is detected on the system. The prerequisite checker generates a warning message in this case.

• Intel and Broadcom agents are selected for a default install only if the corresponding devices are detected on the system. If the corresponding devices are not found, prerequisite checker generates a warning message.

Preinstallation Setup 19

Page 20

• Domain Name System (DNS) or Windows Internet Name Service (WINS) server running on your system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information.

• Do not install managed system and management station RAC components on the same system. Install only the managed system RAC components, as they offer the required functionality.

Common causes for a return code of 3 (failure) from the prerequisite checker:

• You are not logged in with built-in

Administrator

privileges.

• The MSI package is corrupt or one of the required XML files is corrupt.

• Error during copying from a DVD or network access problems while copying from a network share.

• Prerequisite checker detects that another MSI package installation is currently running or that a reboot is pending:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\Windows\Current Version\Installer\InProgress

indicates another MSI package installation is in

progress.

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\ \Session Manager\\PendingFileRenameOperations

indicates that a

reboot is pending.

• Running the 64-bit version of Windows Server 2008 Core, since certain components are disabled from being installed.

Ensure that any error or warning is corrected before you proceed to install Dell OpenManage software components.

Each software has an associated value set after running the prerequisite check. Table 2-2 provides the list of feature IDs for each software feature. The feature ID is a 2 to 5 character designation.

NOTE: The software feature IDs mentioned in Table 2-2 are case-sensitive.

Table 2-2. Software Feature IDs for Managed Systems Software

Feature ID Description

ALL All features

BRCM Broadcom Network Interface Card (NIC) Agent

INTEL Intel NIC Agent

20 Preinstallation Setup

Page 21

Table 2-2. Software Feature IDs for Managed Systems Software

Feature ID Description

IWS Dell OpenManage Server Administrator Web Server

OMSM Server Administrator Storage Management Service

RAC4 Dell Remote Access Controller (DRAC 4)

RAC5 Dell Remote Access Controller (DRAC 5)

iDRAC Integrated Dell Remote Access Controller

SA Server Administrator

RmtMgmt Remote Enablement

(continued)

Installation Requirements

This section describes the general requirements of the Dell OpenManage Server Administrator and provides information on supported operating systems and web browsers.

NOTE: Prerequisites specific to an operating system are listed as part of the

installation procedures.

Supported Operating Systems and Web Browsers

For information on supported operating systems and web browsers, see the Dell Systems Software Support Matrix located

support.dell.com/support/edocs/software/omswrels

NOTE: Ensure that the web browser is configured to bypass the proxy server for

local addresses.

Multilingual User Interface Support

The Dell OpenManage installer provides Multilingual User Interface (MUI) support available on the following operating systems:

• Windows Server 2008 (64-bit)

• Windows Server 2008 (64-bit) R2

• Windows Server 2008 (64-bit) R2 SP1

Preinstallation Setup 21

Page 22

The MUI Pack is a set of language-specific resource files that can be added to the English version of a supported Windows operating system. Dell OpenManage 7.0 installer supports only six languages: English, German, Spanish, French, Simplified Chinese, and Japanese.

NOTE: When MUI is set to non-Unicode languages like Simplified Chinese, set the

system locale to Simplified Chinese. This enables the prerequisite checker messages to be displayed. This is because any non-Unicode application runs only when the system locale (also called Language for non-Unicode Programs on XP) is set to match the application's language.

Viewing Localized Versions of the Web-Based Interface

To view the localized versions of the web interface on Windows, in the Control Panel select Regional and Language Options.

System Requirements

Dell OpenManage Server Administrator must be installed on each system to be managed. You can manage each system running Server Administrator locally or remotely through a supported web browser.

Managed System Requirements

• One of the supported operating system and web browser.

• Minimum of 2 GB of RAM.

• Minimum of 512 MB of free hard drive space.

• Administrator rights.

• TCP/IP connection on the managed system and the remote system to facilitate remote system management. For

•One of the information,

• Monitor with a minimum screen resolution of 800 x 600. The recommended screen resolution is at least 1024 x 768.

supported systems management protocol standards.

see

"Supported Systems Management Protocol Standards".

For more

22 Preinstallation Setup

Page 23

• The Server Administrator Remote Access Controller service requires remote access controller (RAC) be installed on the managed system. See the relevant

Dell Remote Access Controller User’s Guide

for complete

software and hardware requirements.

NOTE: The RAC software is installed as part of the Typical Setup installation

option, provided the managed system meets all of the RAC installation prerequisites.

• The Server Administrator Storage Management Service requires Dell OpenManage Server Administrator be installed on the managed system. See the

Guide

Dell OpenManage Server Administrator Storage Management User’s

for complete software and hardware requirements.

• Microsoft Software Installer (MSI) version 3.1 or later.

NOTE: Dell OpenManage software detects the MSI version on your system.

If the version is lower than 3.1, the prerequisite checker prompts you to upgrade to MSI version 3.1. After upgrading the MSI to version 3.1, you may have to reboot the system to install other software applications such as Microsoft SQL Server.

Supported Systems Management Protocol Standards

A supported systems management protocol must be installed on the managed system before installing your management station or managed system software. On supported Windows and Linux operating systems, Dell OpenManage software supports: Common Information Model (CIM), Windows Management Instrumentation (WMI), and Simple Network Management Protocol (SNMP). You must install the SNMP package provided with the operating system. If SNMP is installed post OMSA installation, you need to restart OMSA services.

NOTE: For information about installing a supported systems management protocol

standard on your managed system, see your operating system documentation.

Preinstallation Setup 23

Page 24

Table 2-3 shows the availability of the systems management standards for each supported operating system.

Table 2-3. Availability of Systems Management Protocol by Operating Systems

Operating System SNMP CIM/WMI

Supported Microsoft Windows operating systems.

Supported Red Hat Enterprise Linux operating systems.

Supported SUSE Linux Enterprise Server operating systems.

NOTE: It is recommended that you install the SFCB, SFCC, OpenWSMAN, and

CMPI-Devel packages from the operating system media, if available.

Available from the operating system installation media.

Install the SNMP package provided with the operating system.

Always installed

Available. Install the CIM packages provided on the Dell

Systems Management Tools and Documentation DVD -

SFCB/SFCC/CMPI-Devel

Available. Install the CIM packages provided on the Dell

Systems Management Tools and Documentation DVD -

SFCB/SFCC/CMPI-Devel

Digital Certificates

All Server Administrator packages for Microsoft are digitally signed with a Dell certificate that helps guarantee the integrity of the installation packages. If these packages are repackaged, edited, or manipulated in other ways, the digital signature is invalidated. This manipulation results in an unsupported installation package and the prerequisite checker does not allow you to install the software.

24 Preinstallation Setup

Page 25

Enabling Windows Installer Logging Service

Windows includes a registry-activated logging service to help diagnose Windows Installer issues. To enable this logging service during a silent install, open the registry editor and create the following path and keys:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Window s\Installer Reg_SZ: Logging Value: voicewarmup

The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 3.1:

v- Verbose output o- Out-of-disk-space message i- Status message c- Initial UI parameter e- All error message w - Non-fatal warning a- Startup of action r- Action-specific record m- Out-of-memory or fatal exit information u- User request p- Terminal property +- Append to existing file !- Flush each line to the log "*"- Wildcard, log all information except for the v option. To include the

v option, specify "/l*v".

Once activated, you can find the log files that are generated in your %TEMP% directory. Some log files generated in this directory are:

•

Managed System Installation

–

SysMgmt.log

•

Management Station Installation

–

MgmtSt.log

These log files are created by default if the prerequisite checker user interface (UI) is running.

Preinstallation Setup 25

Page 26

Microsoft Active Directory

If you use Active Directory service software, you can configure it to control access to your network. Dell has modified the Active Directory database to support remote management authentication and authorization. Dell OpenManage Server Administrator (OMSA), IT Assistant (ITA), Integrated Dell Remote Access Controller (iDRAC), Dell Chassis Management Controller (CMC), and Dell Remote Access Controllers (RAC), can interface with Active Directory. Using Active Directory, you can add and control users and privileges from one central database. For more information, see "Using Microsoft Active Directory."

Configuring the SNMP Agent

Dell OpenManage software supports the SNMP systems management standard on all supported operating systems. The SNMP support may or may not be installed depending on your operating system and how the operating system was installed. An installed supported systems management protocol standard, such as SNMP, is required before installing Dell OpenManage software. For more information, see "Installation Requirements" and "Supported Systems Management Protocol Standards".

You can configure the SNMP agent to change the community name, enable set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant, perform the procedures described in the Dell OpenManage Server Administrator User’s Guide at support.dell.com/manuals.

Secure Port Server and Security Setup

This section contains the following topics:

• Setting User and Server Preferences

• X.509 Certificate Management

26 Preinstallation Setup

Page 27

Setting User and Server Preferences

You can set user and secure port server preferences for Server Administrator and IT Assistant from the respective Preferences web page. Click General Settings and click either the User tab or Web Serve r tab.

NOTE: You must be logged in with administrator privileges to set or reset user or

server preferences.

To set up your user preferences:

Click

Preferences

The

Preferences

Click

General Settings

To add a preselected e-mail recipient, type the e-mail address of your designated service contact in the

NOTE: Clicking Email in any window sends an e-mail message with an

attached HTML file of the window to the designated e-mail address.

To change the home page appearance, select an alternative value in the

skin

scheme

To set up your secure port server preferences:

Click

Preferences

The

Preferences

Click

General Settings

Set options as necessary in the

•

Session Timeout

Select specified time in minutes. After a session time-out the user must log in again to continue. Select Administrator session time-out feature.

•

HTTPS Port

The default secure port for Server Administrator is 1311.

on the global navigation bar.

home page is displayed.

fields and click

Mail To:

Apply Changes

field, and click

on the global navigation bar.

home page is displayed.

, and the

Web Server

tab.

Server Preferences

window:

— Sets the time limit for a session to remain active.

Enable

to set a time-out if there is no user interaction for a

Disable

to disable the Server

— Specifies the secure port for Server Administrator.

Apply Changes

NOTE: Changing the port number to an invalid or in-use port number

may prevent other applications or browsers from accessing Server Administrator on the managed system.

Preinstallation Setup 27

Page 28

•

IP Address to Bind to

— Specifies the IP address(es) for the managed

system that Server Administrator binds to when starting a session.

All

to bind to all IP addresses applicable for your system. Select

to bind to a specific IP address.

NOTE: A user with administrator privileges cannot use Server

Administrator when logged into the system remotely.

NOTE: Changing the IP Address to Bind to value to a value other than

All may prevent other applications or browsers from remotely accessing Server Administrator on the managed system.

— Allows to set the default mail address for e-mail(s) from

•

Select

Specific

Mail to

OMSA GUI.

•

SMTP Server name

and

DNS Suffix for SMTP Server

— Specifies your organization's Simple Mail Transfer Protocol (SMTP) and Domain Name Server (DNS) suffix. To enable Server Administrator to send e-mails, you must type the IP address and DNS suffix for the SMTP server for your organization in the appropriate fields.

NOTE: For security reasons, your organization may not allow e-mails to

be sent through the SMTP server to outside accounts.

•

Command Log Size

— Specifies the largest file size in MB for the

command log file.

•

Support Link

— Specifies the web address for the business entity that

provides support for your managed system.

•

Custom Delimiter

data fields in the files created using the is the default delimiter. Other options are

, and ,.

:,|

Click

Apply Changes

— Specifies the character used to separate the

Export

button. The ; character

!, @, #, $, %, ^, *, ~, ?,

28 Preinstallation Setup

Page 29

X.509 Certificate Management

Web certificates are necessary to ensure that the identity and information exchanged with a remote system cannot be viewed or changed by others. To ensure system security, it is strongly recommended that you either generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from a Certificate Authority (CA). Authorized CAs include Verisign, Entrust, and Thawte.

NOTE: You must be logged in with administrator privileges to perform certificate

management.

You can manage X.509 certificates for Server Administrator and IT Assistant from the respective Preferences page. Click General Settings, select the Web Server tab, and click X.509 Certificate.

Best Practices for X.509 Certificate Management

For the security of your system while using server administrator, ensure the following:

•

Unique host name —

should have unique host names.

•

Change 'localhost' to unique localhost

should be changed to a unique host name.

All systems that have Server Administrator installed

— All systems with host name set to

Remote Enablement Requirements

The Remote Enablement feature is currently supported on:

• Microsoft Windows

•Microsoft Hyper-V

• Hyper-V Server

• Red Hat Enterprise Linux

• SUSE Enterprise Linux

• VMware ESXi and ESX

•Citrix XenServer 6.0

Preinstallation Setup 29

Page 30

To install the Remote Enablement feature, the following must be configured on your system:

• Windows Remote Management (WinRM)

• CA/Self-Signed Certificate

• WinRM HTTPS Listener Port

• Authorization for WinRM and Windows Management Instrumentation (WMI) Servers

Installing WinRM

On Windows Server 2008 R2 and Windows 7, WinRM 2.0 is installed by default. On Windows Server 2008, WinRM 1.1 is installed by default.

Certificate Authority — Signed/Self-Signed Certificate

You need a certificate signed by a CA or a self-signed certificate (generated using the SelfSSL tool) to install and configure the Remote Enablement feature on your system.

NOTE: It is recommended that you use a certificate signed by a CA.

Using a Certificate Signed by a CA

To use a certificate signed by a CA:

Request a valid CA signed certificate.

Create a HTTP listener with the CA signed certificate.

Requesting a Valid CA Signed Certificate

To request a valid CA signed certificate:

Click

Start

Ty p e

mmc

Click

File

Select

In the

Select

30 Preinstallation Setup

Run

and click OK.

Add/Remove Snap-in

Certificates

Certificates snap-in

Local Computer

and click Add.

and click

dialog box, select

Finish

Computer account

, click

Page 31

Click

and click OK.

On the

Console window

, expand

Certificates (Local Computer)

in the

left navigation pane.

Right-click

Click

Select the appropriate certificate type,

Enroll

Click

Creating the HTTPS Listener With the Valid CA Signed Certificate

Finish

Personal

, select

All tasks

Request New Certificate

Mostly (Computer)

, and click

Run the installer and click the link on the prerequisite checker to create the HTTPS listener.

Using the SelfSSL Tool to Generate Self-Signed Certificates

To generate a self-signed certificate using the SelfSSL tool :

Create a certificate.

Add the certificate and take a thumbprint.

Create the WinRM HTTPS listener.

Configure the Envelope size for WinRM.

Creating a Certificate

Download the

microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73b628-ade629c89499&displaylang

Run

iis60rkt.exe

Click

Select

I Agree

Click

In the

Select Type

Click

In the

Select Features

Click

IIS Resource Kit

in the

End-User License Agreement

screen, select

from

Custom

screen, select

and click

SelfSSL 1.0

screen and click

and click

Next.

Preinstallation Setup 31

Page 32

Click

Finish

The

SelfSSL

Click

Ty p e

Start

is installed.

Programs

IIS Resource

SelfSSL

SelfSSL

selfssl /T /N:CN=<computer_name or domain_name>

Adding a Certificate and Taking a Thumbprint

To add a certificate and tae a thumbprint:

NOTE: If Internet Information Service (IIS) is already installed on your system, then

the value of CertificateThumbprint must be an empty string and you need not perform the steps in this section. For example:

winrm create winrm/config/Listener?Address= *+Transport=HTTPS @{Hostname= "<host_name>";CertificateThumbprint=""}

Click

Start

Ty p e

mmc

Click

File

Click

Add

Click

Certificates

In the Certificates snap-in dialog box, select and click

Select

Click

Click OK.

On the

Run

and click OK.

Add/Remove Snap-in

and click

Local Computer

Console

window, expand

Add

and click

Computer account

Finish

Certificates (Local Computer)

left navigation pane.

Expand

Select

In the right-hand pane, double-click the required certificate.

The

Personal

Certificates

Certificate

screen is displayed.

option

in the

32 Preinstallation Setup

Page 33

Click

Details

tab.

Select

Thumbprint

Copy the thumbprint to the clipboard. You can use this parameter while

creating the HTTPS listener.

Click OK.

Creating the WinRM HTTPS Listener

To enable the HTTPS listener on WinRM, type the following command:

winrm create winrm/config/Listener?Address= *+Transport=HTTPS @{Hostname= "<host_name>";CertificateThumbprint= "6e132c546767bf16a8acf4fe0e713d5b2da43013"}

If you are using Windows Server 2008 Small Business Server, leave the value of CertificateThumbprint blank as follows:

winrm create winrm/config/Listener?Address= *+Transport=HTTPS @{Hostname= "<host_name>";CertificateThumbprint=""}

NOTE: Ensure that the values of the Hostname and

CertificateThumbprint are correct.

The HTTP listener is enabled by default and listens at port 80.

Configuring User Authorization for WinRM and WMI Servers

To provide access rights to WinRM and WMI services, users must be explicitly added with the appropriate access levels.

NOTE: To configure user authorization

- For WinRM and WMI Servers, you must login with administrator privileges.

- For Windows Server 2008 operating systems, you must login with built-in administrator privileges

NOTE: The administrator is configured by default.

Preinstallation Setup 33

Page 34

WinRM

To configure user authorization for WinRM servers:

Click

Start

Ty p e

winrm configsddl

If you are using WinRM 2.0, type

Click

Add

Provide the appropriate permission(s) to the respective users and click OK.

WMI

Run

and click OK.

winrm configsddl default

and add the required users or groups (local/domain) to the list.

To configure user authorization for WMI servers:

Click

StartRun

Ty p e

wmimgmt.msc

The

Windows Management Infrastructure (WMI)

Right-click the

Properties

The

WMI Control (Local) Properties

Click

Security

Navigate to

Click

Security

The

Security

and click OK.

WMI Control (Local)

and expand the

Root

DCIM

screen appears.

node in the left pane and click

screen appears.

Root

node in the namespace tree.

sysman

screen is displayed.

Click

Add

to add the required users or groups (local/domain) to the list.

Provide the appropriate permission(s) to the respective users and click OK.

Click OK.

Close the

Windows Management Infrastructure (WMI)

screen.

34 Preinstallation Setup

Page 35

Configuring the Windows Firewall for WinRM

To configure the Windows Firewall for WinRM:

Open the

Click

Click the

Select the see the check box, click

Control Panel

Windows Firewall

Exceptions

tab.

Windows Remote Management

Add Program

check box. If you do not

to add Windows Remote

Management.

Configuring the Envelope Size for WinRM

To configure the envelope size for WinRM:

Open a command prompt.

Ty p e

winrm g winrm/config

Check the value of the

4608

less than

, type the following command:

MaxEnvelopeSizekb

attribute. If the value is

winrm s winrm/config @{MaxEnvelopeSizekb="4608"}

Set the value of

MaxTimeoutms

to 3 minutes:

winrm s winrm/config @{MaxTimeoutms ="180000"}

On WinRM version 2.0, enable the compatibility mode for WinRM version

2.0 to use port 443. WinRM version 2.0 uses port 5986 by default. To enable the compatibility mode, type the following command:

winrm s winrm/config/Service @{EnableCompatibilityHttpsListener="true"}

Preinstallation Setup 35

Page 36

Dependent RPMs for Remote Enablement

If you choose to install the Remote Enablement feature, you have to install certain dependent RPMs and configure these RPMs before installing the feature. Install the following RPMs:

•

libcmpiCppImpl0

•

libwsman1

•

openwsman-server

•

sblim-sfcb

•sblim-sfcc

The dependent RPMs are available on the

Documentation

DVD at srvadmin\linux\RPMS\supportRPMS\opensource-

components\<OS>\<arch>.

NOTE: On supported SLES and Red Hat Enterprise Linux operating systems, it is

recommended that you install the above RPMs from the operating system media, if available.

Installing Dependent RPMs

To install the dependent RPMs not available on the operating system media:

Ensure that Pegasus RPMs are uninstalled.

Check if the

openwsmand

and

using make-install. You can check by running the commands:

openwsman

Dell Systems Management Tools and

sfcbd

binaries are already installed

sfcbd

You can check the existence of the above binaries in the directory.

If the binaries are installed, uninstall these binaries.

36 Preinstallation Setup

/usr/local/sbin

Page 37

Check for the required dependencies for the

openwsman

and

sfcbd

RPMs listed in Table 2-4.

Table 2-4. Required Dependencies

Packages Red Hat Enterprise Server SUSE Linux Enterprise Server

Openwsman

SBLIM SFCC CURL LibCURL

SBLIM SFCB

•OpenSSL

•LibXML

•Pkgconfig

•CURL

•Chkconfig

•Initscript

•SBLIM-SFCC

•zlib

•CURL

•PAM

•OpenSSL

•Chkconfig

•Initscript

• LibOpenSSL

•LibXML

•Pkg-config

•libCURL

• aaa_base

•SBLIM-SFCC

•zlib

•LibCURL

•PAM

• LibOpenSSL

• aaa_base

Preinstallation Setup 37

Page 38

Install the dependent RPMs. You can install the RPMs:

• with a single command

rpm -ivh rpm1 rpm2 rpm3 rpm4 … rpmN

• individually

NOTE: If you are installing RPMs individually, follow the sequence below.

rpm -ivh sblim-sfcb-x.x.x.rpm

rpm -ivh sblim-sfcc-x.x.x.rpm

NOTE: Install the libwsman and openwsman client RPMs simultaneously as

they have cyclic dependency.

rpm -ivh libwsman1-x.x.x.rpm openwsman-clientx.x.x.rpm

rpm -ivh openwsman-server-x.x.x.rpm

Post-Installation Configuration for Remote Enablement

This section details the steps to configure the dependent RPMs if you have installed the Remote Enablement feature.

The post-installation configuration script is available at /opt/dell/srvadmin/etc/ on the server file system.

After installing all the dependent RPMs and the Remote Enablement feature, execute the autoconf_cim_component.sh script.

Before executing the autoconf_cim_component.sh script, ensure that Dell OpenManage is installed. For information on installing Dell OpenManage, see "Installing Managed System Software on Supported Linux and VMware ESX."

Execute the following command to configure sfbc and openwsman as per the default configurations:

./ autoconf_cim_component.sh

NOTE: To configure openwsman on the managed node to run on a different port,

use the -p <port> option with autoconf_cim_component.sh. This is optional and by default the openwsman is configured to run on port 443.

38 Preinstallation Setup

Page 39

Creating Server Certificate for WSMAN

You can either create a new certificate for WSMAN or reuse an existing certificate.

Creating a New Certificate

You can create a new server certificate for WSMAN by executing the owsmangencert.sh script located at /etc/openwsman. This script is provided by the openwsman RPM. Follow the steps in the wizard to create the server certificate.

Reusing an Existing Certificate

If you have a self-signed or CA-signed certificate, you can use the same certificate for the openwsman server by updating the ssl_cert_file and ssl_key_file values, grouped under [server] tag, in /etc/openwsman/openwsman.conf with your existing certificate values.

Configuring CRL for the openwsman Client

You need to configure the Certificate Revocation List (CRL) used by Server Administrator Web Server. To do this:

Mention a valid CRL file in

If left blank, the CRL check is ignored.

NOTE: CRL support is only present on SUSE Linux Enterprise Server version 11 and

Red Hat Enterprise Linux Server version 5 update 5. For other operating systems, contact your operating system vendor to provide the required CURL library with CRL support.

/etc/openwsman/openwsman_client.conf

Running sfcb and openwsman

NOTE: On Red Hat Enterprise Linux 6, replace sfcb with sblim-sfcb.

Run sfcb and openwsman:

•

/etc/init.d/sfcb start

•

/etc/init.d/openwsmand start

Preinstallation Setup 39

Page 40

On Red Hat Enterprise Linux 6, for the sblim-sfcb and openwsman to start automatically after a reboot you need to change the run-levels using the chkconfig utility. For example, if you want to run sblim-sfcb in run- levels 3 and 5, use the following command:

#chkconfig sblim-sfcb on --level 35

NOTE: For more information on chkconfig and its usage, see the operating

system documentation.

The managed system is configured and is ready to be used by the Server Administrator Web Server.

Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems

Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation, replace lib with lib64.

Back up the following files:

•

/etc/pam.d/openwsman

•

/etc/pam.d/sfcb

•

/etc/pam.d/system-auth

Replace the content of

auth required pam_stack.so service=system-auth

/etc/pam.d/openwsman

and

/etc/pam.d/sfcb

with:

auth required /lib/security/pam_nologin.so

account required pam_stack.so service=system-auth

Replace the content of

%PAM-1.0

This file is auto-generated.

User changes will be destroyed the next time authconfig is run.

auth required /lib/security/$ISA/pam_env.so

40 Preinstallation Setup

/etc/pam.d/system-auth

with:

Page 41

auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok

auth sufficient /lib/security/$ISA/pam_krb5.so use_first_pass

auth sufficient /lib/security/$ISA/pam_winbind.so use_first_pass

auth required /lib/security/$ISA/pam_deny.so

account required /lib/security/$ISA/pam_unix.so broken_shadow

account sufficient /lib/security/$ISA/pam_succeed_if.so uid 100 quiet

account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_krb5.so

account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_winbind.so

account required /lib/security/$ISA/pam_permit.so

password requisite /lib/security/$ISA/pam_cracklib.so retry=3

password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5 shadow

password sufficient /lib/security/$ISA/pam_krb5.so use_authtok

password sufficient /lib/security/$ISA/pam_winbind.so use_authtok password required /lib/security/$ISA/pam_deny.so session required /lib/security/$ISA/pam_limits.so session required /lib/security/$ISA/pam_unix.so session optional /lib/security/$ISA/pam_krb5.so

Preinstallation Setup 41

Page 42

Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating System

Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation, replace lib with lib64.

Back up the following files:

•

/etc/pam.d/openwsman

•

/etc/pam.d/sfcb

•

/etc/pam.d/system-auth

•

/etc/pam.d/common-account

Replace the content of

%PAM-1.0

auth include common-auth auth required /lib/security/pam_nologin.so account include common-account

Replace the content of

auth required pam_env.so auth sufficient pam_unix2.so debug auth sufficient pam_winbind.so use_first_pass debug

/etc/pam.d/openwsman/

/etc/pam.d/common-auth

and

/etc/pam.d/sfcb

with:

Replace the content of

account sufficient pam_unix2.so account sufficient pam_winbind.so

/etc/pam.d/common-account

with:

Workaround for the Libssl Issue

If the required library needed by openwsman is present on your system, the autoconf_cim_component.sh script tries to resolve the libssl.so issue.

However, if the library is not present, then the script reports the same. Check if the latest version of the libssl library is installed on your system and then create a soft link with libssl.so.

42 Preinstallation Setup

Page 43

For example: On a 32-bit Dell OpenManage installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link with the latest libssl.so.0.9.8b:

•

ln -sf /usr/lib/libssl.so.0.9.8b /usr/lib/libssl.so

• ldconfig

On a 64-bit Dell OpenManage installation, if you have libssl.so.0.9.8a and libssl.so.0.9.8b in /usr/lib, then create soft link with the latest libssl.so.0.9.8b:

•

ln -sf /usr/lib64/libssl.so.0.9.8b /usr/lib64/libssl.so

•

ldconfig

Preinstallation Setup 43

Page 44

44 Preinstallation Setup

Page 45

Installing Managed System Software on Microsoft Windows Operating Systems

On Microsoft Windows, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD. This utility allows you

to choose the systems management software you want to install on your system.

If the autorun program does not start automatically, use the setup program in the SYSMGMT\srvadmin\windows directory on the Dell Systems

Management Tools and Documentation DVD. See the Dell Systems Software Support Matrix for a list of operating systems currently supported.

NOTE: Use the Dell Systems Management Tools and Documentation DVD to

perform an unattended and scripted silent installation of the managed system software. You can also install and uninstall the features from the command line.

Deployment Scenarios for Server Administrator

You can install Dell OpenManage

• Install the Server Administrator Web Server on any system (Dell PowerEdge system, laptop, or desktop) and the Server Instrumentation on another supported Dell PowerEdge system.

In this method, the Server Administrator Web Server performs the function of a central web server and you can use it to monitor a number of managed systems. Using this method reduces the Server Administrator footprint on the managed systems.

Server Administrator in the following ways

• Continue to install the Server Administrator Web Server and the Server Instrumentation on the same system.

Installing Managed System Software on Microsoft Windows Operating Systems 45

Page 46

Table 3-1 lists the deployment scenarios for installing and using Server Administrator and helps you make the right choice while selecting the various installation options:

Table 3-1. Deployment Scenarios

You want to Select

Remotely manage and monitor your entire network of managed systems from your system (laptop, desktop, or server).

Manage and monitor your current system. Server Administrator Web Server and

Manage and monitor your current system using some other remote system.

View the status of local and remote storage attached to a managed system and obtain storage management information in an integrated graphical view.

Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system.

Server Administrator Web Server. You must then install Server Instrumentation on the managed systems.

Server Instrumentation.

Remote Enablement

For systems running on Microsoft Windows, Remote Enablement is under the Server Instrumentation option. You must then install the Server Administrator Web Server on the remote system.

Storage Management.

Remote Access Controller.

NOTE: Install the Simple Network Management Protocol (SNMP) agent on your

managed system using your operating system medium before installing the managed system software.

46 Installing Managed System Software on Microsoft Windows Operating Systems

Page 47

Installing Server Administrator

This section explains how to install the Server Administrator and other managed system software using two installation options:

• Using the setup program at

Dell Systems Management Tools and Documentation

• Using the unattended installation method through the Windows Installer Engine

NOTE: SNMP service is stopped and started during Systems Management

installation and uninstallation. As a result, services like DSM IT Assistant Connection Service, DSM IT Assistant Network Monitor and other third party services, dependent on SNMP stop. IT Assistant services is started at the end of Systems Management installation or uninstallation. If the third party services are stopped, these services needs to be manually restarted.

NOTE: For Blade systems, you must install Server Administrator on each server

module installed in the chassis.

NOTE: During installation of Server Administrator on supported Windows systems,

if an Out of Memory error message is displayed, you must exit the installation and free up memory. Close other applications or perform any other task that frees up memory, before re-attempting Server Administrator installation.

msiexec.exe

(see Table 3-2).

The setup program invokes the prerequisite checker, which uses your system's Peripheral Component Interconnect (PCI) bus to search for installed hardware such as controller cards.

The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for installing Server Administrator and other managed system software.

For information on the various components of Server Administrator available in Dell OpenManage and to help you choose the required components to install, see "Deployment Scenarios for Server Administrator."

\SYSMGMT\srvadmin\windows

DVD.

on the

Typical Installation

When you launch the Server Administrator installation from the prerequisite checker and select the Typical Setup option, the setup program installs the following managed system software features:

• Server Administrator Web Server

• Server Instrumentation

Installing Managed System Software on Microsoft Windows Operating Systems 47

Page 48

• Remote Access Controller

• Intel SNMP Agent

•Broadcom SNMP Agent

During a Ty p i c a l installation, individual management station services that do not meet the specific hardware and software requirement for that service are not installed on the managed systems. For example, the Dell OpenManage Server Administrator Remote Access Controller service software module is not installed during a Ty p i c a l installation unless the managed system has a remote access controller installed on it. You can, however, go to Custom Setup and select the Remote Access Controller software module for installation.

NOTE: The Remote Enablement feature is available only through the Custom Setup

option.

NOTE: Server Administrator installation also installs some of the required

Visual C++ runtime components on your system.

Custom Installation

The sections that follow describe how to install Server Administrator and other managed system software using the Custom Setup option.

NOTE: Management station and managed system services can be installed in the

same or in different directories. You can select the directory for installation.

Log on with built-in administrator privileges to the system on which you want to install the system management software.

Close all open applications and disable any virus-scanning software.

Insert the your system's DVD drive. The autorun menu appears.

Dell Systems Management Tools and Documentation

DVD into

48 Installing Managed System Software on Microsoft Windows Operating Systems

Page 49

Select

Dell OpenManage Server Administrator

Install

and click

from the autorun menu

If the autorun program does not start automatically, go to the

SYSMGMT\srvadmin\windows setup.exe

The

file.

Dell OpenManage Server Administrator

directory on the DVD, and run the

prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages are displayed. Resolve all error and warning situations, if any.

Click the

Install, Modify, Repair, or Remove Server Administrator

option.

The

Welcome to the Install Wizard for Dell OpenManage Server

Administrator

Click

The

Dell Software License Agreement

Click

The

Setup Type

Select

The

Custom Setup

I accept the terms in the license agreement

Custom

screen appears.

dialog box appears.

and click

dialog box appears.

appears.

and

if you agree.

See Table 4-1 and Table 4-2 to help you select the Server Administrator components for your system.

If you are installing Server Administrator on a non-Dell PowerEdge system, the installer displays only the

Server Administrator Web Server

option.

A selected feature has a hard drive icon depicted next to it. A deselected feature has a red

depicted next to it. By default, if the prerequisite checker finds a software feature with no supporting hardware, the checker deselects them.

To accept the default directory path to install managed system software,

click

. Otherwise, click

you want to install your managed system software, and click

Installing Managed System Software on Microsoft Windows Operating Systems 49

Change

and navigate to the directory where

Page 50

Click

on the

Custom Setup

dialog box to accept the selected

software features for installation.

The

Ready to Install the Program

NOTE: You can cancel the installation process by clicking Cancel.

The installation rolls back the changes that you made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly, leaving the system with an incomplete installation. For more information, see "System Recovery on Failed Installation."

Click

Install

to install the selected software features.

The

Installing Dell OpenManage Server Administrator

dialog box is displayed.

screen appears and provides the status and progress of the software features being installed. After the selected features are installed, the

Completed

Click

dialog box appears.

Finish

to exit the Server Administrator installation.

Install Wizard

If you are prompted to reboot your system, select from the following reboot options to make the installed managed system software services available for use:

•

Yes, reboot my system now.

•

No, I will reboot my system later.

NOTE: If you have selected Remote Enablement during installation, an error

message "A provider, WinTunnel, has been registered in the Windows Management Instrumentation namespace ROOT\dcim\sysman to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests." is logged in Windows Event Log. You can safely ignore this message and continue with installation.

Server Administrator Installation With Citrix Application Server

Citrix remaps all your hard drive letters when installed. For example, if you install Server Administrator on drive C: and then install Citrix, it may change your drive letter C: to M:. Server Administrator may not work properly because of the remapping.

50 Installing Managed System Software on Microsoft Windows Operating Systems

Page 51

In order to avoid this problem, select one of the following options:

Option 1:

Uninstall Server Administrator.

Install Citrix.

Reinstall Server Administrator.

Option 2:

After installing Citrix, type the following command:

msiexec.exe /fa SysMgmt.msi

Performing an Unattended Installation of Managed System Software

The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure.

Unattended installation enables you to simultaneously install Server Administrator on multiple systems. You can perform an unattended installation by creating a package that contains the necessary managed system software files. The unattended installation option also provides several features that enable you to configure, verify, and view information about unattended installations.

The unattended installation package is distributed to the remote systems using a software distribution tool from an independent software vendor (ISV). When the package is distributed, the installation script executes to install the software.

Installing Managed System Software on Microsoft Windows Operating Systems 51

Page 52

Creating and Distributing the Typical Unattended Installation Package

The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation

package. The msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software license agreement and installs all the required Server Administrator features on selected remote systems. These features are installed on the remote systems based on the system's hardware configuration.

NOTE: After an unattended installation is complete, to use the command line

interface (CLI) feature of Server Administrator, you must open a new console window and execute the CLI commands from there. Executing CLI commands from the same console window in which Server Administrator was installed does not work.

You can make the DVD image available to the remote system by either distributing the entire contents of the media, or by mapping a drive from the target system to the location of the DVD image.

Mapping a Drive to Act as the Typical Unattended Installation Package

Share an image of the

Dell Systems Management Tools and Documentation

DVD with each remote system on which you want to install Server Administrator.

You can accomplish this task by directly sharing the DVD or by copying the entire DVD to a drive and sharing the copy.

Create a script that maps a drive from the remote systems to the shared drive described in step 1. This script should execute

msiexec.exe /i Mapped Drive\SYSMGMT\srvadmin\windows\ SystemsManagement\SysMgmt.msi /qb

after the drive has

been mapped.

Configure your ISV distribution software to distribute and execute the script created in step 2.

Distribute this script to the target systems by using your ISV software distribution tools.

The script executes to install Server Administrator on each remote system.

Reboot each remote system to enable Server Administrator.

52 Installing Managed System Software on Microsoft Windows Operating Systems

Page 53

Distributing the Entire DVD as the Typical Unattended Installation Package

Distribute the entire image of the

Documentation

Configure your ISV distribution software to execute the

DVD to your target systems.

Dell Systems Management Tools and

msiexec.exe /i DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb

command from the DVD image.

The program executes to install Server Administrator on each remote system.

Reboot each remote system to enable Server Administrator.

Creating and Distributing Custom Unattended Installation Packages

To create a custom unattended installation package, perform the following steps:

Copy the

SYSMGMT\srvadmin\windows

directory from the DVD to the

system hard drive.

Create a batch script that executes the installation using the Windows Installer Engine (

NOTE: For Customized Unattended Installation, each required feature must

be included as a command line interface (CLI) parameter for it to be installed.

An example is

msiexec.exe

msiexec.exe /i SysMgmt.msi ADDLOCAL=

SA,IWS,BRCM /qb

(For more information and available feature

identifications, see "Customization Parameters").

Place the batch script in the

Installing Managed System Software on Microsoft Windows Operating Systems 53

windows

directory on the system hard drive.

Page 54

Distributing Custom Unattended Installation Packages

For distributing custom unattended installation packages:

NOTE: The SysMgmt.msi installation package for Server Administrator used in the

Custom Setup unattended installation (For more information, see "Creating and Distributing Custom Unattended Installation Packages") is located in the SYSMGMT\srvadmin\windows\SystemsManagement directory in the DVD.

Configure your ISV distribution software to execute the batch script once your installation package has been distributed.

Use your ISV distribution software to distribute the custom unattended installation package to the remote systems. The batch script installs Server Administrator along with specified features on each remote system.

Reboot each remote system to enable Server Administrator.

Specifying Log File Locations

For managed system MSI installation, run the following command to perform an unattended installation while specifying the log file location:

msiexec.exe /i SysMgmt.msi /l*v "C:\openmanage\logs\SysMgmt.log"

Unattended Installation Features

Unattended installation provides the following features:

• A set of optional command line settings to customize an unattended installation.

• Customization parameters to designate specific software features for installation.

• A prerequisite checker program that examines the dependency status of selected software features without having to perform an actual installation.

54 Installing Managed System Software on Microsoft Windows Operating Systems

Page 55

Optional Command Line Settings

Table 3-2 shows the optional settings available for the msiexec.exe MSI installer. Type the optional settings on the command line after msiexec.exe with a space between each setting.

NOTE: See support.microsoft.com for details about all the command line switches

for the Windows Installer Tool.

Table 3-2. Command Line Settings for MSI Installer

Setting Result

/i <Package|Product Code>

/i SysMgmt.msi

This command installs or configures a product.

/i SysMgmt.msi

software.

This command carries out a fresh installation of version 7.0.

– Installs the Server Administrator

/qn

/x <Package|Product Code>

/q[n|b|r|f]

This command uninstalls a product.

/x SysMgmt.msi – Uninstalls the Server Administrator software.

This command sets the user interface (UI) level.

/q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI. This option is used for unattended but not silent installation. /qr – reduced UI. This option is used for unattended installation while displaying a modal dialog box showing install progress.

– full UI. This option is used for standard

/qf

attended installation.

Installing Managed System Software on Microsoft Windows Operating Systems 55

Page 56

Table 3-2. Command Line Settings for MSI Installer

Setting Result

/f[p|o|e|d|c|a|u |m|s|v]<Package| ProductCode>

INSTALLDIR=<path> This command installs a product in a specific location. If

This command repairs a product.

/fp – This option reinstalls a product if a file is missing.

/fo – This option reinstalls a product if a file is missing or

if an older version of a file is installed.

/fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.

/fd – This option reinstalls a product if a file is missing or a different version of a file is installed.

/fc – This option reinstalls a product if a file is missing or the stored checksum value does not match the calculated value.

/fa – This option forces all files to be reinstalled.

/fu – This option rewrites all required user-specific

registry entries.

/fm – This option rewrites all required system-specific registry entries.

/fs – This option overwrites all existing shortcuts.

/fv – This option runs from the source and re-caches the

local package. Do not use this reinstall option for the first installation of an application or feature.

you specify an install directory with this switch, it must be created manually prior to executing the CLI install commands or they fail without displaying an error message.

/i SysMgmt.msi INSTALLDIR=c:\OpenManage /qn – installs a product to a specific location where c:\OpenManage is the install location.

(continued)

For example, running msiexec.exe /i SysMgmt.msi /qn installs Server Administrator features on each remote system based on the system's hardware configuration. This installation is done silently and unattended.

56 Installing Managed System Software on Microsoft Windows Operating Systems

Page 57

Customization Parameters

REINSTALL and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running a silent or unattended installation. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package. For example, you can choose to install Server Administrator, but not Remote Access Controller service on a specific group of servers, and choose to install Server Administrator, but not Storage Management Service, on another group of servers. You can also choose to uninstall one or multiple features on a specific group of servers.

NOTE: Type the REINSTALL, and REMOVE CLI parameters in upper case, as they are

case-sensitive.

NOTE: The software feature IDs mentioned in Table 3-3 are case-sensitive.

Table 3-3. Software Feature IDs

Feature ID Description

ALL All features

BRCM Broadcom NIC Agent

INTEL Intel NIC Agent

IWS Dell OpenManage Server Administrator

Web Se r v er

OMSM Server Administrator Storage

Management Service

RmtMgmt Remote Enablement

RAC4 Remote Access Controller (DRAC 4)

RAC5 Remote Access Controller (DRAC 5)

iDRAC Integrated Dell Remote Access Controller

SA Server Administrator

NOTE: Only iDRAC6 is supported on xx1x systems.

Installing Managed System Software on Microsoft Windows Operating Systems 57

Page 58

You can include the REINSTALL customization parameter on the command line and assign the feature ID (IDs) of the software feature that you want to reinstall. For example,

msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb

This command runs the installation for Dell OpenManage Systems Management and reinstalls only the Broadcom agent, in an unattended but not silent mode.

You can include the REMOVE customization parameter on the command line and assign the feature ID (IDs) of the software feature that you want to uninstall. For example,

msiexec.exe /i SysMgmt.msi REMOVE=BRCM /qb

This command runs the installation for Dell OpenManage Systems Management and uninstalls only the Broadcom agent, in an unattended but not silent mode.

You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program. For example,

msiexec.exe /i SysMgmt.msi REMOVE=BRCM /qb

This command runs the installation for managed system software, and uninstalls the Broadcom agent. This execution is in an unattended but not silent mode.

MSI Return Code

An application event log entry is recorded in the SysMgmt.log file. Table 3-4 shows some of the error codes returned by the msiexec.exe Windows Installer Engine.

Table 3-4. Windows Installer Return Codes

Error Code Value Description

ERROR_SUCCESS 0 The action is completed

successfully.

ERROR_INVALID_PARAMETER 87 One of the parameters was

invalid.

58 Installing Managed System Software on Microsoft Windows Operating Systems

Page 59

Table 3-4. Windows Installer Return Codes

Error Code Value Description

ERROR_INSTALL_USEREXIT 1602 The user canceled the

ERROR_SUCCESS_REBOOT_REQUIRED 3010 A restart is required to

NOTE: For more information on all the error codes returned by the msiexec.exe and

InstMsi.exe Windows Installer functions, see support.microsoft.com.

(continued)

installation.

complete the installation. This message is indicative of a successful installation.

Managed System Software Installation Using Third-Party Deployment Software

You can use third-party deployment software, such as Altiris Deployment Solution, to install managed systems software on supported Dell systems. To distribute and install Server Administrator using Altiris, start your Altiris application and import OpenManage_Jobs.bin located at

SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder to import

OpenManage_Jobs.bin. You might need to modify the Run Script and Copy File tasks to match your deployment environment. When complete, you can

then schedule your job to run on the supported Dell systems that are managed from your Altiris Deployment Solution.

System Recovery on Failed Installation

The Microsoft Software Installer (MSI) provides the ability to return a system to its fully working condition after a failed installation. MSI does this by maintaining an undo operation for every standard action it performs during an install, upgrade, or uninstall. This operation includes restoration of deleted or overwritten files, registry keys, and other resources. Windows temporarily saves all files that it deletes or overwrites during the course of an installation or removal, so that they can be restored if necessary, which is a type of rollback. After a successful installation, Windows deletes all of the temporary backup files.

Installing Managed System Software on Microsoft Windows Operating Systems 59

Page 60

In addition to the rollback of MSI Standard Actions, the Dell OpenManage library also has the ability to undo commands listed in the INI file for each application if a rollback occurs. All files that are modified by the Dell OpenManage installation actions are restored to their original state if a rollback occurs.

When the MSI engine is going through the installation sequence, it ignores all actions that are scheduled as rollback actions. If a Custom Action, MSI Standard Action, or a Dell OpenManage installation action fails, then a rollback starts.

An installation cannot be rolled back once it is completed; transacted installation is only intended as a safety net that protects the system during an installation session. If you want to remove an installed application, you should uninstall that application.

NOTE: Driver installation and removal is not executed as part of the installation

transaction and therefore cannot be rolled back if a fatal error occurs during execution.

NOTE: Installations, uninstallations, and upgrades that you cancel during installer

cleanup, or after the installation transaction is completed, are not rolled back.

Failed Updates

MSI patches and updates provided by vendors must be applied to the original vendor MSI packages provided. If you intentionally or accidentally repackage an MSI package, or make changes to it directly, patches and updates may fail. MSI packages must not be repackaged; doing so changes the feature structure and Globally Unique Identifier (GUID), which break any provided patches or updates. When it is necessary to make any changes to a vendor-provided MSI package, use a .mst transform file.

NOTE: A GUID is 128-bit long, and the algorithm used to generate a GUID

guarantees unique GUID. The product GUID uniquely identifies the application. In this case, the product GUID for Server Administrator is {DDA04AC3-F66B-47E0B189-6008EB1D80A2}.

60 Installing Managed System Software on Microsoft Windows Operating Systems

Page 61

Upgrading Managed System Software

The Dell OpenManage installer provides an Upgrade option for upgrading Server Administrator and other managed system software.

The setup program runs the prerequisite checker, which uses your system's PCI bus to search for installed hardware, such as controller cards.

The setup program installs or upgrades all of the managed system software features that are appropriate for your particular system's hardware configuration.

NOTE: All user settings are preserved during upgrades.

The following procedures show how to upgrade Server Administrator and other managed system software.

Upgrading Guidelines

• You can upgrade to the latest version of Dell OpenManage Server Administrator from any of the previous three versions. For example, upgrade to Dell OpenManage Server Administrator 7.0 is supported only for Dell OpenManage Server Administrator versions 6.3 and later.

• To upgrade from versions earlier than 6.3, uninstall the existing Server Administrator and reinstall the latest Server Administrator.

NOTE: Uninstalling Server Administrator deletes its user settings. Reinstall Server

Administrator and apply the user settings.

• When upgrading an operating system to a major version, uninstall the existing OpenManage software and reinstall the latest OpenManage software. When upgrading only to an update level change (for example, Red Hat Enterprise Linux 5 Update 4 to Red Hat Enterprise Linux 5 Update 5), upgrade to the latest OpenManage software; all user settings are preserved.

NOTE: Uninstalling OpenManage software deletes its user settings. Reinstall

OpenManage software and apply the user settings.

• If you have installed Server Administrator Web Server version 7.0, ensure that you install Server Instrumentation version 7.0 on your managed system. Accessing an earlier version of Server Administrator using Server Administrator Web Server version 7.0 may display an error.

Installing Managed System Software on Microsoft Windows Operating Systems 61

Page 62

Upgrade

Insert the your system's DVD drive. The autorun menu appears.

Select

If the autorun program does not start automatically, go to the

SYSMGMT\srvadmin\windows setup.exe

The appears and runs the prerequisite checks for the managed station. Any relevant informational, warning, or error messages are displayed. Resolve all error and warning situations, if any.

Click the The

Administrator

Click

The

Click

The

Continue the installation steps as mentioned in the custom installation section. Follow the procedure from "step 8" in "Custom Installation."

For an unattended upgrade, the msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software license agreement and upgrades all the required Server Administrator features on selected remote systems. All major user settings are retained during an unattended upgrade.

Dell Systems Management Tools and Documentation

Dell OpenManage Server Administrator

directory on the DVD, and run the

file.

Dell OpenManage Server Administrator prerequisite

Install, Modify, Repair, or Remove Server Administrator

Welcome to the Install Wizard for Dell OpenManage Server

screen appears.

Dell Software License Agreement

I accept the terms in the license agreement

Setup Type

dialog box appears.

appears.

and click

and

DVD into

Install

status screen

if you agree.

option.

Modify

If you want to add or remove Server Administrator components:

Navigate to the Windows

Click

Add/Remove Programs

Click

Dell OpenManage Server Administrator

The

Welcome to the Install Wizard for Dell OpenManage Server

Administrator

62 Installing Managed System Software on Microsoft Windows Operating Systems

dialog box appears.

Control Panel

and click

Change

Page 63

Click

The

Program Maintenance

Select the

The

To select a specific managed system software application, click the drop-

Modify

Custom Setup

option and click

dialog box appears.

down arrow beside the listed feature and select either

installed…

to install the feature, or

dialog box appears.

This feature will not be available

This feature will be

ignore the feature.

A selected feature has a hard drive icon depicted next to it. A deselected feature has a red

next to it. By default, if the prerequisite checker finds a software feature with no supporting hardware, the checker deselects the feature.

Click

to accept the selected software features for installation.

The

Ready to Modify the Program

Click

Install

to install the selected software features.

The

Installing Dell OpenManage Server Administrator

dialog box appears.

screen is displayed. Messages give the status and progress of the software features being installed.

When the selected features are installed, the

Install Wizard Completed

dialog box appears.

Click

Finish

to exit the Server Administrator installation.

If you are prompted to reboot your system, select from the following reboot options to make the managed system software services available for use:

•

Yes, reboot my system now.

•

No, I will reboot my system later.

NOTE: If you run the installer from another system and try to add a component

using the Modify option, the installer may display an error. A corrupt source on the system on which you run the installer may have caused the error. You can verify this by checking the following registry entry: HKLM\Software\Classes\Installer\Products\<GUID>\sourcelist\lastusedsource. If the value of lastusedsource is a negative number, it means that the source is corrupt.

Installing Managed System Software on Microsoft Windows Operating Systems 63

Page 64

Repair

If you want to repair an installed Server Administrator component that may be damaged:

Navigate to the Windows

Click

Add/Remove Programs

Click

Dell Server Administrator

The

Welcome to the Install Wizard for Dell OpenManage Server

Administrator

Click

The

Program Maintenance

Select the

The

Ready to Repair the Program

Click

Install

The

Installing Dell OpenManage Server Administrator

and provides the status and progress of the software features being installed.

dialog box appears.

Repair

option and click

to install the selected software features.

Control Panel

and click

dialog box appears.

Change

screen appears

When the selected features are installed, the dialog box appears.

Click

Finish

to exit the Server Administrator installation.

If you are prompted to reboot your system, select from the following reboot options:

•

Yes, reboot my system now

•

No, I will reboot my system later.

Install Wizard Completed

Uninstalling Managed System Software

You can uninstall managed system software features by using the Dell Systems Management Tools and Documentation DVD, or your operating

system. You can simultaneously perform unattended uninstallation on multiple systems.

64 Installing Managed System Software on Microsoft Windows Operating Systems

Page 65

Uninstalling Managed System Software Using Dell-Provided Media

Insert the your system's DVD drive.

If the setup program does not start automatically, run the

SYSMGMT\srvadmin\windows

The appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages detected during checking are displayed. Resolve all error and warning situations, if any.

Click the

The

Administrator

Click

The

This dialog enables you to modify, repair, or remove the program.

Select the

The

Click

The and provides the status and progress of the software features being uninstalled.

Dell Systems Management Tools and Documentation

directory on the DVD.

Dell OpenManage Server Administrator prerequisite

Install, Modify, Repair, or Remove Server Administrator

Welcome to the Install Wizard for Dell OpenManage Server

screen appears.

Program Maintenance

Remove

Remove the Program

Remove

Uninstalling Dell OpenManage Server Administrator

option and click

dialog box appears.

DVD into

setup.exe

status screen

screen appears

option.

in the

When the selected features are uninstalled, the dialog box appears.

Click

Finish

to exit the Server Administrator uninstallation.

If you are prompted to reboot your system, select from the following reboot options:

•

Yes, reboot my system now.

•

No, I will reboot my system later.

All Server Administrator features are uninstalled.

Installing Managed System Software on Microsoft Windows Operating Systems 65

Install Wizard Completed

Page 66

Uninstalling Managed System Software Features Using the Operating System

Navigate to the Windows

Click

Add/Remove Programs

Click

Dell OpenManage Server Administrator

The

Add or Remove Programs

Click

Yes

to confirm uninstallation of Server Administrator.

The

Dell OpenManage Server Administrator

the status and progress of the software features being uninstalled.

If you are prompted to reboot your system, select from the following reboot options:

•

Yes, reboot my system now.

•

No, I will reboot my system later.

All Server Administrator features are uninstalled.

Control Panel

dialog box appears.

and click

screen appears and provides

Remove

Unattended Uninstall Using the Product GUID

If you do not have the installation DVD or the MSI package available during an uninstallation, you can use the following command line to uninstall Dell OpenManage systems management software on managed systems or management stations running Windows operating system. For these cases, you can use the package GUIDs to uninstall the product.

For managed systems, use the following command:

msiexec.exe /x {DDA04AC3-F66B-47E0-B189-6008EB1D80A2}

Unattended Uninstallation of Managed System Software

The Dell OpenManage installer features an unattended uninstallation procedure. Unattended uninstallation enables you to simultaneously uninstall managed systems software from multiple systems. The unattended uninstallation package is distributed to the remote systems using a software distribution tool from an ISV. When the package is distributed, the uninstallation script executes to uninstall the software.

66 Installing Managed System Software on Microsoft Windows Operating Systems

Page 67

Distributing the Unattended Uninstallation Package

The Dell Systems Management Tools and Documentation DVD is pre-configured to act as the unattended uninstallation package. To distribute the package to one or more systems:

Configure your ISV distribution software to execute the

msiexec.exe /x DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb

command, if you are using the DVD, after the

unattended uninstallation package has been distributed.

Use your ISV distribution software to distribute the typical unattended uninstallation package to the remote systems.

The program executes to uninstall managed systems software on each remote system.

Reboot each remote system to complete uninstallation.

Unattended Uninstall Command Line Settings

Table 3-2 shows the unattended uninstall command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x SysMgmt.msi with a space between each setting.

For example, running msiexec.exe /x SysMgmt.msi /qb runs the unattended uninstallation, and displays the unattended uninstallation status while it is running.

Running msiexec.exe /x SysMgmt.msi /qn runs the unattended uninstallation, but silently (without displaying messages).

Installing Managed System Software on Microsoft Windows Operating Systems 67

Page 68

68 Installing Managed System Software on Microsoft Windows Operating Systems

Page 69

Installing Managed System Software on Supported Linux and VMware ESX

The Dell OpenManage installer supports both 32-bit and 64-bit architecture. The following table explains the operating system installation matrix for Dell OpenManage.

Table 4-1. Operating System Installation Matrix for Dell OpenManage

Operating System Architecture

Red Hat Enterprise Linux 5 32-bit

Red Hat Enterprise Linux 5 64-bit

Red Hat Enterprise Linux 5.7 64-bit

Red Hat Enterprise Linux 6 64-bit

Red Hat Enterprise Linux 6.1 64-bit

SUSE Linux Enterprise Server (SLES) 10 64-bit

SUSE Linux Enterprise Server (SLES) 11 64-bit

SUSE Linux Enterprise Server (SLES) 11 SP 2 64bit

OpenManage 32-bit Architecture OpenManage 64-bit

Architecture

Install or Upgrade Not supported

Upgrade (Upgrade is supported from N-1, N-2, and N-3)

Not supported Install

Upgrade (Upgrade is supported from N-1, N-2, and N-3)

Not supported Install

Install or Upgrade (Upgrade is supported from N-1 and N-

Installing Managed System Software on Supported Linux and VMware ESX 69

Page 70

Table 4-1. Operating System Installation Matrix for Dell OpenManage

(continued)

Operating System Architecture

ESX 4.0 U3 64-bit Install or Upgrade Not supported

ESX 4.1 U2 64-bit Install or Upgrade Not supported

ESXi 4.0 U3 64-bit Not supported Install

ESXi 4.1 U2 64-bit Not supported Install

ESXi 5.0 Not supported Install

ESXi 5.0 P1

* Patch Release ESXi500-201109001

NOTE: On a Dell OpenManage upgrade, it is recommended that you upgrade to the

latest open source components available on the DVD.

NOTE: With scripted installation using srvadmin-install.sh or Yum repository-based

installations, the srvadmin-cm RPM that provides 32-bit Inventory Collector does not get installed on a 64-bit operating system. Inventory Collector utility feeds software inventory data to management station applications like ITA. If required, srvadmin-cm package can be installed from appropriate subfolders under SYSMGMT/srvadmin/linux/RPMS/supportRPMS/srvadmin from the Dell Systems Management Tools and Documentation DVD. Since srvadmin-cm RPM requires 32bit version of zlib and compat-libstdc++ libraries, ensure that these libraries are installed on the system.

NOTE: If you are upgrading the operating system to a major version (example, SLES

10 to SLES 11), uninstall the existing version of Dell OpenManage and install the supported version.

NOTE: Before you migrate to a 64-bit version of Dell OpenManage software,

ensure that you uninstall the 32-bit Dell OpenManage and other OpenSource components (openwsman-server, openwsman-client, libwsman1, sblim-sfcb, sblim-sfcc, libcmpiCppImpl0, libsmbios2, smbios-utils-bin) installed as part of the 32-bit Dell OpenManage.

OpenManage 32-bit Architecture OpenManage 64-bit

Architecture

64-bit Not supported Install

The installation scripts and RPM packages specific to supported Linux and VMware ESX operating systems are provided to install and uninstall the Dell OpenManage Server Administrator and other managed system software components. These installation scripts and RPMs are located in the SYSMGMT/srvadmin/linux/supportscripts directory available in the Dell Systems Management Tools and Documentation DVD.

70 Installing Managed System Software on Supported Linux and VMware ESX

Page 71

The install script srvadmin-install.sh allows silent or interactive installation. By including the srvadmin-install.sh script in your Linux scripts, you can install Server Administrator locally or across a network on single or multiple systems.

The second install method uses the Server Administrator RPM packages provided in the custom directories and the Linux rpm command. You can write Linux scripts that install Server Administrator locally or across a network on single or multiple systems.

Using a combination of the two install methods is not recommended and may require that you manually install the required Server Administrator RPM packages provided in the custom directories, using the Linux rpm command.

For information on supported platforms and supported operating systems, see the Dell Systems Software Support Matrix at

support.dell.com/support/edocs/software/omswrels

Software License Agreement

The software license for the Red Hat Enterprise Linux and SUSE Linux Enterprise Server version of the Dell OpenManage software is located on the

Dell Systems Management Tools and Documentation

file. By installing or copying any of the files on the Dell-provided media, you are agreeing to the terms in this file. This file is also copied to the root of the software tree where you install the Dell OpenManage software.

DVD

. Read the license.txt

Server Administrator Device Drivers

Server Administrator includes two device drivers for Linux: Systems Management Base Driver (dcdbas) and BIOS Update Driver (dell_rbu). Server Administrator uses these drivers to perform the systems management functions on supported Linux operating systems. Depending on the system, Server Administrator loads one or both of these drivers if required.

The device drivers for Linux have been released as open source under the GNU General Public License v2.0. They are available in Linux kernels from kernel.org starting with kernel 2.6.14.

Installing Managed System Software on Supported Linux and VMware ESX 71

Page 72

If the Server Administrator drivers are available with the operating system, Server Administrator uses those versions of the drivers. If the Server Administrator drivers are not available with the operating system, Server Administrator uses its Dynamic Kernel Support (DKS) feature to build the drivers when needed.

Dynamic Kernel Support

Server Administrator includes DKS, a feature that Server Administrator uses to build its device drivers automatically for a running kernel if needed.

If you see the following message during Server Administrator Device Drivers startup, then Server Administrator has attempted to use the DKS feature, but was unable to use the feature because certain prerequisites were not met:

Building <driver> using DKS... [FAILED]

where

NOTE: Server Administrator logs messages to the /var/log/messages log file.

To use DKS, identify which kernel is running on the managed system, and check the DKS prerequisites.

Determining the Running Kernel

Type the following command at a console:

root

uname -r

dcdbas

dell_rbu

Press <Enter>.

The system displays a message identifying the running kernel.

Dynamic Kernel Support Prerequisites

For managed system software to use DKS, the following dependencies must be met before starting Server Administrator.

• The running kernel must have loadable module support enabled.

• The source for building kernel modules for the running kernel must be available from Linux Enterprise Server, the

/lib/modules/`uname –r`/build

kernel-source

RPM provides the necessary

. On systems running SUSE

72 Installing Managed System Software on Supported Linux and VMware ESX

Page 73

kernel source. On systems running Red Hat Enterprise Linux, the

kernel-devel

RPMs provide the necessary kernel source for building kernel

modules.

•The GNU

make

utility must be installed. The

make

RPM provides this

utility.

•The GNU C compiler (

gcc

) must be installed. The

gcc

RPM provides this

compiler.

• The GNU linker (ld) must be installed. The

binutils

RPM provides this

linker.

When these prerequisites have been met, DKS automatically builds a device driver when needed during Server Administrator startup.

Using Dynamic Kernel Support After Server Administrator Installation

To enable Server Administrator to support a kernel that is not supported by a precompiled device driver and is loaded after Server Administrator has been installed, perform the following step: Ensure that the DKS prerequisites are met on the managed system and boot the new kernel on the system.

Server Administrator builds a device driver for the kernel running on the system the first time Server Administrator starts after the kernel is loaded. By default, Server Administrator starts during system startup.

Copying a Dynamically Built Device Driver to Systems Running the Same Kernel

When the Server Administrator dynamically builds a device driver for the running kernel, it installs the device driver in the

/lib/modules/

/kernel/drivers/firmware directory, where

is the kernel name (returned by typing uname -r). If you have a system running the same kernel for which a device driver was built, you can copy the newly built device driver to the /var/omsa/dks/

directory on the other system for use by the Server Administrator. This allows the Server Administrator to use DKS on multiple systems without having to install the kernel source on every system.

Installing Managed System Software on Supported Linux and VMware ESX 73

Page 74

For example, System A is running a kernel that is not supported by one of the Server Administrator precompiled device drivers. System B is running the same kernel. Perform the following steps to build a device driver on system A and copy the device driver to system B for use by Server Administrator:

Ensure that the DKS prerequisites are met on system A.

Start Server Administrator on system A.

Server Administrator builds a device driver for the kernel running on system A during startup.

Ty p e

uname -r

on system A to determine the name of the running

kernel.

Copy any

/lib/modules/

the kernel name returned by typing

dcdbas.*

/var/omsa/dks/

dell_rbu.*

kernel/drivers/firmware

files in the

directory on system B, where

uname -r

directory on system A to

is the

in step 3.

NOTE: The /lib/modules/

contain one or more of the following files: dcdbas.* or dell_rbu.*

NOTE: You may have to create the /var/omsa/dks/

system B. For example, if the kernel name is 1.2.3-4smp, you can create the directory by typing: mkdir -p /var/omsa/dks/1.2.3-4smp.

Start Server Administrator on system B.

/kernel/drivers/firmware directory may

directory on

Server Administrator detects that the device driver you copied to the

/var/omsa/dks/

directory supports the running kernel and uses

that device driver.

NOTE: When you have uninstalled Server Administrator from system B, the

/var/omsa/dks/ You must remove the files if they are no longer needed.

<kernel>/*

. files that you copied to system B are not removed.

74 Installing Managed System Software on Supported Linux and VMware ESX

Page 75

OpenIPMI Device Driver

The Server Instrumentation feature of Server Administrator requires the OpenIPMI device driver that provides IPMI-based information and functionality.

All supported Linux systems contain the required version of IPMI module in the default kernel itself. You do not have to install the IPMI RPM. For more information on supported systems, see the Dell Systems Software Support Matrix available at

support.dell.com/support/edocs/software/omswrels

Degradation of Functionality When the Server Administrator Instrumentation Service is Started

After Server Administrator is installed, the Server Administrator Instrumentation Service performs a run-time check of the OpenIPMI device driver whenever it is started. The Server Administrator Instrumentation Service is started whenever you run either the srvadmin-services.sh start or srvadmin-services.sh restart commands, or when you restart the system (during which the Server Administrator Instrumentation Service is started).

Server Administrator installation blocks the installation of Server Administrator packages if an appropriate version of the OpenIPMI device driver is not currently installed on the system. However, it is still possible, though not typical, that you can uninstall or replace a sufficient version of the OpenIPMI device driver after Server Administrator has been installed. Server Administrator cannot prevent this.

To account for a user uninstalling or replacing a sufficient version of the OpenIPMI device driver after Server Administrator has been installed, the Server Administrator Instrumentation Service checks the OpenIPMI device driver version whenever it is started. If a sufficient version of the OpenIPMI device driver is not found, the Server Administrator Instrumentation Service degrades itself so that it does not provide any of the IPMI-based information or functionality. Primarily, this means that it does not provide any probe data (for example, fans, temperatures, and voltage probe data).

Installing Managed System Software on Supported Linux and VMware ESX 75

Page 76

Installing Managed System Software

This section explains how to install managed system software using the following installation options:

•Using the

NOTE: If you have downloaded the managed system software installer

(available as a .tar.gz file) from support.dell.com, the srvadmin-install.sh shell script is present as setup.sh in the root directory.

• Using the RPM command

For information on the various components of Server Administrator available in Dell OpenManage version 7.0 and to help you choose the required components to install, see "Deployment Scenarios for Server Administrator."

Prerequisites for Installing Managed System Software

• You must be logged in as

• The running kernel must have loadable module support enabled.

•The

/etc

•The system must be installed if you use SNMP to manage your server. If you want to use supporting agents for the you must install the operating system support for the SNMP standard before you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system.

srvadmin-install.sh

/opt

directory must have at least 250 MB of free space, and the

, and

/var

directories must each have at least 20 MB of free space.

ucd-snmp

net-snmp

shell script

root

package that is provided with the operating

ucd-snmp

net-snmp

/tmp,

agent,

NOTE: When installing RPM packages, to avoid warnings concerning the

RPM–GPG key, import the key with a command similar to the following:

rpm --import <OM DVD mountpoint>/SYSMGMT/srvadmin/ linux/RPM-GPG-KEY

• In case of Red Hat Enterprise Linux 6, install the wsman and sblim packages from the operating system DVD. To install these packages:

In the

Select

Select the

Package selection

Customize now

System Management

screen, select

and click

group.

Basic Server

76 Installing Managed System Software on Supported Linux and VMware ESX

Page 77

From the sub-category, select the

Web-based Enterprise Management

Optional Packages

option.

The default selected packages are:

• openwsman-client

• sblim-sfcb

• sblim-wbemcli

•wsmancli

Deselect the

Select the

After the operating system installation, install the following package

sblim-wbemcli

openwsman-server

package from the above list.

and click

from the operating system DVD or using the Yum utility:

•libcmpiCppImpl0

• Install all the prerequisite RPMs required for successful installation.

If your system had VMware ESX (version 4.0 or 4.1) factory-installed, Red Hat Enterprise Linux (versions 5.x and 6.0), or SUSE Linux Enterprise Server (version 10 and 11), see the "Dependent RPMs for Remote Enablement" section for information on any RPMs that you need to manually install prior to installing managed system software. Typically, you may not need to manually install any RPMs.

Installing Managed System Software Using Dell-Provided Media

The Dell OpenManage installer uses RPMs to install each component. The media (DVD) is divided into subdirectories to enable easy custom installation.

NOTE: On the Red Hat Enterprise Linux 5.x operating system, DVDs are auto-

mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. Manually mount the DVD and then run executables.

Installing Managed System Software on Supported Linux and VMware ESX 77

Page 78

To review the software before you install it, follow this procedure:

Load the

Dell Systems Management Tools and Documentation

DVD into

your system's DVD drive.

Mount the DVD, if required.

When you have mounted the DVD, navigate to:

<OM DVD mount point>/SYSMGMT/srvadmin/linux/

The installation script and RPM folder are available under the Linux directory.

Express Install

Use the provided shell script to perform the express installation on supported Linux and VMware ESX operating systems.

NOTE: On the Red Hat Enterprise Linux 5.x operating system, DVDs are

auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. Manually mount the DVD and then run executables.

root

to the system running the supported operating system

where you want to install the managed system components.

Insert the

Dell Systems Management Tools and Documentation

DVD into

the DVD drive.

Mount the DVD, if required.

Navigate to

OM DVD mount point>/SYSMGMT/srvadmin/linux/supportscripts

< directory. Run the

srvadmin-install.sh

shell script as follows, which

performs an express installation.

sh srvadmin-install.sh --express

sh srvadmin-install.sh -x

78 Installing Managed System Software on Supported Linux and VMware ESX

Page 79

The setup program installs the following managed system software features:

• Server Administrator Web Server

• Server Instrumentation

• Storage Management

• Remote Access Controller

Remote enablement is not installed and Server Administrator services do not start automatically.

NOTE: The 32-bit srvadmin-cm RPM is not installed when OpenManage is installed

on a 64-bit operating system. If required, the srvadmin-cm package can be installed from the appropriate subfolders under SYSMGMT/srvadmin/linux/RPMS/supportRPMS/srvadmin from the Dell Systems Management Tools and Documentation DVD. Inventory Collector utility carried as part of srvadmin-cm rpm feeds software inventory data to Dell Management Station applications like ITA.

Start the Server Administrator services after the installation using the

srvadmin-services.sh

script by using the

sh srvadmin-services start

command.

Component-Specific Install Using RPM Commands

The RPMs specific to a particular OpenManage component are grouped together. To facilitate

following directories

an RPM-based installation, install the RPMs from the

• SYSMGMT/srvadmin/linux/custom/<OS>/Remote-Enablement/<

• SYSMGMT/srvadmin/linux/custom/<

arch

Instrumentation/<

• SYSMGMT/srvadmin/linux/custom/<

arch

StorageManagement/<

• SYSMGMT/srvadmin/linux/custom/<

>/SA-WebServer/<

>/Server-

>/add-RAC4/<

>/add-RAC5/<

>/add-

>/add-iDRAC/<

arch

Installing Managed System Software on Supported Linux and VMware ESX 79

Page 80

Where <OS> is the supported operating system and <arch> is 32-bit (i386) or 64-bit (x86_64).

NOTE: In case of SUSE Linux Enterprise Server version 10 and 11:

32-bit Dell OpenManage rpm packages are provided for upgrade from the previous 32-bit installs only. If you do not have an existing installation, then you cannot install a 32-bit version of the software. You must install operating system specific rpms from the 64-bit directory.

For example, if you are running Red Hat Enterprise Linux version 5, you can customize the installation by adding the RPMs from the following directories:

SYSMGMT/srvadmin/linux/custom/ RHEL5/addStorageManagement/<arch>

SYSMGMT/srvadmin/linux/custom/ RHEL5/SAWebServer/<arch>

SYSMGMT/srvadmin/linux/custom/ RHEL5/Server-Instrumentation/<arch>

Storage Management component packages

Server Administrator Web Server component packages

Server Instrumentation packages

The DVD provides RPMs that enable repository-based installation using clients such as Yum, Zypper, and Rug. There are RPMs that install the entire set or you can select individual RPMs to install specific components. The RPMs are available at:

SYSMGMT/srvadmin/linux/RPMS/supportRPMS/metaRPMS

NOTE: For a comprehensive list of RPMs and their description, see the "Dell

OpenManage Linux Installer Packages."

The following list of RPMs enables the installation of a particular RPM set.

Table 4-2. Meta RPMs

Meta RPMs Details

srvadmin-all Installs all the components.

srvadmin-base Installs the Server Instrumentation component.

This component has to be installed before installing any of the other specific components.

srvadmin-idrac Installs the iDRAC component.

srvadmin-rac4 Installs the DRAC 4 component.

80 Installing Managed System Software on Supported Linux and VMware ESX

Page 81

Table 4-2. Meta RPMs

Meta RPMs Details

srvadmin-rac5 Installs the DRAC 5 component.

srvadmin-standardAgent Installs the Remote Enablement component.

srvadmin-storageservices Installs the storage services component.

srvadmin-webserver Installs the web server component.

(continued)

The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Remote Enablement feature and the Storage Management Service components.

NOTE: On the Red Hat Enterprise Linux 5.x operating system, DVDs are auto-

mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. You have to manually mount the DVD and then run executables.

root

to the system running the supported operating system

where you want to install the managed system components.

Insert the

Dell Systems Management Tools and Documentation

DVD into

the DVD drive.

Navigate to the operating system specific directory corresponding to your system.

Type the following command:

rpm –ivh Server-Instrumentation/<arch>/*.rpm add-StorageManagement/<arch>/*.rpm RemoteEnablement/<arch>/*.rpm

Server Administrator services do not start automatically.

NOTE: Ensure that you install Server Instrumentation or Remote Enablement

before installing Remote Access Controller or Storage Management.

NOTE: If you choose to install the Remote Enablement feature, ensure that

you install the dependent RPMs before installing this feature. For more information on installing dependent RPMs, see "Dependent RPMs for Remote Enablement."

Installing Managed System Software on Supported Linux and VMware ESX 81

Page 82

Start the Server Administrator services after the installation by using the command:

sh srvadmin-services start

NOTE: You can install Server Administrator on any system that meets

operating system dependencies. However, after installation, certain Server Administrator services may not be started on unsupported systems.

NOTE: When Dell OpenManage Server Administrator is installed on a system,

dependency issues related to RPMs may occur. To resolve these issues, install the missing RPMs from SYSMGMT/srvadmin/linux/RPMS/supportRPMS/opensourcecomponents. If the RPMs are not available in this directory, install these RPMs from the operating system media. If not available on the media, search for these RPMs on the Internet.

Using the Shell Script to Perform the Custom Installation

You can run the Server Administrator Custom Install script in an interactive mode.

The basic usage of the script is:

srvadmin-install.sh [OPTION]...

Server Administrator Custom Installation Utility

This utility runs in interactive mode if you do not specify any options, and runs silently if you provide one or more options.

The options are:

[

-x|--express

other options passed are ignored.

] — Installs all components (including RAC, if available) any

[

-d|--dellagent

[

-c|--cimagent

[

-s|--storage

] — Installs Server Instrumentation components.

] — Installs Remote Enablement components.

] — Installs Storage Management, including Server

Instrumentation.

[

-r|--rac

] — Installs applicable RAC components, including Server

Instrumentation.

[

-w|--web

[

-u|--update

] — Installs Server Administrator Web Server.

] — Updates applicable Server Administrator components.

82 Installing Managed System Software on Supported Linux and VMware ESX

Page 83

[

-h|--help

] — Displays the help text.

Options that can be used along with the options above:

[

-p|--preserve

NOTE: If you do not use the [-p | --preserve] option during the installation, the

history information on the screen gets cleared off.

[

-a|--autostart

] — Preserves the screen without clearing off.

] — Starts the installed services after components have

been installed.

Using the Shell Script to Perform the Installation in Interactive Mode

This installation procedure uses the srvadmin-install.sh to prompt you for the installation of specific components.

root

to the system running the supported operating system

where you want to install the managed system components.

Insert the

Dell Systems Management Tools and Documentation

DVD into

the DVD drive.

Mount the DVD, if required.

Navigate to

OM DVD mount point>/SYSMGMT/srvadmin/linux/supportscripts

Execute the script with the

sh srvadmin-install.sh

command

and accept the terms of the end-user license agreement.

Executing the command displays a list of component options. If any of the components are already installed, then those components are listed separately with a check mark next to them. The Server Administrator installation options are displayed.

Press <c> to copy, <i> to install, <r> to reset and start over, or <q> to quit. If you press <c>, you are prompted to enter the absolute destination path.

When the installation is complete, the script has an option for starting the services.

Press <y> to start the services or <Enter> to exit.

Installing Managed System Software on Supported Linux and VMware ESX 83

Page 84

Using the Install Script To Run in the Silent Mode

Perform the following steps for a silent installation using the srvadmin-install.sh shell script:

Log on as

root

to the system running the supported operating system

where you want to install the managed system components.

Insert the

Dell Systems Management Tools and Documentation

the DVD drive.

Mount the DVD, if required.

Navigate to <

point

To install the Storage Management Service components, type the

OM DVD mount

SYSMGMT/srvadmin/linux/supportscripts

following command:

sh srvadmin-install.sh --storage

(long options)

sh srvadmin-install.sh -s

NOTE: Long options can be combined with short options, and vice-versa.

(short options)

Server Administrator services do not start automatically.

Start Server Administrator services after the installation by typing the command:

sh srvadmin-services start

DVD into

NOTE: After installing Server Administrator, log out and then log in again to access

the Server Administrator Command Line Interface (CLI).

Determining the OpenManage Server Administrator Architecture

Use the following command to identify if the already installed OpenManage Server Administrator is of 32-bit or 64-bit architecture:

rpm -q --queryformat "%{NAME} - %{ARCH}\n" `rpm -qa | grep srvadmin`

The system displays a message identifying the architecture where, i386 refers to 32-bit and x86_64 refers to 64-bit.

84 Installing Managed System Software on Supported Linux and VMware ESX

Page 85

Managed System Software Installation Using Third-Party Deployment Software

You can use third-party deployment software, such as Altiris Deployment Solution, to install managed system software on supported Dell servers. To distribute and install managed system software using Altiris, start your Altiris application and import OpenManage_Jobs.bin located at

SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder to import

OpenManage_Jobs.bin. You might need to modify the Run Script and Copy File tasks to match your deployment environment. Once complete, you can

then schedule your job to run on the supported Dell systems that are managed from within your Altiris Deployment Solution.

Uninstalling Managed System Software

To uninstall Managed System Software, you must be logged in as root.

Uninstalling Managed System Software Using the Uninstall Script

An uninstallation script is installed when you install Server Administrator. You can execute the script by typing srvadmin-uninstall.sh and then pressing <Enter>.

Uninstalling Managed System Software Using the RPM Command

The individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage. Following are examples:

To uninstall only the Server Administrator Web Server, use this command:

rpm –e `rpm -qa | grep srvadmin-iws`

During an uninstallation, files in which user settings are made are preserved with the .rpmsave file extension. Log files are also preserved after the uninstallation.

Installing Managed System Software on Supported Linux and VMware ESX 85

Page 86

86 Installing Managed System Software on Supported Linux and VMware ESX

Page 87

Installing Managed System Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server

The Server Core installation option of the Microsoft Windows Server 2008 and Hyper-V Server operating system provides a minimal environment for running specific server roles that reduce the maintenance and management requirements and the attack surface for those server roles. AWindows Server 2008 Core or Hyper-V Server installation installs only a subset of the binaries that are required by the supported server roles. For example, the Explorer shell is not installed as part of a Windows Server 2008 Core or Hyper-V Server installation. Instead, the default user interface for a Windows Server 2008 Core or Hyper-V Server installation is the command prompt.

NOTE: Windows Server 2008 Core or Hyper-V Server operating system does not

support a graphical user interface (GUI) based installation of Dell OpenManage software components. You need to install OpenManage software in the Command Line Interface (CLI) mode on Server Core. For more information on Server Core, see microsoft.com.

NOTE: On Windows 7, to install the systems management software successfully,

you must log in using an account which belongs to the Administrators Group and must execute the setup.exe using the option Run as administrator from the rightclick menu.

NOTE: You have to log in as a built-in administrator to install the systems

management software on Windows Server 2008 and Windows Vista. For more information about the built-in Administrator account, see the Windows Server 2008 Help.

Running Prerequisite Checker In CLI Mode

You must run the prerequisite checker in the CLI mode as Windows Server 2008 and Hyper-V Server does not support the GUI mode. For more information, see "Prerequisite Checker."

Installing Dell OpenManage Software On Windows Server 2008 87

Page 88

Installing Managed System Software in CLI Mode

Launch the MSI file from the command prompt using the command

msiexec /i SysMgmt.msi The MSI file SysMgmt.msi is located at SYSMGMT\srvadmin\windows\SystemsManagement on the Dell Systems

Management Tools and Documentation DVD.

To install the localized version of the managed system software, type

msiexec /I SysMgmt.msi TRANSFORMS= <languauge_transform>.mst in the command prompt. Replace

<language_transform>.mst with the appropriate language file:

•

1031.mst

•

1034.mst

•

1036.mst

•

1041.mst

•

2052.mst

NOTE: For more information on optional command line settings for the MSI

installer, see "Command Line Settings for MSI Installer."

(German)

(Spanish)

(French)

(Japanese)

(Simplified Chinese)

Uninstalling Systems Management Software

To uninstall managed system software, type msiexec /x sysmgmt.msi in the command prompt.

88 Installing Dell OpenManage Software On Windows Server 2008

Page 89

Installing Dell OpenManage Software on VMware ESXi

VMware ESXi is factory-installed on some Dell systems. For a list of these systems, see the latest Dell Systems Software Support Matrix at

support.dell.com/support/edocs/software/omswrels

Administrator Web Server version 7.0 to access VMware ESXi 4.0 U3, VMware ESXi 4.1 U2, VMware ESXi 5.0, and VMware ESXi 5.0 P1 systems.

Dell OpenManage Server Administrator is available as a .zip file for installing on systems running VMware ESXi. The zip file, OM-SrvAdmin-Dell-Web-

7.0.0-<bldno>.VIB-ESX<version>i_<bld-revno>.zip, where <version> is the supported ESXi version, is available for download at support.dell.com.

Download VMware vSphere Command Line Interface (vSphere CLI) from vmware.com and install on your Microsoft Windows or Linux system. Alternately, you can import VMware vSphere Management Assistant (vMA) to your ESXi host.

Using the vSphere CLI

To install Dell OpenManage software on VMware ESXi using the vSphere CLI:

Copy and unzip the ESX<version>i_<bld-revno>.zip file ESXi 5.0 and ESXi 5.0 P1, copy the file to the folder on the ESXi 5.0 or ESXi 5.0 P1 server.

Shut down all guest operating systems on the ESXi host and put the ESXi host in maintenance mode.

If you are using vSphere CLI on Windows, navigate to the directory where you have installed the vSphere CLI utilities.

If you are using vSphere CLI on Linux, you can execute the command from any directory.

OM-SrvAdmin-Dell-Web-7.0.0-<bldno>.VIB-

. You can use Server

to a directory on your system. For

/var/log/vmware

Installing Dell OpenManage Software on VMware ESXi 89

Page 90

Execute the following command:

For VMware ESXi4.0/ESXi 4.1:

vihostupdate.pl --server <IP address of ESXi host>

-i -b <path to Dell OpenManage file>

For VMware ESXi 5.0/ESXi5.0 P1

esxcli --server <IP Address of ESXi 5.0 host> software vib install -d /var/log/vmware/<Dell OpenManage file>

NOTE: The .pl extension is not required if you are using vSphere CLI on Linux.

Enter the root username and password of the ESXi host when prompted.

The command output displays a successful or a failed update. In case of a failed update, see "Troubleshooting."

Restart the ESXi host system.

Using the VMware vSphere Management Assistant (vMA)

The vMA allows administrators and developers to run scripts and agents to manage ESX/ESXi systems. For more information on vMA, see vmware.com/support/developer/vima/.

Log on to vMA as an administrator and provide the password when prompted.

Copy and unzip the ESX<version>i_<bld-revno>.zip

Shut down all guest operating systems on the ESXi host and put the ESXi host in maintenance mode.

In vMA, execute the following command:

For VMware ESXi4.0/ESXi 4.1:

OM-SrvAdmin-Dell-Web-7.0.0-<bldno>.VIB-

file to a directory on the vMA.

vihostupdate --server <IP address of ESXi Host> -i

-b <path to Dell OpenManage file>

For VMware ESXi 5.0/ESXi 5.0 P1

esxcli --server <IP Address of ESXi 5.0 host> software vib install -d /var/log/vmware/<Dell OpenManage file>

90 Installing Dell OpenManage Software on VMware ESXi

Page 91

Enter the root username and password of the ESXi host when prompted.

The command output displays a successful or a failed update. In case of a failed update, see "Troubleshooting."

Restart the ESXi host system.

When you run the command, the following components are installed on your system:

• Server Administrator Instrumentation Service

• Remote Enablement

• Server Administrator Storage Management

• Remote Access Controller

You must install the Server Administrator Web Server separately on a management station. For information on installing the Server Administrator Web Server, see "Installing Managed System Software on Microsoft Windows Operating Systems" and "Installing Managed System Software on Supported Linux and VMware ESX."

After installing Server Administrator, you have to enable Server Administrator Services. For information on enabling these services, see "Enabling Server Administrator Services on the Managed System."

Enabling Server Administrator Services on the Managed System

The Server Administrator Web Server communicates with the VMware ESXi system through the Server Administrator Common Interface Model (CIM) provider. The Server Administrator CIM provider is an Original equipment manufacturer (OEM) provider on the VMware ESXi system. CIM OEM providers are disabled by default on VMware ESXi 4.0 and ESXi 4.1. You must enable the CIM OEM providers on the VMware ESXi system before accessing it using Server Administrator Web Server.

NOTE: In ESXi 4.1 U2, ESXi 5.0 and ESXi 5.0 P1 Dell OpenManage CIM OEM provider

is enabled by default.

Installing Dell OpenManage Software on VMware ESXi 91

Page 92

Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi4.0/ESXi 4.1)

To enable CIM OEM providers using VMware vSphere Client, you must have the vSphere Client tool installed. You can download and install the tool from https://<IP_address of ESXi host> where <ip_address> is the IP address of the VMware ESXi system.

To enable CIM OEM providers on the VMware ESXi system using vSphere Client:

Log on to the VMware ESXi host system using vSphere Client.

Click the

Under the

In the

Change the value of the

CIMoemProviderEnabled

Click OK.

For the changes to take effect without restarting the system, use the

Restart Management Agents

(DCUI) on the local console of the VMware ESXi system.

If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi host system.

Configuration

Software

Advanced Settings

NOTE: This option is available under Troubleshooting Options in ESXi 4.1.

tab.

section on the left side, click

dialog box, click

CIMOEMProvidersEnabled

(for ESXi 4.1) field to 1.

option in the Direct Console User Interface

UserVars

Advanced Settings

on the left pane.

(for ESXi 4.0) or

92 Installing Dell OpenManage Software on VMware ESXi

Page 93

Enabling CIM OEM Providers Using vSphere CLI (for VMware ESXi

4.0/ESXi 4.1)

If you are using vSphere CLI on Windows, navigate to the directory where you have installed the vSphere CLI utilities. On Linux, proceed to step 2.

Execute the following command:

vicfg-advcfg.pl --server <ip_address of ESXi host>

--username <user_name> --password <password> --set 1 UserVars.CIMOEMProvidersEnabled

NOTE: For ESXi 4.0, use CIMOEMProvidersEnabled and for ESXi 4.1, use

CIMoemProviderEnabled. The .pl extension is not required if you are using vSphere CLI on Linux.

For the changes to take effect without restarting the system, use the

Restart Management Agents

option in the DCUI on the local console of

the VMware ESXi system.

NOTE: This option is available under Troubleshooting Options in ESXi 4.1.

If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi host system.

Enabling CIM OEM Providers Using vMA (for VMware ESXi 4.0/ESXi 4.1)

Execute the following command:

vicfg-advcfg --server <ip_address of ESXi host> -username <user_name> --password <password> --set 1 UserVars.CIMOEMProvidersEnabled

NOTE: For ESXi 4.0, use CIMOEMProvidersEnabled and for ESXi 4.1, use

CIMoemProviderEnabled.

For the changes to take effect without restarting the system, use the

Restart Management Agents

option in the DCUI on the local console of

the VMware ESXi system.

If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi host system.

Installing Dell OpenManage Software on VMware ESXi 93

Page 94

Uninstalling the Existing OpenManage VIB

The following command can be used to uninstall the existing OpenManage VIB:

vihostupdate.pl --server <IP Address> -r -B Dell_OpenManage_ESXi_OM640

Reboot the system after uninstalling.

Configuring the SNMP Agent on Systems Running VMware ESXi

Server Administrator generates Simple Network Management Protocol (SNMP) traps in response to changes in the status of sensors and other monitored parameters. You must configure one or more trap destinations on the system running Server Administrator to send SNMP traps to a management station.

Server Administrator supports SNMP traps on VMware ESXi but does not support SNMP Get and Set operations because VMware ESXi does not provide the required SNMP support. You can use the VMware vSphere CLI to configure VMware ESXi to send SNMP traps to a management application such as IT Assistant.

NOTE: For more information about using the VMware vSphere CLI, see the

VMware support site at vmware.com/support.

Configuring Your System to Send Traps to a Management Station Using the vSphere CLI

Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator to send SNMP traps to a management station.

Configure your ESXi system running Server Administrator to send traps to a management station:

Install the VMware vSphere CLI.

Open a command prompt on the system in which the vSphere CLI is installed.

94 Installing Dell OpenManage Software on VMware ESXi

Page 95

Navigate to the directory in which the vSphere CLI is installed. The default location on Linux is

/usr/bin

Files\VMware\VMware vSphere CLI\bin

Configure the SNMP setting using the following command:

and on Windows is

C:\Program

vicfg-snmp.pl --server <server> --username <username> --password <password> -c <community> -t <hostname>@162/<community>

where < < the ESXi user, < <

Enable SNMP using the following command:

server

> is the hostname or IP address of the ESXi system,

username

hostname

NOTE: If you do not specify a user name and password, you are prompted to

> is a user on the ESXi system, <

community

> is the SNMP community name and

password

> is the password of

> is the hostname or IP address of the management station.

specify the same.

vicfg-snmp.pl --server <server> --username <username> --password <password> -E

View the SNMP configuration using the following command:

vicfg-snmp.pl --server <server> --username <username> --password <password> -s

Test the SNMP configuration using the following command:

vicfg-snmp.pl --server <server> --username <username> --password <password> -T

NOTE: The .pl extension is not required if you are using vSphere CLI on Linux or

using vMA.

The SNMP trap configuration takes effect immediately without restarting any services.

Installing Dell OpenManage Software on VMware ESXi 95

Page 96

Troubleshooting

• When attempting to use the error may be displayed:

unpacking c:\OM-SrvAdmin-Dell-Web-7.0.0<bldno>.VIB-ESX<version>i_<bld-revno>.zip

metadata.zip.sig does not exist

signature mismatch : metadata.zip

Unable to unpack update package.

This error is displayed if you are using an older version of the Remote CLI. To resolve this issue, download and install the latest vSphere version of the CLI.

• When attempting to use the error may be displayed:

Unable to create, write or read a file as expected.I/O Error (28) on file : [Errno 28] No space left on device.

See the VMware KB article 1012640 at

vihostupdate

kb.vmware.com

command, the following

to fix this error.

96 Installing Dell OpenManage Software on VMware ESXi

Page 97

Installing Dell OpenManage Software on Citrix XenServer

The Dell OpenManage Server Administrator is installed on Citrix XenServer using the Dell OpenManage Supplemental Pack. The OpenManage Supplemental Pack for Citrix XenServer 6.0 can be installed in two ways:

• During the installation of XenServer

Start the installation of XenServer as usual and follow the instructions on the screen.

One of the early questions during the installation process of XenServer

Yes

is if you want to install any Supplemental Packs; click continue with the installation process.

After the base XenServer image is installed (5-10 minutes depending on the speed of your system), you are prompted to insert your Supplemental Pack CD. Eject the XenServer installation CD from the optical drive, insert the Dell OpenManage Supplemental Pack CD

and click

was found

. The message '

' is displayed. To confirm installation, click

OpenManage Supplemental Pack

and

Use

and click

NOTE: If you have more than one Supplemental Pack, (either the Linux

Supplemental Pack from Citrix or other third-party applications) you can install them in any order, although it is recommended that you install the Dell OpenManage Supplemental Pack last.

After completing the Dell OpenManage Supplemental Pack

installation (2-5 minutes, depending on the speed of your system), you are prompted to install other Supplemental Packs. If you do not

Skip

want to install other supplemental packs, click <Enter>. The XenServer is installed successfully.

NOTE: When installing RPM packages, to avoid warnings concerning the

RPM–GPG key, import the key with a command similar to the following:

rpm --import<OM DVD mountpoint>/ SYSMGMT/srvadmin/linux/RPM-GPG-KEY

Installing Dell OpenManage Software on Citrix XenServer 97

and press

Page 98

• On a running system

Burn the Supplemental Pack ISO file to a CD/DVD or download the ISO file to your server.

If you are downloading the ISO file, mount it on a temporary directory as follows:

$ mount -o loop <openmanange-supplemental-packfilename>.iso /mnt

If you burned the ISO file to a CD/DVD, insert it in the optical drive and run:

$ mount /dev/cdrom /mnt

Install the supplemental pack:

$ cd /mnt

$ ./install.sh

$ xe-install-supplemental-pack <openmanangesupplemental-pack-filename>.iso

NOTE: If a previous version of OpenManage is already installed on the system, then

the command to upgrade it to version 7.0 is

./install.sh.

After the installation or upgrade of OpenManage, execute the following post-installation configuration script of Remote Enablement feature

$ cd /opt/dell/srvadmin/etc

$ ./autoconf_cim_component.sh -p 5986

When the installation is complete, unmount the ISO file or CD:

$ cd ..

$ umount /mnt

CAUTION: Removal of the Dell OpenManage Supplemental Pack or any Dell

OpenManage RPMs is not supported by Dell or Citrix and it is not recommended. Manual removal of any RPM leaves the system in an inconsistent state which could make any potential issue debugging effort difficult or impossible. A future Supplemental Pack release supports removal of the Dell OpenManage Supplemental Pack.

98 Installing Dell OpenManage Software on Citrix XenServer

Page 99

If the XenServer image is upgraded to a newer XenServer update or release, the Dell OpenManage Supplemental Pack must be reinstalled since the new XenServer image is placed on a different partition from the original. In this case, follow the same installation instructions as before. However, any Dell OpenManage configuration settings saved on your server is lost.

For more information on using Dell OpenManage with Citrix XenServer Dell Edition, see the Citrix XenServer Dell Edition Solution Guide at support.dell.com/support/edocs/software/Citrix/.

NOTE: If you are connecting to a XenServer 6.0 managed node using server

administrator web server, use port 5986 in the format Hostname:Port Number, or IP address:Port Number.

Post Installation Tasks

After the installation or upgrade of OpenManage:

Execute the post installation configuration scripts of Remote Enablement feature:

$ cd /opt/dell/srvadmin/etc

$ ./autoconf_cim_component.sh -p 5986

Restart openwsman and sfcb services:

$ /etc/init.d/openwsmand restart

$ /etc/init.d/sfcb restart

Open the port 5986:

$ iptables -I RH-Firewall-1-INPUT -p tcp --destination-port 5986 -j ACCEPT

Start the Server Administrator services:

$ sh srvadmin-services start

Installing Dell OpenManage Software on Citrix XenServer 99

Page 100

100 Installing Dell OpenManage Software on Citrix XenServer

Dell OpenManage Server Administrator Version 7.0 Installation Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Introduction

Dell OpenManage Systems Management Software

Security Features

Other Documents You Might Need

Getting Technical Assistance

Preinstallation Setup

Prerequisite Checker

Installation Requirements

Supported Operating Systems and Web Browsers

Multilingual User Interface Support

Viewing Localized Versions of the Web-Based Interface

System Requirements

Digital Certificates

Enabling Windows Installer Logging Service

Microsoft Active Directory

Configuring the SNMP Agent

Secure Port Server and Security Setup

Setting User and Server Preferences

X.509 Certificate Management

Remote Enablement Requirements

Installing WinRM

Dependent RPMs for Remote Enablement

Post-Installation Configuration for Remote Enablement

Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems

Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating System

Workaround for the Libssl Issue

Installing Managed System Software on Microsoft Windows Operating Systems

Deployment Scenarios for Server Administrator

Installing Server Administrator

Typical Installation

Custom Installation

Server Administrator Installation With Citrix Application Server

Performing an Unattended Installation of Managed System Software

Managed System Software Installation Using Third-Party Deployment Software

System Recovery on Failed Installation

Failed Updates

Upgrading Managed System Software

Upgrading Guidelines

Upgrade

Modify

Repair

Uninstalling Managed System Software

Uninstalling Managed System Software Using Dell-Provided Media

Uninstalling Managed System Software Features Using the Operating System

Unattended Uninstall Using the Product GUID

Unattended Uninstallation of Managed System Software

Installing Managed System Software on Supported Linux and VMware ESX

Software License Agreement

Server Administrator Device Drivers

Dynamic Kernel Support

OpenIPMI Device Driver

Degradation of Functionality When the Server Administrator Instrumentation Service is Started

Installing Managed System Software

Prerequisites for Installing Managed System Software

Installing Managed System Software Using Dell-Provided Media

Server Administrator Custom Installation Utility

Managed System Software Installation Using Third-Party Deployment Software

Uninstalling Managed System Software

Uninstalling Managed System Software Using the Uninstall Script

Uninstalling Managed System Software Using the RPM Command

Installing Managed System Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server

Running Prerequisite Checker In CLI Mode

Installing Managed System Software in CLI Mode

Uninstalling Systems Management Software

Installing Dell OpenManage Software on VMware ESXi

Using the vSphere CLI

Using the VMware vSphere Management Assistant (vMA)

Enabling Server Administrator Services on the Managed System

Enabling CIM OEM Providers Using vSphere Client (for VMware ESXi4.0/ESXi 4.1)

Enabling CIM OEM Providers Using vMA (for VMware ESXi 4.0/ESXi 4.1)

Configuring the SNMP Agent on Systems Running VMware ESXi

Configuring Your System to Send Traps to a Management Station Using the vSphere CLI

Troubleshooting

Installing Dell OpenManage Software on Citrix XenServer

Post Installation Tasks