Dell OpenManage Server Administrator Version 7.1 Installation Manual

Dell OpenManage Server Administrator Version 7.1 Installation Guide

Notes, Cautions, and Warnings

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

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2012 Dell Inc.

Trademarks used in this text: Dell™, the Dell logo, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™,
PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell
Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD
is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc.
Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks
or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat
Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are
registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation
and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in
the United States and/or other countries. VMware
trademarks of VMware, Inc. in the United States or other countries.
Corporation.

2012 - 06

®

,

Virtual SMP

®

®

,

vMotion

®

is a registered trademark of International Business Machines

IBM

,

vCenter

®

and

vSphere

®

are registered trademarks or

®

®

Rev. A00

Contents

Notes, Cautions, and Warnings...................................................................................................2

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

Dell OpenManage Systems Management Software................................................................................................9

Server Administrator Components on a Managed System................................................................................9

Security Features....................................................................................................................................................11

Other Documents You Might Need.........................................................................................................................11

Getting Technical Assistance.................................................................................................................................12

2 Preinstallation Setup................................................................................................................13

Prerequisite Checker..............................................................................................................................................13

Installation Requirements.......................................................................................................................................15

Supported Operating Systems and Web Browsers.........................................................................................15

Multilingual User Interface Support.................................................................................................................16

Viewing Localized Versions of the Web-Based Interface...............................................................................16

System Requirements......................................................................................................................................16

Digital Certificates............................................................................................................................................17

Enabling Windows Installer Logging Service..................................................................................................17

Microsoft Active Directory...............................................................................................................................18

Configuring SNMP Agents......................................................................................................................................18

Secure Port Server and Security Setup.................................................................................................................19

Setting User and Server Preferences..............................................................................................................19

X.509 Certificate Management.........................................................................................................................20

Remote Enablement Requirements........................................................................................................................21

Installing WinRM..............................................................................................................................................21

Certificate Authority Signed Self-Signed Certificate.......................................................................................21

Dependent RPMs for Remote Enablement.......................................................................................................24

Post-Installation Configuration for Remote Enablement..................................................................................25

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

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

Workaround for the Libssl Issue.............................................................................................................................28

3 Installing Managed System Software on Microsoft Windows Operating Systems .....29

Deployment Scenarios for Server Administrator...................................................................................................29

Installing Server Administrator .......................................................................................................................30

System Recovery on Failed Installation..................................................................................................................36

Failed Updates..................................................................................................................................................36

Upgrading Managed System Software..................................................................................................................37

Upgrading Guidelines.......................................................................................................................................37

Upgrade............................................................................................................................................................37

Modify...............................................................................................................................................................38

Repair...............................................................................................................................................................39

Uninstalling Managed System Software................................................................................................................39

Uninstalling Managed System Software Using Dell-Provided Media.............................................................39

Uninstalling Managed System Software Features Using the Operating System.............................................40

Unattended Uninstall Using the Product GUID................................................................................................40

Unattended Uninstallation of Managed System Software...............................................................................40

4 Installing Managed System Software on Supported Linux and VMware ESX...............43

Software License Agreement.................................................................................................................................44

Server Administrator Device Drivers......................................................................................................................44

Dynamic Kernel Support..................................................................................................................................44

OpenIPMI Device Driver.........................................................................................................................................46

Degradation of Functionality When the Server Administrator Instrumentation Service is Started................46

Installing Managed System Software....................................................................................................................46

Prerequisites for Installing Managed System Software..................................................................................46

Installing Managed System Software Using Dell-Provided Media..................................................................47

Server Administrator Custom Installation Utility..............................................................................................50

Managed System Software Installation Using Third Party Deployment Software..........................................51

Uninstalling Managed System Software................................................................................................................52

Uninstalling Managed System Software Using the Uninstall Script................................................................52

Uninstalling Managed System Software Using the RPM Command...............................................................52

5 Installing Managed System Software On Microsoft Windows Server 2008 Core

and Microsoft Hyper-V Server...................................................................................................53

Running Prerequisite Checker In CLI Mode...........................................................................................................53

Installing Managed System Software in CLI Mode................................................................................................53

Uninstalling Systems Management Software........................................................................................................54

6 Installing Dell OpenManage Software on VMware ESXi...................................................55

Using the vSphere CLI............................................................................................................................................55

Using the VMware vSphere Management Assistant (vMA)..................................................................................56

Using the VMWare Update Manager (VUM)..........................................................................................................56

Using the Power CLI...............................................................................................................................................57

Enabling Server Administrator Services on the Managed System........................................................................57

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

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

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

Uninstalling the Existing OpenManage VIB.....................................................................................................59

Configuring the SNMP Agent on Systems Running VMware ESXi........................................................................59

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

Troubleshooting......................................................................................................................................................60

7 Installing Dell OpenManage Software on Citrix XenServer ..............................................61

During the installation of XenServer.......................................................................................................................61

On a Running System..............................................................................................................................................61

XenServer Upgrade................................................................................................................................................62

Post Installation Tasks............................................................................................................................................62

8 Using Microsoft Active Directory...........................................................................................63

Active Directory Schema Extensions.....................................................................................................................63

Overview of the Active Directory Schema Extensions....................................................................................63

Active Directory Object Overview....................................................................................................................63

Active Directory objects in multiple domains..................................................................................................65

Setting up Server Administrator Active Directory Objects in Multiple Domains.............................................66

Configuring Active Directory to Access the Systems......................................................................................67

Configuring the Active Directory Product Name.............................................................................................68

Extending the Active Directory Schema.................................................................................................................68

Using the Dell Schema Extender......................................................................................................................69

Active Directory Users and Computers Snap-In..............................................................................................72

Installing the Dell Extension to the Active Directory Users and Computers Snap-In......................................72

Adding Users and Privileges to Active Directory.............................................................................................73

9 Frequently Asked Questions....................................................................................................77

How do I install Dell OpenManage Server Administrator with only the CLI features?...........................................77

What ports do Dell OpenManage applications use?..............................................................................................77

When I run virtual media on the DRAC controller over a Wide Area Network (WAN) with low bandwidth

and latency, launching Dell OpenManage Install directly on the virtual media failed, what do I do?...................77

Do I need to uninstall the Adaptec Fast Console application installed on the system before installing the

Server Administrator Storage Management Service?...........................................................................................77

Microsoft Windows................................................................................................................................................77

How do I fix a faulty installation of Server Administrator?...............................................................................77

What do I do when the creation of WinRM listener fails with the following error message?.........................78

What are the firewall-related configuration that needs to be done for WinRM?............................................78

When launching the Dell OpenManage Install, an error message may display, stating a failure to load

a specific library, a denial of access, or an initialization error. An example of installation failure during

Dell OpenManage Install is "failed to load OMIL32.DLL." What do I do?..........................................................78

I get a misleading warning or error message during Dell OpenManage installation......................................78

I am getting the following error message while launching Dell OpenManage Install:....................................78

Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe?..........79

When I run Dell OpenManage Install, I see unreadable characters on the Prerequisite check

information screen...........................................................................................................................................79

I have installed Server Administrator and Dell Online Diagnostics in the same directory and Dell

Online Diagnostics fails to work, what do I do?...............................................................................................79

I have installed Server Administrator using remote Server Administrator deploy on Windows Server

2008, I do not see Server Administrator icon on the desktop?

I see a warning message while uninstalling Server Administrator on Windows Server 2008 as the

installer tries to remove the shortcut?.............................................................................................................79

Where can I find the MSI log files? .................................................................................................................79

I downloaded the Server Administrator files for Windows from the Dell Support website and copied it

to my own media. When I tried to launch the SysMgmt.msi file, it failed. What is wrong?.............................79

Does Dell OpenManage Install support Windows Advertised installation?....................................................80

How do I check the disk space availability during custom installation?.........................................................80

What do I do when I see the current version is already installed message is displayed?..............................80

What is the best way to use the prerequisite checker information?...............................................................80

In the Prerequisite Checker screen, I get the following message. What can I do to resolve this problem?...80

Is the time shown during installation or uninstallation by Windows Installer Services accurate?.................81

Can I launch my installation without running the prerequisite checker? How do I do that?...........................81

How do I know what version of systems management software is installed on the system?.........................81

Do I need to reboot the system after upgrading the Dell OpenManage?........................................................81

Where can I see the Server Administrator features that are currently installed on my system?...................81

What are the names of all the Dell OpenManage features under Windows?.................................................81

Red Hat Enterprise Linux or SUSE Linux Enterprise Server...................................................................................82

After installing Server Administrator, I cannot log in.......................................................................................82

I see the following message when I try to install Server Administrator on a guest Linux operating

system..............................................................................................................................................................82

I manually installed my Red Hat Enterprise Linux 4 64-bit operating system and can see RPM

dependencies while installing Server Administrator. Where can I find these dependent RPM files?............82

I have performed a non-default install of the Linux operating system using the Linux operating system

media, I see missing RPM file dependencies while installing Server Administrator?.....................................82

Where can I find the source packages for Open Source RPMs?....................................................................83

What do I do when management station RAC utility installation fails due to missing RPM file?....................83

When using the rpm -e 'rpm -qa | grep srvadmin' command to remove Dell OpenManage systems

management software, some RPM utility versions may schedule an uninstallation in an incorrect

order, which results in users encountering misleading warning or error messages. What is the

solution?...........................................................................................................................................................83

What do I do when I am asked to authenticate using the root user account?................................................83

Why am I getting a warning concerning the RPM package key during installation?......................................83

What are the names of all the Dell OpenManage features under Red Hat Enterprise Linux or SUSE

Linux Enterprise Server?..................................................................................................................................84

What do the directories under srvadmin/linux/custom/<operating system> contain?....................................84

.........................................................................79

What are the additional components that can be installed on a system that already has Server

Administrator installed?...................................................................................................................................88

What happens if I install the RPM package on an unsupported system or on an unsupported

operating system?............................................................................................................................................89

What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems

after Server Administrator is started?

What kernel modules are loaded when Server Administrator is started?.......................................................90

..............................................................................................................89

10 Dell OpenManage Linux Installer Packages......................................................................91

8

1

Introduction

This topic 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 the 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 the Dell systems
with proactive monitoring, notification, and remote access.

Dell OpenManage systems management software comprises of two DVDs:

•

Dell Systems Management Tools and Documentation

•

Dell OpenManage Server Update Utility

NOTE: For more information on these DVDs, see

Guide

at support.dell.com/manuals.

Dell OpenManage Management Station Software Installation

Server Administrator Components on a Managed System

The setup program provides the following options:

• Custom Setup

• Typical Setup

The custom setup option enables you to select the software components you want to install. The Managed System

Software Components table lists the various managed system software components that you can install during a custom

installation.

Table 1. Managed System Software Components

Component What is installed Deployment Scenario Systems to install on

Server Administrator Web
Server

Server Instrumentation Server Administrator CLI

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

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 the system as
the managed system.
Installing Server

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

Supported Dell PowerEdge
systems. For a list of
supported Dell PowerEdge

9

Component What is installed Deployment Scenario Systems to install on

Instrumentation and the
Server Administrator Web
Server installs Server
Administrator. Use Server
Administrator to monitor,
configure, and manage the
system.

NOTE: If you choose to
install only Server
Instrumentation (without
selecting Remote
Enablement), you must
also install the Server
Administrator Web
Server.

systems, see the

Dell
Systems Software Support
Matrix

at support.dell.com/

manuals.

Storage Management Server Administrator

Storage Managementthe

Remote Enablement Server Administrator CLI

and Instrumentation Service
and CIM Provider

Remote Access Controller Server Administrator CLI

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

Install to implement
hardware RAID solutions
and configure the storage
components attached to the
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/manuals.

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

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

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/

manuals.

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

10

Component What is installed Deployment Scenario Systems to install on

you diagnose the probable
cause of a system crash.

Intel SNMP Agent

Broadcom SNMP Agent Broadcom SNMP Agent Install to enable Server

Related Links:

Custom Installation

Intel Simple Network
Management Protocol
(SNMP) Agent

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

Administrator to obtain
information about NICs.

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

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

Security Features

Dell OpenManage systems management software components provide these security features:

• Authentication for users from Operating System with different privilege levels, 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.

NOTE: Applicable only for systems running Red Hat Enterprise Linux or SUSE Linux Enterprise Server or VMware
ESX/ESXi.

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

• SSL encryption (Auto Negotiate and 128-bit or higher.)

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
support.dell.com/manuals.

Dell OpenManage Server Administrator User’s Guide

at

Other Documents You Might Need

In addition to this guide, access the following guides available on the Dell Systems Management Tools and
Documentation DVD or at support.dell.com/manuals. On the Manuals page, click Software → Systems Management.
Click the appropriate product link on the right-side to access the documents.

11

• The

Dell Lifecycle Controller 2 Version 1.00.00 User's Guide

Controller.

• The

Dell Management Console User’s Guide

Management Console.

• The

Dell Systems Build and Update Utility User’s Guide

Update Utility.

• The

Dell Systems Software Support Matrix

systems supported by these systems, and the Dell OpenManage components that can be installed on these
systems.

• The

Dell OpenManage Server Administrator User's Guide

Administrator.

• The

Dell OpenManage Server Administrator SNMP Reference Guide

information base (MIB.)

• The

Dell OpenManage Server Administrator CIM Reference Guide

(CIM) provider, which is an extension of the standard management object format (MOF) file. This guide explains
the supported classes of management objects.

• The

Dell OpenManage Server Administrator Messages Reference Guide

on the Server Administrator home page Alert log, or on the operating system’s event viewer. This guide explains
the text, severity, and cause of each alert message that the Server Administrator displays.

• The

Dell OpenManage Server Administrator Command Line Interface Guide

line interface for Server Administrator, including an explanation of CLI commands to view system status, access
logs, create reports, configure various component parameters, and set critical thresholds.

• The

Dell OpenManage IT Assistant User’s Guide

Assistant.

• The

Dell Remote Access Controller 5 User’s Guide

configuring a DRAC 5 controller and using DRAC 5 to remotely access an inoperable system.

• The

Integrated Dell Remote Access Controller User's Guide

and using an integrated Dell Remote Access Controller to remotely manage and monitor the system and its
shared resources through a network.

• The

Dell Update Packages User's Guide

Packages for Windows and Linux as part of the system update strategy.

• The

Dell OpenManage Server Update Utility User's Guide

Server Update Utility.

• The

Dell Systems Management Tools and Documentation

the media.

provides information about installing, configuring, and using Dell

provides information about the various Dell systems, the operating

has information about installing, configuring, and using the IT

provides complete information about installing and

provides information about obtaining and using the Dell Update

provides information on using the Lifecycle

provides information on using the Systems Build and

describes the installation and use of Server

documents the SNMP management

documents the Common Information Model

lists the messages that are displayed

documents the complete command

provides complete information about configuring

provides information on using the Dell OpenManage

DVD contains readme files for applications found on

NOTE: If the product does not perform as expected or you do not understand a procedure described in this guide,
see Getting Help in the system’s Hardware Owner’s Manual .

Getting Technical Assistance

NOTE: If you do not have an active Internet connection, you can find contact information on the purchase invoice,
packing slip, bill, or Dell product catalog.

Dell provides several online and telephone-based support and service options. Availability varies by country and
product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer
service issues, visit support.dell.com and select the support category.

If you are not a U.S. customer, select your country code at the bottom of the support.dell.com page, or select All to see
more choices.

12

2

Preinstallation Setup

Ensure that you perform the following before installing Server Administrator:

• Read the installation instructions for the operating system.

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

• Read the applicable Dell OpenManage readme files and the
support.dell.com/manuals.

• Close all applications running on the system before installing the Server Administrator applications.
On Linux, ensure that all operating system RPM Package Manager (RPM) packages required by the Server

Administrator RPMs are installed. If the 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, manual
installation of RPMs is not required.

Prerequisite Checker

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 the system’s hardware and software that may affect
the installation and operation of software features

NOTE: To use supporting agents for the Simple Network Management Protocol (SNMP), 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 the system.

Dell Systems Software Support Matrix

located at

Run the prerequisite checker silently by executing runprereqchecks.exe /s from the SYSMGMT\srvadmin
\windows\PreReqChecker directory on the
prerequisite checker, a HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of
the prerequisite check. The Temp 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 HKEY_LOCAL_MACHINE\Software\Dell Computer Corporation\OpenManage
\PreReqChecks\MN\ key for a managed system:

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. The following table details the return codes.

Table 2. Return Codes While Running the Prerequisite Checker Silently

Return Code Description

0 No condition, or conditions, is associated with the

1 An informational condition, or conditions, is associated

Dell Systems Management Tools and Documentation

software.

with the software. It does not prevent a software product
from being installed.

DVD. After running the

13

Return Code Description

2 A warning condition, or conditions, is associated with the

software. It is recommended that you resolve the
conditions causing the warning before proceeding with
the installation of the software. To continue, select and
install the software using the custom installation.

3 An error condition, or conditions, is associated with the

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

—1 A Microsoft Windows Script Host (WSH) error. The

prerequisite checker does not run.

—2 The operating system is not supported. The prerequisite

checker does not run.

—3 The user does not have Administrator privileges. The

prerequisite checker does not run.

—4 Not an implemented return code.

—5 The prerequisite checker does not run. The user failed to

change the working directory to %TEMP%.

—6 The destination directory does not exist. The prerequisite

checker does not run.

—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 prerequisite checker does not run.

—10 An error has occurred with the scripting environment. The

prerequisite 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 the storage controllers or drivers has outdated firmware or driver. See
firmwaredriverversions_<lang>.html (where <
the %TEMP% folder. To find %TEMP%, run echo %TEMP%.

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

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

14

lang

> stands for language) or firmwaredriverversions.txt found in

• 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\CurrentVersion\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. The following table 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 the table are case-sensitive.

Table 3. Software Feature IDs for Managed Systems Software

Feature ID Description

ALL All features

BRCM Broadcom Network Interface Card (NIC) Agent

INTEL Intel NIC Agent

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 (iDRAC6 for yx1x and iDRAC7 for yx2x systems) Integrated Dell Remote Access Controller

SA Server Administrator

RmtMgmt Remote Enablement

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
located at support.dell.com/manuals.

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

Dell Systems Software Support Matrix

15

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

• Windows Small Business Server 2011 (64-bit)

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

NOTE: When the MUI Pack is set to non-Unicode languages like Simplified Chinese, set the system locale to
Simplified Chinese. This enables display of the prerequisite checker messages. 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

Install Dell OpenManage Server Administrator 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 2 GB RAM.

• Minimum 512 MB free hard drive space.

• Administrator rights.

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

• One of the Supported Systems Management Protocol Standards.

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

768.

• The Server Administrator Remote Access Controller service requires remote access controller (RAC) installed
on the managed system. See the relevant
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
installed on the managed system. See the

Guide

for complete software and hardware requirements.

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

Dell Remote Access Controller User’s Guide

for complete software

Dell OpenManage Server Administrator Storage Management User’s

16

NOTE: Dell OpenManage software detects the MSI version on the 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, reboot the
system to install other software applications such as Microsoft SQL Server.

Related Links:

Supported Systems Management Protocol Standards

Supported Systems Management Protocol Standards

Install a supported systems management protocol on the managed system before installing the 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 )

• Simple Network Management Protocol (SNMP)

Install the SNMP package provided with the operating system. If SNMP is installed post OMSA installation, restart
OMSA services.

NOTE: For information about installing a supported systems management protocol standard on the managed
system, see the operating system documentation.

The following table shows the availability of the systems management standards for each supported operating system.

Table 4. 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.

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

Supported SUSE Linux Enterprise
Server operating systems.

Install the SNMP package provided
with the operating system.

Documentation

CMPI-Devel

Available. Install the CIM packages
provided on the

DVD - SFCB/SFCC/

.

Dell Systems
Management Tools and
Documentation

CMPI-Devel

DVD - SFCB/SFCC/

.

NOTE: It is recommended to nstall the SFCB, SFCC, OpenWSMAN, and CMPI-Devel packages from the operating
system media, if available.

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.

Enabling Windows Installer Logging Service

Windows includes a registry-activated logging service to help diagnose Windows Installer issues.

17

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\Windows\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, the log files are generated in the %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.

Microsoft Active Directory

If you use Active Directory service software, you can configure it to control access to the 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,
add and control users and privileges from a central database.

Related Links:

Using Microsoft Active Directory

Configuring SNMP Agents

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

18

Configure the SNMP agent to change the community name, enable set operations, and send traps to a management
station. To configure the SNMP agent for proper interaction with management applications such as IT Assistant,
perform the procedures described in the
manuals.

Related Links:

• Installation Requirements

• Supported Systems Management Protocol Standards

Dell OpenManage Server Administrator User’s Guide

at support.dell.com/

Secure Port Server and Security Setup

This section contains the following topics:

• Setting User and Server Preferences

• x 509 Certificate Management

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 Server tab.

Setting User Preferences

To set up user preferences:

NOTE: Log in with administrator privileges to set or reset user or server preferences.

1. Click Preferences on the global navigation bar.

2. Click General Settings.

3. To add a preselected e-mail recipient, type the e-mail address of the designated service contact in the Mail To:
field, and click Apply Changes.

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.

4. To change the home page appearance, select an alternative value in the skin or scheme fields and click Apply
Changes.

Setting Secure Port Server Preferences

To set up secure port server preferences:

NOTE: Log in with administrator privileges to set or reset user or server preferences.

1. Click Preferences on the global navigation bar.

2. Click General Settings, and the Web Server tab.

3. Set options as necessary in the Server Preferences window:

Session Timeout

Sets the time limit for a session to remain active. Select Enable to set a time-out if there is no
user interaction for a specified time in minutes. After a session time-out, the user must log in
again to continue. Select Disable to disable the Server Administrator session time-out feature.

HTTPS Port Specifies the secure port for Server Administrator. The default secure port for Server

Administrator is 1311.

19

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.

IP Address to
Bind to

Mail to Allows to set the default mail address for e-mail(s) from OMSA GUI.

SMTP Server
name and DNS
Suffix for SMTP
Server

Command Log
Size

Support Link Specifies the web address for the business entity that provides support for the managed

Custom Delimiter Specifies the character used to separate the data fields in the files created using the Export

Specifies the IP address(es) for the managed system that Server Administrator binds to when
starting a session. Select All to bind to all IP addresses applicable for the system. Select
Specific 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.

Specifies the 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 the organization in the appropriate fields.

NOTE: For security reasons, the organization may not allow e-mails to be sent through the
SMTP server to outside accounts.

Specifies the largest file size in MB for the command log file.

system.

button. The ; character is the default delimiter. Other options are !, @, #, $, %, ^, *, ~, ?, :,|, and ,.

4. Click Apply Changes.

X.509 Certificate Management

Web certificates are necessary to ensure that the identity and information exchanged with a remote system is not
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: Log 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 the system while using server administrator, ensure the following:

Unique host name

Change 'localhost' to unique For systems with host name set to localhost change the host name to a unique host

All systems that have Server Administrator installed should have unique host names.

name.

20

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

To install the Remote Enablement feature, configure the following on the 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, Windows Server 2008 R2 SP1 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 the 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:

1. Request a valid CA signed certificate.

2. Create a HTTP listener with the CA signed certificate.

Requesting a Valid CA Signed Certificate

To request a valid CA signed certificate:

1. Click Start → Run.

2. Type mmc and click OK.

3. Click File → Add/Remove Snap-in.

4. Select Certificates and click Add.

5. In the Certificates snap-in dialog box, select Computer account, click Next.

6. Select Local Computer and click Finish.

7. Click Close and click OK.

8. On the Console window, expand Certificates (Local Computer) in the left navigation pane.

21

9. Right-click Personal, select All tasks → Request New Certificate .

10. Click Next.

11. Select the appropriate certificate type, Mostly (Computer), and click Enroll.

12. Click Finish.

Creating the HTTPS Listener With the Valid CA Signed Certificate

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 :

1. Create a certificate.

2. Add the certificate and take a thumbprint.

3. Create the WinRM HTTPS listener.

4. Configure the Envelope size for WinRM.

Creating a Certificate

1. Download the IIS Resource Kit from microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628­ade629c89499&displaylang.

2. Run iis60rkt.exe.

3. Click Next.

4. Select I Agree in the End-User License Agreement screen and click Next.

5. Click Next.

6. In the Select Type screen, select Custom and click Next.

7. Click Next.

8. In the Select Features screen, select SelfSSL 1.0 and click Next.

9. Click Next.

10. Click Finish.

The SelfSSL is installed.

11. Click Start → Programs → IIS Resource → SelfSSL → SelfSSL.

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

Adding a Certificate and Taking a Thumbprint

To add a certificate and take a thumbprint:

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

CertificateThumbprint is 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=""}

1. Click Start → Run.

2. Type mmc and click OK.

3. Click File → Add/Remove Snap-in.

4. Click Add.

5. Click Certificates and click Add.

6. In the Certificates snap-in dialog box, select Computer account option and click Next.

7. Select Local Computer and click Finish.

22

8. Click Close.

9. Click OK.

10. On the Console window, expand Certificates (Local Computer) in the left navigation pane.

11. Expand Personal.

12. Select Certificates.

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

The Certificate screen is displayed.

14. Click Details tab.

15. Select Thumbprint.

16. Copy the thumbprint to the clipboard.

You can use this parameter while creating the HTTPS listener.

17. 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="6e132c546767bf16a8acf4fe0e713d5b
2da43013"}

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, explicitly add users 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.

WinRM

To configure user authorization for WinRM servers:

1. Click Start → Run.

2. Type winrm configsddl and click OK.

If you are using WinRM 2.0, type winrm configsddl default.

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

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

WMI

To configure user authorization for WMI servers:

1. Click Start → Run.

2. Type wmimgmt.msc and click OK.

The Windows Management Infrastructure (WMI) screen is displayed.

3. Right-click the WMI Control (Local) node in the left pane and click Properties.

23

The WMI Control (Local) Properties screen is displayed.

4. Click Security and expand the Root node in the namespace tree.

5. Navigate to Root → DCIM → sysman.

6. Click Security.

The Security screen is displayed.

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

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

9. Click OK.

10. Close the Windows Management Infrastructure (WMI) screen.

Configuring the Windows Firewall for WinRM

To configure the Windows Firewall for WinRM:

1. Open Control Panel.

2. Click Windows Firewall.

3. Click Exceptions tab.

4. Select Windows Remote Management check box. If you do not see the check box, click Add Program to add
Windows Remote Management.

Configuring the Envelope Size for WinRM

To configure the envelope size for WinRM:

NOTE: 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"}

1. Open a command prompt.

2. Type winrm g winrm/config.

3. Check the value of the MaxEnvelopeSizekb attribute. If the value is less than 4608, type the following command:

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

4. Set the value of MaxTimeoutms to 3 minutes:

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

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
\RPMS\supportRPMS\opensource-components\<OS>\<arch>.

NOTE: On supported SLES 11 and above and Red Hat Enterprise Linux 6 and preceding operating systems, it is
recommended that you install the RPMs from the operating system media, if available.

Dell Systems Management Tools and Documentation

DVD at srvadmin\linux

24

Installing Dependent RPMs

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

1. Make sure that Pegasus RPMs are uninstalled.

2. Check if the openwsmand and sfcbd binaries are already installed using make-install. Check by running the

commands: openwsman or sfcbd or you can check the existence of the binaries in the /usr/local/sbin directory.

3. If the binaries are installed, uninstall these binaries.

4. Check for the required dependencies for the openwsman and sfcbd RPMs listed in the following table.

Table 5. Required Dependencies

Packages Red Hat Enterprise Server SUSE Linux Enterprise Server

Openwsman

SBLIM SFCC CURL LibCURL

SBLIM SFCB

5.

Install the dependent RPMs. You can install the RPMs:

– with a single command rpm -ivh rpm1 rpm2 rpm3 rpm4 … rpmN

or

– individually

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

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

OpenSSL
LibXML
Pkgconfig
CURL
Chkconfig
Initscript
SBLIM-SFCC

zlib
CURL
PAM
OpenSSL
Chkconfig
Initscript

LibOpenSSL
LibXML
Pkg-config
libCURL
aaa_base
aaa_base
SBLIM-SFCC

zlib
LibCURL
PAM
LibOpenSSL
aaa_base
aaa_base

NOTE: Install the libwsman and openwsman client RPMs simultaneously as they have cyclic dependency.

rpm -ivh libwsman1-x.x.x.rpm openwsman-client-x.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, make sure that Dell OpenManage is installed.

25

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 <
autoconf_cim_component.sh. This is optional and by default the openwsman is configured to run on port 443.

Related Links:

Installing Managed System Software on Supported Linux and VMware ESX

port

> option with

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 the 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:

1. Mention a valid CRL file in /etc/openwsman/openwsman_client.conf.

2. 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 the operating system vendor to provide the required CURL
library with CRL support.

Running sfcb and openwsman

Run sfcb and openwsman:

• /etc/init.d/sfcb start

• /etc/init.d/openwsmand start

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

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 with .lib lib64

26

1. Back up these files:

– /etc/pam.d/openwsman

– /etc/pam.d/sfcb

– /etc/pam.d/system-auth

2. Replace the content of /etc/pam.d/openwsman and /etc/pam.d/sfcb with

auth required pam_stack.so service=system-auth
auth required /lib/security/pam_nologin.so
account required pam_stack.so service=system-auth

3. Replace the content of /etc/pam.d/system-auth with

%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
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

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.

1. Back up the following files:

– /etc/pam.d/openwsman

– /etc/pam.d/sfcb

– /etc/pam.d/system-auth

– /etc/pam.d/common-account

2. Replace the content of /etc/pam.d/openwsman/ and /etc/pam.d/sfcb with

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

3. Replace the content of /etc/pam.d/common-auth with

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

27

4. Replace the content of /etc/pam.d/common-account with

account sufficient pam_unix2.so
account sufficient pam_winbind.so

Workaround for the Libssl Issue

If the required library needed by openwsman is present on the 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 the system and then create a soft link with libssl.so.

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

28

Installing Managed System Software on Microsoft Windows Operating Systems

3

On Microsoft Windows, an autorun utility is displayed when you insert the

Documentation

system.

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

Matrix

for a list of operating systems currently supported.

NOTE: Use the
silent installation of the managed system software. Install and uninstall the features from the command line.

DVD. This utility allows you to choose the systems management software you want to install on the

Dell Systems Management Tools and Documentation

Dell Systems Management Tools and Documentation

Dell Systems Management Tools and

DVD. See the

DVD to perform an unattended and scripted

Dell Systems Software Support

Deployment Scenarios for Server Administrator

You can install Dell OpenManage Server Administrator in the following ways:

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

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

The following table lists the deployment scenarios for installing and using Server Administrator and helps you make the
right choice while selecting the various installation options:

Table 6. Deployment Scenarios

You want to Select

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

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

Manage and monitor the 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.

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

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.

29

You want to Select

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

NOTE: Install the Simple Network Management Protocol (SNMP) agent on the managed system using the
operating system medium before installing the managed system software.

Remote Access Controller.

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 \SYSMGMT\srvadmin\windows on the

Documentation

• Using the unattended installation method through the Windows Installer Engine msiexec.exe.

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, manually restart these services.

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.

The setup program invokes the prerequisite checker, which uses the 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.

Related Links:

• Deployment Scenarios for Server Administrator

• Optional Command Line Settings

DVD.

Dell Systems Management Tools and

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

• Remote Access Controller

• Intel SNMP Agent

• Broadcom SNMP Agent

During a Typical 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 Typical 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.

30