The Dell
OpenManage Systems Management CD provides a setup program to install, upgrade, and uninstall Server Administrator and other managed
system and management station
software components on your managed system. Additionally, you can install Server
Administrator on multiple
systems through an unattended installation across a network.
Using the setup program on the Systems Management CD, you can install and upgrade Server Administrator on
systems running all supported operating systems. On systems running supported Microsoft® Windows®
and Red Hat Linux operating systems, you can uninstall Server Administrator with the Systems Management CD or through
the operating system. On systems running supported Novell® NetWare® operating
systems, you can only uninstall Server Administrator through the operating
system.
You can use the Systems Management CD to perform an unattended
installation and uninstallation
of Server Administrator on systems running supported
Microsoft Windows and Red Hat Linux
operating systems. Additionally, you can install and uninstall Server
Administrator from the command line on systems running supported Red Hat Linux
operating systems.
NOTE: You should
always use the Systems Management CD to install, upgrade, and
uninstall Server Administrator.
NOTE: Upgrading to
the most recent version of Server Administrator does not require that you
uninstall any previously installed software components. The setup program
on the Systems Management CD automatically uninstalls and then upgrades the managed
system software components that are appropriate for your particular
system's hardware
configuration.
Read the installation requirements to
ensure that your system meets or
exceeds the minimum requirements.
Read the Server Administrator Compatibility Guide. This document
contains compatibility information about Server Administrator installation
and operation on various hardware platforms (or systems) running supported
Microsoft® Windows®, Novell® NetWare®, and Red Hat Linux operating
systems.
Read the Server Administrator readme file on the Systems Management CD. The file contains
the latest information about
software, firmware, and driver versions, in addition to information about
known issues.
Read the installation instructions for your operating system.
The following sections describe the Server Administrator general requirements.
Operating systemspecific installation prerequisites are listed as part of the
installation procedures.
Server Administrator supports each of the following operating systems:
Microsoft Windows NT® Server 4.0 (Service Pack 6a or later)
Microsoft Windows 2000 Server Family (includes Windows 2000 Server,
Windows 2000 Advanced Server, and Windows Small Business Server
[SBS] 2000) (Service Pack 3 recommended)
Red Hat Linux Advanced Server, version 2.1
Red Hat Linux, version 7.3 (with the
2.4.18-4smp kernel or later)
Red Hat Linux, version 8.0
NOTE: Support for updated kernels released by
Red Hat and
for later versions of Red Hat Linux may require the use of Dynamic Kernel
Support (see "Dynamic Kernel Support" for an explanation of this feature).
Novell NetWare, version 5.1 (Service Pack 4 or later)
Novell NetWare, version 6.0 (Service Pack 1 or later)
NOTE: See the Server Administrator readme
file on the Systems Management CD for the latest detailed list of
the Server Administrator Services that are supported on
each supported operating system.
Server Administrator must be installed on each system
to be managed. You can then manage each system running Server Administrator locally or
remotely through a supported Web browser.
A mouse, keyboard, and monitor to manage a system locally.
The monitor requires a minimum screen resolution of 800 x 600. The recommended
screen resolution setting is 1024 x 768.
The Server Administrator Remote Connection Service requires that
a Remote Access Controller (RAC) is installed on the system to be managed. See
"Remote Access Service" and the Dell
Remote Access Controller Installation and Setup Guide for complete
software and hardware requirements.
NOTE: The RAC
software is installed as part
of the Express Setup and Custom Setup installation options when
installing managed system software from the Systems Management
CD, provided that the managed system meets all of the RAC installation prerequisites. See
"Remote Access Service" and the Dell
Remote Access Controller Installation and Setup Guide for complete
software and hardware
requirements.
The Server Administrator Storage Management Service requires that Dell
OpenManage Array
Manager version 3.1.1 or later is installed on the system to be managed as part
of the Express Setup or Custom Setup managed system software
installation from the Systems Management
CD. See the Array Manager User's Guide for complete
software and hardware requirements.
NOTE: Array Manager is installed as part
of the Express Setup and Custom Setup installation options when
installing managed system software from the Systems Management
CD, provided that the managed system meets all of the Array
Manager installation prerequisites. The Storage Management
Service requires that you install Array Manager as part of the Server
Administrator installation from the Systems Management
CD. See the Array Manager User's Guide for complete
software and hardware
requirements.
Remote Management System Requirements
Microsoft Internet Explorer 5.x or later, Netscape Navigator
6.01 or later, or Mozilla 1.0 or later to manage a system remotely from the Server
Administrator home page.
NOTE: The Remote
Access Service supports Netscape Navigator 6.2.x or later.
TCP/IP connection on the managed system and the remote system to facilitate remote system management.
Minimum screen resolution of 800 x 600. The recommended
screen resolution setting is 1024 x 768.
A supported systems management protocol standard must be installed on the
managed system before installing Server Administrator. On supported Microsoft Windows operating systems, Server Administrator
supports these two systems management standards: Common Information Model (CIM)
and Simple Network Management Protocol (SNMP). On supported Red Hat Linux and
Novell NetWare operating systems, Server Administrator supports the SNMP systems
management standard.
NOTE: For information about installing a
supported system management protocol standard on your managed system, see your operating system documentation.
Table 1 shows the availability of the systems management
standards for each supported operating system:
Table 1. Availability of Systems Management Protocol by
Operating Systems
Operating System
SNMP
CIM
Microsoft Windows NT Server and Microsoft Windows 2000
Server Family
Available from the operating system installation media.
Available from the operating system installation media.
Red Hat
Linux Advanced Server 2.1, Red Hat Linux 7.3, and Red Hat Linux 8.0
You must install the ucd-snmp package provided with the operating
system.
Unavailable.
Novell NetWare
Always installed.
Unavailable.
SNMP Access Control Configuration
The management information base (MIB) branch implemented by the Instrumentation Service is identified by
the OID 1.3.6.1.4.1.674.10892.1. Management applications must have
access to this branch of the MIB tree to manage systems running the
Instrumentation Service.
The default SNMP configuration provides read-only access only to the MIB-II "system" branch
(identified by the OID 1.3.6.1.2.1.1) of the MIB tree for the "public"
community. This configuration does not allow management applications to
retrieve or change Instrumentation Service information. If the
Instrumentation Service detects this configuration during installation, it
attempts to modify the SNMP configuration to provide read-only access to the
entire MIB tree for the "public" community.
The following installation procedures provide step-by-step instructions for installing, upgrading, and uninstalling
Server Administrator for each
supported operating system.
This section explains how to install, upgrade, and uninstall Server
Administrator on a
system that is running a supported Windows operating system. This
section includes the following topics:
This section explains how to install and upgrade the Server Administrator. There
are two installation options:
Use the setup program on the Systems Management CD to install or upgrade Server Administrator and other managed
system software.
Use the unattended installation program to install Server Administrator
and other managed system software on multiple systems.
Prerequisites for Installing or Upgrading Server Administrator
You must have administrator privileges.
If you want to use supporting agents for the SNMP or for the CIM, you must install the operating
system support for the SNMP or CIM standard before you install Server Administrator. For
more information about installing SNMP or CIM, see the installation instructions
for the operating system you are running on your system.
NOTE: During a Custom
or Express installation, individual Server Administrator services
will not be installed on managed systems that do not meet the
specific hardware and software installation requirements
for that service. For example, the Server Administrator Remote Access
Service software module will not be installed during an Express
installation unless the managed system has an installed remote access
controller.
Express and Custom Installation
The Systems Management CD features an Express Setup option and a Custom
Setup option for installing Server
Administrator and other managed system software.
When you insert the Systems Management CD in your systems CD drive, the
setup program uses your systems PCI bus
to search for installed hardware such as controller cards.
When a user selects the Express Setup option, the setup program
installs or upgrades all of the managed system software components that are appropriate for your particular
system's hardware
configuration. For more information on how to perform
an express setup, see the Software Quick Installation Guide. You can access the Software Quick Installation Guide
from the task bar within the setup program.
When a user selects the Custom Setup option, the user can deselect one or more
software components that the setup program has identified as appropriate for the installed
options on the system. During an express setup, you cannot add to the list of components to install because all the components that are appropriate for the hardware
configuration are preselected.
The sections that follow show how to install and upgrade Server Administrator and
other managed system software using the Custom Setup option.
Custom Installation
Insert the Systems Management CD into your systems CD drive.
If the CD does not automatically start the setup program, go to your systems desktop,
double-click
My Computer, double-click the CD drive icon, and double-click the setup.exe
file.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select System Type screen appears.
Click Install Managed System.
The Select Setup Type screen appears.
Click Custom Setup.
The Select Destination screen appears.
To accept the default directory path to install managed system software, click Next.
Otherwise, click Browse and navigate to the directory where you want to install your managed
system software, and then click
Next.
The Managed System Software screen appears.
Each managed system software application listed has a check box to the left of its
name. A check in the check box indicates that the software is selected for installation. As a default, all available
software components are selected.
A button appears to the right of each component
name.
The Settings button indicates that you can install and
configure the component.
The More Info buttons are color coded:
Black indicates that the software is available for your system.
Yellow indicates that the software is available for your system, but you must perform an additional action before you can install it; for example,
starting the driver for the component.
Red indicates that the software is unavailable for your system. You do
not have required hardware or software components installed.
Buttons that appear in gray do not provide either
information or configuration options.
Click Next to install the selected software components.
The Installation Summary screen appears, listing all the managed system
software services you selected for installation.
Click Next to continue.
A Confirm Install dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages display, stating which
software components are being installed.
When the selected components are installed, the setup program asks if you want to reboot your system.
You must reboot your system to make the installed managed system software services available for use.
Select your reboot option:
Yes, reboot my system now.
No, I will reboot my system later.
Click Finish.
If prompted, click OK to confirm the reboot or Cancel to reboot
later.
Express and Custom Upgrade
The Systems Management CD features an Express
Upgrade option and a Custom Upgrade option for upgrading Server
Administrator and other managed system software.
When you insert the Systems Management CD in your systems CD drive, the
setup program uses your systems PCI bus
to search for installed hardware such as controller cards.
When a user selects the Express Upgrade option, the setup program
installs or upgrades all of the managed system software components that are appropriate for your particular
system's hardware
configuration. For more information on
how to perform an express upgrade, see the Software Quick Installation Guide.
You can access the Software Quick Installation Guide
from the task bar within the setup program.
When a user selects the Custom Upgrade option, the user can deselect one or
more components that the setup program has identified as appropriate for upgrade on
your system. During an express upgrade, you cannot add to the list of managed system
software components to install because all components appropriate
for your system are preselected.
The following procedures show how to upgrade Server Administrator and other
managed system software using the Custom Upgrade option.
Custom Upgrade
Insert the Systems Management CD into your systems CD drive.
If the CD does not automatically start the setup program, go to your systems desktop, double-click
My Computer, double-click the CD drive icon, and double-click the setup.exe
file.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select System Type screen appears.
Click Upgrade Managed System.
The Select Setup Type screen appears.
Click Custom Upgrade.
The Managed System Software screen appears.
Each managed system software component listed has a check box to the left of its
name. A check in the check box indicates that the software component is selected for upgrade. As a default, all
outdated software components
are selected.
A button to the right of each component name provides
information about the component.
The Upgrade Info button indicates that you can
upgrade and configure the component.
The More Info buttons are color coded:
Yellow indicates that the software is available for your system, but
either the current version is already installed or
you must perform an additional action before you can install it; for example,
starting the driver for the component.
Red indicates that the component is not
installed on your system.
Buttons that appear in gray do not provide either
information or configuration options.
Click Next to install the selected components.
The Installation Summary screen appears, listing all of the managed
system software services you selected for
upgrade.
Click Next to continue.
A Confirm Install dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages display, stating which components are being installed.
When the selected components are installed, the setup program asks if you want to reboot your system.
You must reboot your system to make the installed managed system software services available for use.
Select your reboot option:
Yes, reboot my system now.
No, I will reboot my system later.
Click Finish.
If prompted, click OK to confirm the reboot or Cancel to reboot
later.
The Systems Management CD features an Express Setup option and a
Custom Setup option for the unattended installation procedure.
Unattended installation allows you to install Server Administrator on multiple
systems simultaneously. You can perform an unattended installation by creating
an unattended installation package that contains all of the necessary managed
system software files. The unattended installation option also provides
several features that allow users 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.
Creating and Distributing the Express Unattended Installation Package
The Express Setup unattended installation option uses the Systems
Management CD as the unattended installation package. The setup.exe /ilicense=yes program accesses the Systems Management CD to
accept the software license agreement and install all required Server
Administrator components on selected remote systems. The setup.exe /ilicense=yes program installs Server Administrator components on each remote system based on
the system's hardware configuration.
NOTICE: The license=yes
setting must be added to the setup.exe /i command
for an Express Setup unattended installation to run. Adding the license=yes
setting confirms that you accept the software license agreement for using the
unattended installation program. See "Optional Command Line Settings"
for more information.
You can make the Systems Management CD image available to the remote
system by either distributing the entire contents of the CD or by mapping a
drive from the target system to the location of the CD image.
Mapping a Drive to Act as the Express Unattended Installation Package
Share an image of the Systems Management CD with each remote
system on which you want to install Server Administrator.
You can accomplish this task by directly sharing the CD or by copying the entire CD to a drive and
sharing the copy.
Create a script that maps a drive from the remote system(s) to the shared
drive described in step 1. This script should execute setup.exe /i
license=yes
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 setup.exe /ilicense=yes program executes to install Server Administrator on each remote system.
Reboot each remote system to enable Server Administrator.
Distributing the Entire CD as the Express Unattended Installation Package
Distribute the entire image of the Systems Management CD to your
target systems.
Configure your ISV distribution software to execute the setup.exe /i
license=yes program from the Systems Management CD image.
The setup.exe /i
license=yes 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
The Custom Setup unattended installation option creates an unattended installation
package in a directory on your system's hard drive. To create a custom unattended installation package, perform the following
steps.
NOTE:
The setup.exe program that is used for the Custom Setup unattended
installation with the /p option is located at the root of the Systems
Management CD.
Run the setup.exe /p program from the Systems Management CD.
A software license agreement appears.
Click Accept if you agree.
The Select Destination screen appears.
Click Next, to accept the default directory path for the creation of the unattended installation
package. Otherwise, click Browse, navigate to the directory where you want to
create the unattended installation package, close the navigation window, and
then click Next.
The Managed System Software screen appears.
If present, buttons to the right of
a component name provide
information or configuration options for the component.
The Settings
button, for example, indicates that you can configure the
component.
Buttons that appear in gray do not provide either
information or configuration options.
Click Next when you have selected each managed system software component that you want
to include in the unattended installation package.
The Dell OpenManage Components window appears.
While the package is being created, the following message is displayed:
Setup is creating an unattended installation package for
managed system services. Please wait...
When the script is complete, the Setup
Complete window appears. The following message is displayed:
The unattended installation package
was created successfully
Click Finish.
The directory that you selected in step 3 now contains the custom unattended
installation package.
The custom unattended installation package is located in the directory you created in step
4 of the preceding procedure (for example, c:\temp\dell\openmanage).
This directory contains all of the managed system software components you selected to
distribute, along with all the necessary unattended installation program files.
NOTE:
The setup.exe program that is used for the Custom Setup unattended
installation with the /i option is located in the root directory of the Systems
Management CD.
Configure your ISV software distribution software to
execute the setup.exe /i program after the custom unattended installation package
has been
distributed.
Use your ISV software distribution software to distribute the custom unattended installation package
to the remote systems.
The setup.exe /i program executes to install Server Administrator on each remote system.
Reboot each remote system to enable Server Administrator.
Table 2 shows the optional settings available for unattended installation.
Type the optional settings on the command line after
setup.exe /i with a space in between each setting.
NOTE:
Running setup.exe /? or setup.exe /help displays a list of all
available command line settings.
Installs the Array Manager Console as
part of the Array Manager (Storage Management Service) installation.
If the amconsole option is set to yes or the
amconsole option is
not used, the system automatically installs the Array Manager Console. If
the amconsole option is set to no, then Array Manager Console is not installed.
cim=yes/no
Installs the Common Information Model (CIM)
as part of the Server Administrator installation.
If the cim option is set to yes or the cim option is not used,
the system automatically installs CIM. If the cim option is set to no,
then CIM is not installed.
icon=yes/no
Places or prevents placement of the
Dell OpenManage icon on the desktop and in the Start menu after installation
is complete.
If the icon option is set to yes or if the
icon option is not
used, the icon is placed on the desktop and in the Start menu. If the
icon
option is set to no, then the icon is not placed anywhere.
license=yes
Accepts the software license agreement for using the
unattended installation program. The license
agreement (license.txt) is located in the /app/doc directory on the Systems Management CD.
NOTICE: The license=yes
setting must be added to the command line
for an express unattended installation to run.
logfile=<logfile-location>
Specifies a
nondefault filename for the short format log
file. For more information, see "Log Files." The full path including
the name of the file must be specified in this option. If the path or the
filename contains any spaces, then the location must be enclosed in double
quotes. The location cannot contain any of the reserved words described in this
section such as icon, web, reboot, and
so on.
password=<password>
Sets the password for SNMP Set operations. You will need this
password to log in to Server Administrator after installation. Spaces are not
allowed in the password.
If a password is not entered or the password option is not used, the password is
set to "calvin" by default.
reboot=yes/no
Automatically reboots the system after installation is
complete.
If the reboot option is set to no or the
reboot option is not
used, the system will not reboot.
showstatus=yes/no
Displays the installation status while the System Management
Installation program is installing Dell OpenManage applications.
If the showstatus option is set to no or the
showstatus option is
not used, the status is not displayed during installation. If the
showstatus option is set to yes, then the installation status is displayed in a small console on the desktop.
sil=<silfile-location>
Specifies a customization file. For more information about
the customization file, see "Customization Files." The full path including
the name of the file must be specified in this option. If the path or the
filename contains any spaces, then the location must be enclosed in double
quotes. The location cannot contain any of the reserved words described in this
section such as icon, web, reboot, and
so on.
snmpsets=yes/no
Enables SNMP Set operations on the system running Server Administrator.
If the snmpsets option is set to yes or the
snmpsets option is not
used, the system will allow SNMP Set operations.
web=yes/no
Automatically starts the Server
Administrator Web server after every system reboot.
If the web option is set to yes or the web
option is not used,
the system will automatically start the Server Administrator Web
server after every reboot. If the web option is set to no, then the Server Administrator
Web server will not automatically start on
reboot.
For example, running setup.exe /i password=ABC reboot=yes icon=no installs Server Administrator components on each remote system based on
the system's hardware configuration, sets the password for SNMP Set operations to "ABC,"
reboots each system after installation is complete, and specifies that the Dell
OpenManage icon
is not placed on the desktop and the Start
menu.
Customization files provide a way to customize the exact software components
to install. With the customization file, users can selectively install software
components for different systems using the same unattended installation
package. For example, you can choose to install Server Administrator, but not
Remote Access Service on a specific group of servers, and choose to install Server
Administrator, but not Storage Management Service, on another group of servers. The customization file
is formatted as a simple text file with a .sil filename suffix, in which each line contains one software
component relationship. For example:
component ID=yes/no
A designation of yes indicates that the component is installed. A designation of
no indicates that the component is not installed. Table 3 shows the
component IDs for each software component. The component ID is a 2- to
5-character designation.
Table 3. Software Component IDs
Component ID
Software Component
am
Storage Management Service
brcm
Broadcom NIC agent
drac2
Remote Assistant Card (DRAC II)
ibm
IBM® NIC agent
intc
Intel® NIC agent
old
Diagnostic Service
rac
Remote Access Service
sa
Server Administrator
sym
Symbios agent
Figure 1 shows an example of a customization file, C:\temp\unattend\install.sil,
in which all components except Remote Access Service and DRAC II are designated
to be installed.
The unattended installation log files capture the installation status of each software
component and the result of each unattended installation dependency check. For
more information
about log files generated by the dependency check, see the "Dependency Check" section.
Two log files are generated in a temp
folder during an unattended installation, ominstal.log and omstatus.log. The temp
folder is typically located at c:\temp. Each log provides the installation status of each component,
the host system name, and the start and end time of the
installation. On a large-scale, unattended installation deployment of hundreds or
thousands of servers, users can save the unattended installation log file for
each server and easily isolate an installation problem on one or more servers
with the host information in the log file.
The omstatus.log provides installation
information in a shortened format that is designed to be easily read by scripts.
You can use this information to write automatic script files to query the
installation status and take remedy actions as needed. See Figure 2.
There is one line per software component. A value of "0" indicates that the installation of the
component succeeded, a value of "-1" indicates that installation of the component failed, and
a value of "1" indicates that the component did not install because a dependency was not met.
See "Dependency Check" for information about identifying installation
dependencies. The software component
ID is the same 2- to
5- character designation described in the "Customization Files"
section.
HOST = Server_xyz
START = Mon Sep 23 10:18:20 PDT 2002
sa = 0
old = 0
rac = 1
am = 0
drac2 = 1
ibm = 1
intc = 0
brcm = 0
sym = 0
END = Mon Sep 23 10:19:55 PDT 2002
The ominstal.log provides full text installation
information about the components. See Figure 3.
Figure 3. Example of a Full Text ominstal.log File
Applications with WARNING or DEPENDENCY cannot be installed using unattended
mode.
Host Name: Server_xyz
---------START Mon Sep 23 10:18:20 PDT 2002 -----------------------------------
OK: Server Administrator is all set to install
DEPENDENCY: Remote Access : Remote Access Controller was not detected on the
system.
OK: Storage Management is all set to install
OK: Diagnostic Service is all set to install
DEPENDENCY: Remote Assistant Card (DRAC II) : Remote Assistant Card (DRAC II)
was not detected on this system.
WARNING: Intel Agent : Warning! Current version is already installed on the
system.
DEPENDENCY: Broadcom Agent : Broadcom NIC was not detected on this system.
DEPENDENCY: IBM Agent : IBM Agent card was not detected on this system.
DEPENDENCY: Symbios Agent : LSI CI card not detected on the system.
The setup.exe /c program provides the capability to examine the
dependency status of software components without launching the actual
installation. This program generates two log files
in your system's temp folder: ominstal_chk.log and omstatus_chk.log.
The ominstal_chk.log provides full text information about the
dependency status of software components.
The omstatus_chk.log provides
dependency status information in a shortened format that is designed to be
easily read by scripts. See Figure 2 for an example of a log file.
There is one line per software component. A value of "0" indicates that the
installation is ready to proceed, a value of "1" indicates that one or
more components has a dependency warning, and a value of "2" indicates that one or more components has a dependency
error. The software component
ID is the same 2- to
5- character designation described in the "Customization Files"
section.
component ID=0/1/2
where "0" means OK to install, "1" means warning,
and "2" means dependency error.
See the "Log Files" for more information.
The format is very similar to the .sil file format and the
software component IDs are
identical.
Use the following command line settings with the dependency check feature.
Dependency Check Command Line Settings
Table 5 shows the dependency check command line settings available for unattended installation.
Type the optional settings on the command line after
setup.exe /c with a space in between each setting.
NOTE:
Running setup.exe /? or setup.exe /help displays a list of all
available command line settings.
Specifies a nondefault filename for the short format
dependency log file. The full path including the name of the file must be
specified. If the path or the filename contains any spaces, then
the location must be enclosed in double quotes.
showstatus=yes/no
Displays the status of the dependency check program.
If the
showstatus option is set to yes then the dependency check status
will be displayed in a small console on the desktop. If the
showstatus option is set to
no or the
showstatus option is
not used, the status will not be displayed during the dependency check.
sil=<silfile-location>
Runs a dependency check on the components specified in
the .sil file. For more information about the format of the .sil
file, see "Customization Files."
For example, running setup.exe /c sil=C:/temp/dep.sil
showstatus=yes runs the dependency check for all components listed in the
customization file (dep.sil), saves the dependency check log files (ominstal_chk.log
and omstatus_chk.log)in the temp folder, and displays
the dependency check status while the command is running.
Dependency Check Return Codes
The setup.exe /c program returns a status code to indicate success or failure. The
return codes are described in Table 6.
NOTE:
Components with a dependency warning or failure cannot be installed using
unattended mode.
You can uninstall Server Administrator managed system software components by using the Systems Management CD or your operating system. Additionally, you can perform an unattended
uninstallation on multiple systems simultaneously.
Uninstalling Server Administrator Managed System Software Using the Systems Management CD
Insert the Systems Management CD into your systems CD drive.
If the CD does not automatically start the setup program, go to your systems desktop, double-click
My Computer, double-click the CD drive icon, and double-click the setup.exe
file.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select System Type screen appears.
Click Uninstall.
The Uninstall Selection screen appears. Each managed system software component listed has a check box to the left of its
name. A check in the check box indicates that the software component is selected for
uninstallation. As a default, all installed managed system software components
are selected.
Click Next to uninstall the selected managed system software components.
The Uninstall Summary screen appears, listing all of the managed
system software services you selected for
uninstallation.
Click Next to continue.
The Confirm Uninstall dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages display, stating which components are being
uninstalled. When the selected components are uninstalled, the setup program asks if you want to reboot your system.
You must reboot your system to complete the uninstallation process.
Select your reboot option:
Yes, reboot my system now.
No, I will reboot my system later.
Click Finish.
If prompted, click OK to confirm the reboot or Cancel to reboot
later.
Click the Start button, point to Settings> Control
Panel.
Double-click Add/Remove Programs.
Click Server Administrator and click Change/Remove.
The Uninstall Selection screen appears.
Each managed system software component listed has a check box to the left of its
name. A check in the check box indicates that the component is selected to be
uninstalled. As a default, all installed components are selected.
Click Next to uninstall the selected components.
The Uninstall Summary screen appears, listing all the managed system
software components you selected to uninstall.
Click Next to continue.
A Confirm Uninstall dialog box appears.
Click Yes to confirm your selections.
A screen appears on which messages are displayed, stating which components are being
uninstalled.
When the selected components are uninstalled, a dialog box asks if you want to reboot your system.
You must reboot your system to complete the uninstallation process.
The Systems Management CD features an unattended uninstallation procedure.
Unattended uninstallation allows you to uninstall Server Administrator from multiple
systems simultaneously. 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.
Distributing the Unattended Uninstallation Package
The Systems Management CD is preconfigured to act as the unattended
uninstallation package.
To distribute the package to one or more systems, perform the following steps:
Configure your ISV software distribution software to
execute the setup.exe /u program after the unattended uninstallation package has been
distributed.
Use your ISV software distribution software to distribute the express unattended
uninstallation package to the remote systems.
The setup.exe /u program executes to uninstall Server Administrator on each remote system.
Reboot each remote system to complete the uninstallation process.
Unattended Uninstall Command Line Settings
Table 7 shows the unattended uninstall command line settings available for unattended
un installation.
Type the optional settings on the command line after
setup.exe /u with a space in between each setting.
Automatically reboots the system after uninstallation is
complete.
If the reboot option is set to no or the
reboot option is not
used, the system will not reboot.
showstatus=yes/no
Displays the status of the unattended uninstallation.
If the
showstatus option is set to yes then the unattended uninstallation status
will be displayed in a small console on the desktop. If the showstatus option is set to
no or the showstatus option is
not used, the status will not be displayed during the unattended uninstallation.
For example, running setup.exe /u reboot=yes
showstatus=yes runs the unattended uninstallation, displays
the unattended installation status while it is running, and reboots the system
after uninstallation.
This section explains how to install, upgrade, and uninstall Server Administrator on an
ix86
system that is running a supported Red Hat Linux operating system. Server
Administrator can be installed and upgraded from either the setup
program on the Systems Management CD or from the Red Hat Linux command
line.
Additionally, Server Administrator includes Dynamic Kernel Support, a feature
that automatically builds a device driver for a running kernel if Server
Administrator detects that none of its prebuilt device drivers support that
kernel. This section includes the following topics:
Server Administrator provides prebuilt device drivers for the precompiled
kernels listed in the Server Administrator readme file on the Systems Management CD. If the running
kernel is not one of the precompiled kernels listed in the readme
file, or if the running kernel is reconfigured and recompiled in such a way that
none of the prebuilt Server Administrator device drivers support the recompiled
kernel, Server Administrator must use its Dynamic Kernel Support feature to support
the running kernel.
For example, if you see either of the following messages during Server
Administrator installation or startup, Server Administrator attempted to
use its Dynamic Kernel Support feature, but was unable to use the feature
because certain prerequisites were not met:
Server Administrator is unable to build a device driver for the running kernel
because the needed kernel source files are not installed.
or
Building device driver for running kernel... [FAILED]
Needed
kernel source files are not installed.
NOTE:
Server Administrator logs messages to the Red Hat Linux
system log file, /var/log/messages.
Determining the Running Kernel
Log in as root.
To determine the kernel that is running on your system, type the following
string and press <Enter>:
uname -r
The system displays a message about the running kernel.
NOTE:
If the running kernel is not one of those listed in the Server Administrator
readme file, Server Administrator must use Dynamic Kernel Support to support
the running kernel.
For Server Administrator to use its Dynamic Kernel Support feature,
the following Dynamic Kernel Support prerequisites must be met before
installing or restarting Server Administrator:
The running kernel must be installed from an RPM package file released
by Red Hat.
The running kernel must have loadable module support enabled.
The kernel-headers RPM for the running kernel must be installed.
The kernel-source RPM for the running kernel must be installed.
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, Server Administrator's Dynamic Kernel
Support automatically builds a device driver when needed during Server Administrator
installation or startup. For example:
If Server Administrator is not installed when an unsupported kernel is
booted, Server Administrator builds a device driver for the kernel during
installation.
If Server Administrator is installed when an unsupported kernel is booted,
Server Administrator builds a device driver for the kernel the first time that it
starts after the kernel is loaded.
NOTE: "Unsupported kernels" are kernels that are not
supported by a prebuilt device driver. You may proceed to the installation
instructions if you are running a supported kernel.
Using Dynamic Kernel Support During Server Administrator Installation
To install Server Administrator on a system running a
kernel that is not supported by a prebuilt device driver, perform the following steps:
During installation, Server Administrator builds a device driver for the
kernel running on the system.
Using Dynamic Kernel Support After Server Administrator Installation
To enable Server Administrator to support a kernel that is not supported by a
prebuilt device driver and is loaded after Server Administrator has been
installed, perform the following steps:
Server Administrator builds a device driver for the kernel running on the
system the first time that 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 Server Administrator dynamically builds a device driver for the running kernel,
it installs the device driver into the directory /lib/modules/<kernel>/misc, where
<kernel>
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 same directory on the other system. This action
allows Server Administrator to use Dynamic Kernel Support on multiple systems without having to
install the kernel source on every system.
For example: System A is running a kernel that is not supported by one of the
Server Administrator prebuilt 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:
Server Administrator builds a device driver for the kernel running on system A during
installation.
Type uname -r to determine the name of the running kernel.
Copy the file /lib/modules/<kernel>/misc/esm.o from system A to the same directory on system B.
NOTE: You might have to create the directory /lib/modules/<kernel>/misc
on system B.
Install Server Administrator on system B.
Server Administrator detects that the device driver you copied to the file /lib/modules/<kernel>/misc/esm.o
supports the running kernel and uses that device driver.
NOTE: When Server Administrator is uninstalled from system B, the
process removes the /lib/modules/<kernel>/misc/esm.o file that you copied to system B.
This section explains how to install and upgrade Server Administrator. There
are three installation options:
Use the setup program on the Systems Management CD to install or upgrade Server Administrator
and other managed system software.
Install or upgrade Server Administrator from the Red Hat Linux command
line.
Use the unattended installation program to install Server Administrator
and other managed system software on multiple systems.
Prerequisites for Installing Server Administrator
You must be logged in as root.
The running kernel must have loadable module support enabled.
The ucd-snmp package that is provided with the operating system must be installed.
If you want to use supporting agents for the ucd-snmp agent, 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.
NOTE: During a Custom
or Express installation, individual Server Administrator services
will not be installed on managed systems that do not meet the
specific hardware and software installation requirements
for that service. For example, the Server
Administrator Remote Access Service software module will not be installed
during an Express installation unless the managed system has
an installed remote access controller.
The Systems Management CD features an Express Setup option and a Custom
Setup option for installing Server
Administrator and other managed system software, and an Express Upgrade
option and a
Custom Upgrade option for upgrading Server
Administrator and other managed system software.
When you load the Systems Management CD in your systems CD drive, the
setup program uses your systems peripheral controller interconnect (PCI) bus
to search for installed hardware such as controller cards.
When a user selects the Express Setup or Express Upgrade option, the user lets the setup program
install or upgrade all the managed system software components that are appropriate for the hardware
configuration of your particular system. For more information on how to perform
an express setup or express upgrade, see the Server Assistant QIG. You can access the QIG from the task bar within the setup program.
When a user selects the Custom Setup or Custom Upgrade option, the user can deselect one or more
components that the setup program has identified as appropriate for your system. During an
express setup or express upgrade, you cannot add to the list of components to install because all the
components that are appropriate for the hardware
configuration are preselected.
The sections that follow show how to install and upgrade Server Administrator and
other managed system software using the Custom Setup and Custom Upgrade
options.
Custom Installation
Start a system running X Windows.
Insert the Systems Management CD into the CD drive on your system.
If the CD does not mount automatically, type mount /mnt/cdrom.
After the CD mounts, the File
Manager should automatically start and display the contents of the root
directory of the CD.
Double-click the start.sh file in the File Manager window.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select Setup Type screen appears.
Click Custom Setup.
The Managed System Software screen appears.
Each managed system software application listed has a check box to the left of its
name. A check in the check box indicates that the software is selected for installation. As a default, all available
components are selected.
A button appears to the right of each component
name.
The Settings button indicates that you can install and
configure the component.
The More Info buttons are color coded:
Black indicates that the software is available for your system.
Yellow indicates that the software is available for your system, but
you must perform an additional action before you can install it; for example,
starting the driver for the component.
Red indicates that the software is unavailable for your system. You do
not have required hardware or software components installed.
Buttons that appear in gray do not provide either
information or configuration options.
Click Next to install the selected components.
The Installation Summary screen appears, listing all of the managed
system software services
that you selected for installation.
Click Next to continue.
A Confirm Install dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages are displayed, stating which components are being installed.
When the selected components are installed, the Installation Complete screen appears.
Click Finish.
Server Administrator starts.
Custom Upgrade
Start a system running X Windows.
Insert the Systems Management CD into the CD drive on your system.
If the CD does not automatically mount, type mount /mnt/cdrom.
After the CD mounts, the File
Manager should automatically start and display the contents of the root
directory of the CD.
Double-click the start.sh file in the File Manager window.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select System Type screen appears.
Click Upgrade Managed System.
The Select System Type screen appears.
Click Upgrade Managed System.
The Select Setup Type screen appears.
Click Custom Upgrade.
The Managed System Upgrade Selection screen appears.
Each managed system software component listed has a check box to the left of its
name. A check in the check box indicates that the component is selected for upgrade. As a default, all
installed components are selected.
A button to the right of each component name provides
information about the component.
The Upgrade Info button indicates that you can
upgrade and configure the component.
The More Info buttons are color coded:
Yellow indicates that the software is available for your system, but
either the current version is already installed or
you must perform an additional action before you can install it; for example,
starting the driver for the component.
Red indicates that the software is unavailable for your system. You do
not have required hardware or software components installed.
Buttons that appear in gray do not provide either
information or configuration options.
Click Next to upgrade the selected components.
The Installation Summary screen appears, listing all the managed system
software services you selected for
upgrade.
Click Next to continue.
A Confirm Install dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages are displayed, stating which components are being installed.
When the selected components are installed, the Installation Complete screen appears.
The Systems Management CD features an an Express Setup option and a
Custom Setup option for the unattended installation procedure.
Unattended installation allows you to install Server Administrator on multiple
systems simultaneously. You can perform an unattended installation by creating
an unattended installation package that contains all of the necessary managed system
software files. The unattended installation option also provides
several features that allow users 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 ISV.
When the package is distributed, the installation script executes to install the
software.
Creating and Distributing the Express Unattended Installation Package
The Express Setup unattended installation option uses the Systems
Management CD as the unattended installation package. The start.sh-license program accesses the Systems Management CD to
accept the software license agreement and install all required Server
Administrator components on selected remote systems. The start.sh-license program installs Server Administrator components on each remote system based on
the system's hardware configuration.
NOTICE: The -license
setting must be added to the start.sh command
for an Express Setup unattended installation to run. Adding the -license setting confirms that you accept the software license agreement for using the
unattended installation program. See "Optional Command Line Settings"
for more information.
You can make the Systems Management CD image available to the remote
system by distributing the entire contents of the CD.
Distributing the Entire CD as the Express Unattended Installation Package
NOTE:
Do not start an X Windows system.
Distribute the entire image of the Systems
Management CD to your target systems.
Configure your ISV software distribution software to
execute the start.sh-license program from the Systems
Management CD image.
The start.sh -license program executes to install Server Administrator on each remote system.
Creating and Distributing the Custom Unattended Installation Package
The Custom Setup unattended installation option creates an unattended installation
package in a directory on your system's hard drive. To create an unattended installation package, perform the following steps:
NOTE:
Do not start an X Windows system.
Create a destination directory for building the unattended installation
package.
Insert the Systems Management CD into the CD drive on your system.
If the CD does not mount automatically, type mount /mnt/cdrom.
Change to the directory that contains the installation shell script by
typing cd /mnt/cdrom.
Run the preparation script by typing sh
prepunat.sh.
Follow the directions on the screen.
Accept the license agreement when prompted.
When prompted for a destination (directory path) for the unattended
installation package, type the path to the directory you created in step 1.
Continue to follow the directions on the screen to install all necessary files to the
managed system.
Distributing Unattended Installation Packages
The custom unattended installation package is located in the directory you created in step
4 above.
This directory contains all of the managed system software components to
distribute, along with all the necessary unattended installation program files.
Configure your ISV software distribution software to
execute the start.sh program after the unattended installation package
has been
distributed.
Use your ISV distribution software to distribute the unattended installation package
to the remote systems.
The start.sh program executes to install Server Administrator on each remote system.
Table 8 shows the optional command line settings and
subcommands available for unattended installation.
Type the settings on the command line after start.sh with a space in between each
setting or subcommand. Subcommands must follow a setting.
(Where logfile is the file name and complete path.)
Specifies a nondefault filename for the short format
dependency log file. The full path including the name of the file must be
specified. If the path or the filename contains any spaces, then
the location must be enclosed in double quotes. See "Dependency Check."
-sil=<silfile>
(Where silfile is the file name and complete path.)
Runs a dependency check on the components specified in
the .sil file. For more information about the format of the .sil
file, see "Customization Files."
--help,
-?,
or
/?
Shows all available command line settings.
-license
Accepts the software license agreement for using the
unattended installation program. The license
agreement (license.txt) is located in the /app/doc directory on the Systems Management CD.
NOTICE: The -license
setting must be added to the command line
for an express unattended installation to run.
-silent
Runs the installation in command line
mode.
-license
Accepts the software license agreement for using the
silent unattended installation program. The license
agreement (license.txt) is located in the /app/doc directory on the Systems Management CD.
NOTICE: The -license
setting must be added to the command line
for a silent unattended installation to run.
-log=<logfile>
(Where logfile is the file name and complete path.)
Specifies a
nondefault filename for the short format log
file. For more information, see "Log Files." The full path including
the name of the file must be specified in this option. If the path or the
filename contains any spaces then the location must be enclosed in double
quotes. The location cannot contain any of the reserved words described in this
section such as icon, web, reboot, and so on.
-nosnmpsets
Disables SNMP Set operations on the Server Administrator
system.
If the -nosnmpsets option is not
used, the system will allow SNMP Set operations.
-noweb
The Server Administrator
Web server will not automatically start.
-sil=<silfile>
(Where silfile is the file name and complete path.)
Specifies a customization file. For more information about
the customization file, see "Customization Files." The full path including
the name of the file must be specified in this option. If the path or the
filename contains any spaces, then the location must be enclosed in double
quotes. The location cannot contain any of the reserved words described in this
section such as icon, web, reboot, and so on.
For example, running start.sh -silent -license -noweb
installs Server Administrator components on each remote system based on
the system's hardware configuration, accepts the software license agreement, and
does not automatically start the Server Administrator
Web server.
Customization files provide a way to customize the exact software components
to install. With the customization file, users can selectively install software
components for different systems using the same unattended installation
package. For example, you can choose to install Server Administrator, but not
the Remote Access Service, on a specific group of servers, and choose to install Server
Administrator, but not the Diagnostic Service, on another group of servers. The customization file
is formatted as a simple text file with a .sil filename suffix, in which each line contains one software
component relationship. For example:
component ID=yes/no
A designation of yes indicates that the component is installed. A designation of
no indicates that the component is not installed. Table 9 shows the
component IDs for each software component. The component ID is a 2- to
5- character designation.
Figure 4 shows an example of a customization file, \tmp\install.sil,
in which all available components except Remote Access Service and DRAC II are designated
to be installed.
The unattended installation log files capture the installation status of each software
component and the result of each unattended installation dependency check. For
more information
about log files generated by the dependency check, see "Dependency Check."
Two log files are generated in a temp
folder during an unattended installation, ominstal.log and omstatus.log. The temp
folder is typically located at
\tmp. Each log provides the installation status of each component,
the host system name, and the start and end time of the
installation. On a large-scale, unattended installation deployment of hundreds or
thousands of servers, users can save the unattended installation log file for
each server and easily isolate an installation problem on one or more servers
with the host information in the log file.
The omstatus.log provides installation
information in a shortened format that is designed to be easily read by scripts.
You can use this information to write automatic script files to query the
installation status and take remedy actions as needed. See Figure 5.
One line per software component is available. A value of "0" indicates that the installation of the
component succeeded, a value of "-1" indicates that installation of the component failed, and
a value of "1" indicates that the component did not install because a dependency was not met.
See "Dependency Check" for information about identifying installation
dependencies. The software component
ID is the same 2- to
5- character designation described in "Customization Files."
HOST = Server_xyz
START = Mon Sep 23 10:18:20 PDT 2002
sa = 0
old = 0
rac = 1
am = 0
drac2 = 1
ibm = 1
intc = 0
brcm = 0
sym = 0
END = Mon Sep 23 10:19:55 PDT 2002
The ominstal.log provides full text installation
information about the components. See Figure 6.
Figure 6. Example of a Full Text ominstal.log File
Applications with WARNING or DEPENDENCY cannot be installed using unattended
mode.
Host Name: Server_xyz
---------START Mon Sep 23 10:18:20 PDT 2002 -----------------------------------
OK: Server Administrator is all set to install
DEPENDENCY: Remote Access : Remote Access Controller was not detected on the
system.
OK: Storage Management is all set to install
OK: Diagnostic Service is all set to install
DEPENDENCY: Remote Assistant Card (DRAC II) : Remote Assistant Card (DRAC II)
was not detected on this system.
WARNING: Intel Agent : Warning! Current version is already installed on the
system.
DEPENDENCY: Broadcom Agent : Broadcom NIC was not detected on this system.
DEPENDENCY: IBM Agent : IBM Agent card was not detected on this system.
DEPENDENCY: Symbios Agent : LSI CI card not detected on the system.
The start.sh -dcheck program provides the capability to examine the
dependency status of software components without launching the actual
installation. This program generates two log files to your system's tmp folder: ominstal_chk.log and omstatus_chk.log.
The ominstal_chk.log provides full text information about the
dependency status of software components.
The omstatus_chk.log provides
dependency status information in a shortened format that is designed to be
easily read by scripts. See Figure 5 for an example of a log file.
There is one line per software component. A value of "0" indicates that the
installation is ready to proceed, a value of "1" indicates that one or
more components has a dependency warning, and a value of "2" indicates that one or more components has a dependency
error. The software component
ID is the same 2- to
5- character designation described in the "Customization Files"
section.
component ID 0/1/2
where "0" means OK to install, "1" means warning,
and "2" means dependency error.
See "Log Files" for more information.
The format is very similar to the .sil file format and the
software component IDs are
identical.
Use the following command line settings with the dependency check feature.
Dependency Check Command Line Settings
Table 10 shows the dependency check command line settings available for unattended installation.
Type the optional settings on the command line after start.sh -dcheck with a space in between each setting.
Runs a dependency check on the components specified in
the .sil file. For more information about the format of the .sil
file, see "Customization Files."
-logfile <logfile-location>
Specifies a nondefault filename for the short format
dependency log file. The full path including the name of the file must be
specified. If the path or the filename contains any spaces then
the location must be enclosed in double quotes.
For example, running start.sh -dcheck -sil
dep.sil runs the dependency check for all components listed in the
customization file (dep.sil), and saves the dependency check log files (ominstal_chk.log
and omstatus_chk.log)in the temp folder.
You can uninstall Server Administrator using the Systems
Management CD or from the Red Hat Linux command line. Additionally, you can perform an
unattended uninstallation on multiple systems simultaneously.
Prerequisites for Uninstalling Server Administrator
Insert the Systems Management CD into the CD drive on your system.
If the CD does not automatically mount, type mount /mnt/cdrom.
After the CD mounts, the File
Manager should automatically start and display the contents of the root
directory of the CD.
Double-click the start.sh file in the File Manager window.
The Welcome to Dell OpenManage Systems Management Installation screen appears.
Click Next.
A software license agreement appears.
Click Accept if you agree.
A message displays stating that a setup wizard is being prepared to lead you through the setup process.
The Select System Type screen appears.
Click Uninstall.
The Uninstall Selection screen appears. Each managed system software component listed has a check box to the left of its
name. A check in the check box indicates that the software component is selected for
uninstallation. As a default, all installed managed system software components
are selected.
Click Next to uninstall the selected managed system software components.
The Uninstall Summary screen appears, listing all of the managed
system software services you selected for
uninstallation.
Click Next to continue.
The Confirm Uninstall dialog box appears.
Click Yes to confirm your selections.
The Dell OpenManage Components screen appears. Messages display, stating which components are being
uninstalled.
Insert the Systems Management CD into the CD drive on your system.
If the CD does not mount automatically, type mount /mnt/cdrom.
Change to the directory that contains the uninstallation shell script by
typing cd /mnt/cdrom.
Run the uninstall.sh
file that is located at /usr/lib/dell/openmanage on your hard drive.
Follow the directions on the screen to uninstall all installed Server
Administrator files from the
managed system.
Performing an Unattended Uninstallation of Managed System Software
The Systems Management CD features an unattended uninstallation procedure.
Unattended uninstallation allows you to uninstall Server Administrator from multiple
systems simultaneously. 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.
Distributing the Unattended Uninstallation Package
The Systems Management CD has been preconfigured to act as the unattended
uninstallation package.
To distribute the package to one or more systems, perform the following steps:
Configure your ISV software distribution software to
execute the uninstall.sh program after the unattended uninstallation package has been
distributed.
Use your ISV software distribution software to distribute the unattended
uninstallation package to the remote systems.
The uninstall.sh program executes to uninstall Server Administrator on each remote system.
On systems running supported Red Hat Linux operating systems, you can configure Server Administrator to change the default password for
SNMP Set operations.
Changing the Default Password for SNMP Set Operations
NOTE:
The default password for root is calvin.
Type the following command:
dcinuser32
The Systems Management User Security utility displays the following
instructions:
Dell Systems Management User Security Utility
Dell Computer Corporation.
Version x.y.y (BLD_zzzz)
The user name and password allow SET commands to be honored by
Server Administrator; otherwise SET requests will be rejected.
Do you want to change the default security settings for
Server Administrator?
(Y for Yes, N for No, or Q to Quit; then press the Enter key):
If you want to change the default password, press <y>, type the
new password, and type the new password again to confirm it.
If you do not want to change the default password, press <n> or <q> to exit.
Exiting resets the root password for allowing SNMP Set operations to its default
value.
This section explains how to install, upgrade, and uninstall Server
Administrator on a
system that is running a supported Novell NetWare operating system. This section
includes the following topics:
This section explains how to install and upgrade the Server Administrator. There
are two installation options:
Use the setup program on the Systems Management CD to install or upgrade Server Administrator and other managed
system software.
Use the silent installation procedure to install Server Administrator
and other managed system software on multiple systems.
Prerequisites for Installing or Upgrading Server Administrator
The following are prerequisites for installing Server Administrator:
You must have administrator privileges.
The SNMP agent that is provided with the operating system must be installed on
the managed system. If you want to use supporting agents for the SNMP
agent, 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.
NOTE: During a Custom
or Express installation, individual Server Administrator services
will not be installed on managed systems that do not meet the
specific hardware and software installation requirements
for that service. For example, the Server
Administrator Remote Access Service software module will not be installed
during an Express installation unless the managed system has
an installed remote access controller.
Installing and Upgrading Server Administrator Using the Systems Management CD
Insert the Systems Management CD into the system's CD drive.
Type load cdrom and press <Enter>.
If the volume name does not display, type volumes at the console prompt and
press <Enter>.
All available volumes display.
Record the volume name for the CD drive.
Type load nwconfig and press <Enter>.
In the NetWare Configuration screen under Configuration Options, select
Product Options and press <Enter>.
On the Other Installation Actions menu, select Install a product not listed
and press <Enter>.
NOTE: A dialog box listing previously
selected paths might appear after pressing <Enter>. Press
<Esc> to close this dialog box.
A default message appears, stating that the product is to be installed from
drive A.
Press <F3> to specify a different installation path.
Erase A: and type volume_name:netware,
where volume_name is the name of the
volume assigned to the CD drive.
NOTE: You cannot enter spaces in the pathname.
After you enter the path, press <Enter> to continue.
A message appears, stating:
Indicate which file groups you want installed.
Select any other components you want to install. Server Administrator is not included in the list
of file groups because it is installed by default.
NOTE: Items selected for installation have
an X next to them. Pressing <Enter> next to an item selects that
item. Pressing the spacebar next to an item toggles the selection
between selected and not selected.
Press <F10> to accept the components you have selected and to continue with
installation.
The installation of Server Administrator and the components you selected begins.
Status messages appear.
The Systems Management Security Utility appears and asks whether you want to
change the default security settings for SNMP Set operations.
NOTE: The default password for root is calvin.
Select one of the following options:
Press <y> to change the default password for root.
Type the new password, and then type the password again to
confirm.
Press <n> or <q> to exit the security utility and reset the
password for root to its default value.
The installation of Server Administrator and the components you selected
continues.
Status messages appear. When the installation is complete, a
dialog box
appears stating that the installation is complete.
Press <Enter>.
Press <Esc> twice and
<Enter> once to return to the console prompt and exit the NWConfig
program.
Reboot the system.
Performing a Silent Installation or Upgrade of Server Administrator
Use the following procedure to silently install Server Administrator for the
first time or to upgrade to a more recent version of Server Administrator.
Insert the Systems Management CD into the system's CD drive.
Type load cdrom and press <Enter>.
If the volume name does not display, type volumes at the console prompt and
press <Enter>.
All available volumes display.
Record the volume name for the CD drive.
Type load volume_name:\Netware\ominss32.nlm
-license and press <Enter>.
The installation script installs all necessary files to the
managed system. If you are upgrading to a more recent version of Server
Administrator, the installation script will uninstall previously installed
versions before installing the current version of Server Administrator.
NOTICE: The -license
setting must be added to the command
for a silent installation to run. Adding -license to the command confirms that you accept the software license agreement for using the
silent installation program. You can view the
license agreement (license.txt)on the Systems Management CD in the app/doc
directory.
You can uninstall Server Administrator from your system using the Product Options menu in the NWConfig
utility
or using the silent uninstallation script provided on the Systems Management
CD.
Uninstalling Using the NWConfig Utility
At the NetWare command line console, type load
nwconfig and press <Enter>.
Select Product Options from the Configuration Options menu.
Select View/Configure/Remove from the Other
Installation Actions menu.
Select SRVADMIN from the Currently Installed
Products menu and press <Delete> to uninstall Server
Administrator.
Performing a Silent Uninstallation
At the NetWare command line console, type omunins.ncf
and press <Enter>. The uninstallation script uninstalls all Server Administrator files from the
managed system.
