######################################################################
DELL(TM) OPENMANAGE(TM) INSTALLATION AND SERVER MANAGEMENT README
######################################################################

Version 5.2
Release Date: March 2007

Dell OpenManage Subscription Service Kit consists of a suite of five
CDs to assist you in installing, configuring, and updating the
necessary programs and operating systems you need to get your
Dell PowerEdge(TM) system up and running.

######################################################################
CONTENTS
######################################################################

* Criticality
* Compatibility/Minimum Requirements
* Release Highlights - Features
* Release Highlights - Fixes
* Installation
* Pre-requisite Checker
* User Notes
* Known Issues
* History

######################################################################
CRITICALITY
######################################################################

2 = Recommended

######################################################################
COMPATIBILITY/MINIMUM REQUIREMENTS
######################################################################

The following Dell PowerEdge systems are supported for "Dell PowerEdge
Installation and Server Management" CD version 5.2:

======================================================================
SUPPORTED SYSTEMS
======================================================================

* The following PowerEdge systems are supported:

  600SC, 650, 700, 750, 800, 830, 840, 850, 860, 1600SC, 1650, 1655MC,
  1750, 1800, 1850, 1855MC, 1900, 1950, 1955, 2600, 2650, 2800, 2850,
  2900, 2950, 2970, 4600, 6600, 6650, 6800, 6850 and 6950.

######################################################################
RELEASE HIGHLIGHTS - FEATURES
######################################################################

* Added installation support for the following operating system:

  - Red Hat(R) Enterprise Linux version 5
  - Windows Server 2003 SP2

* Added installation support for the following PowerEdge systems:

  - 2970
  - 6950

* For a detailed table of supported systems and the operating systems,
  see the "Software Support Matrix for PowerEdge Systems" document.
  See "index.htm" file in the "srvadmin\windows\docs\readme\PEOSOM\"
  directory on the "Installation and Server Management" CD.

######################################################################
RELEASE HIGHLIGHTS - FIXES
######################################################################

N/A

######################################################################
INSTALLATION
######################################################################

* On Microsoft(R) Windows(R) operating systems, run "setup.exe" from
  the "srvadmin\windows" directory of the CD or the software package.
  NOTE: This step is not necessary if the CD runs automatically.

* On Red Hat Enterprise Linux and SUSE Linux Enterprise Server
  operating systems, to perform an "Express Install," execute the
  "srvadmin-install.sh" script from the
  "/srvadmin/linux/supportscripts" directory as follows:

  "sh srvadmin-install.sh -x"

* Detailed installation instructions, including silent install
  options, can be found in the "Dell OpenManage Installation and
  Security User's Guide" on the "Dell PowerEdge Documentation" CD or
  on the Dell Support website at "support.dell.com."

######################################################################
PREREQUISITE CHECKER
######################################################################
The Prerequisite Checker displays three types of messages. These are
informational, warning, and error messages.

Informational messages indicate a condition of which you should be
aware. They do not prevent a feature from being installed.

Warning messages indicate a condition that prevents a feature
from being installed during "Express" installation. It is best that
you resolve the condition causing the warning before proceeding with
the installation of that feature. If you decide to continue, you can
select and install the feature using the Custom installation.

Error messages indicate a condition of which you should be aware
that prevents the feature from being installed. You must resolve the
condition causing the error before proceeding with the installation of
that feature. If not, the feature will not be installed.

To execute the Prerequisite Checker silently, run the utility
RunPreReqChecks.exe with the /s command line option. e.g.
"RunPreReqChecks.exe /s".

After running it, an htm file will be created in the %Temp% directory.
The file is named omprereq.htm, and will contain the results of the
prerequisite check.

NOTE: The Temp directory is usually "X:\Documents and Settings\
username\Local Settings\Temp." To find %TEMP%, go to a command line
prompt and type "echo %TEMP%".

The return code from RunPreReqChecks.exe will be the number associated
with the highest severity condition for all the features. The return
code values are as follows:

Return Code  Description
-----------  ---------------------------------------------------------
     3       At least one feature has issued an error message.  The
             Prerequisite Checker has completed successfully.

     2       At least one feature has issued a warning message.
             The Prerequisite Checker has completed successfully.

     1       At least one feature has issued an informational message.
             The Prerequisite Checker has completed successfully.

     0       Prerequisite Checker completed successfully with no error,
             warning, or informational messages.

    -1       Windows Host Scripting Error (WSH). The Prerequisite
             Checker did not run.

    -2       Operating system is not supported. The Prerequisite Checker
             did not run.

    -3       User does not have Administrator privileges. The
             Prerequisite Checker did not run.

    -4       Unused.

    -5       Failed to change working directory to %TEMP%. The
             Prerequisite Checker did not run.

    -6       Destination directory does not exist. The Prerequisite
             Checker did not run.

    -7       Internal Error. The Prerequisite Checker did not run.

    -8       An instance is already running. The Prerequisite Checker
             did not run.

    -9       Windows Host Scripting Error (WSH) is wrong version,
             corrupted or not installed. The Prerequisite Checker did
             not run.

   -10       Error with scripting environment. The Prerequisite Checker
             did not run.


Additionally, The results of the Prerequisite Checker are written to
the registry under the main registry key for the Management Station:

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

and under the main registry key for the Managed System:

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

Each feature has an associated value set after running the
prerequisite check, they are the same values as those returned by
RunPreReqChecks.exe.

Feature IDs for the Management Station
----------------------------------------------------------------------
AMCON          Array Manager Console
ITA            IT Assistant
RACMS          Remote Access Controller Management
ADS	       Active Directory Snap-In Utility
BMU	       Baseboard Management Controller Management Utility

Feature IDs for the Managed System:
----------------------------------------------------------------------
BRCM           Broadcom NIC agent
INTEL(R)       Intel NIC agent
IWS            Server Administrator Web Server
OMSM           Storage Management
RAC3           Remote Access Controller (DRAC III)
RAC4           Remote Access Controller (DRAC 4)
RAC5	       Remote Access Controller (DRAC 5)
SA             Server Administrator

######################################################################
USER NOTES
######################################################################

======================================================================
USER NOTES FOR ALL SUPPORTED OPERATING SYSTEMS
======================================================================

* The Dell OpenManage Server Administrator CD is bootable. If the
  system is required to reboot from a different drive, remove the CD
  from the drive or change the boot order.

* Adaptec utilities are no longer available on the "Dell PowerEdge
  Installation and Server Management" CD. They continue to be
  available for customer downloads from the Dell Support website at
  "support.dell.com."

* The "Dell OpenManage Software Quick Installation Guide" provides
  instructions on how to install the applications on the "Installation
  and Server Management" CD for all supported operating systems. See
  the "QUICK_INSTALL_GUIDE.htm" file in the
  "srvadmin\docs\en\OpenManage_QIG" directory on the "Installation
  and Server Management" CD.

* If you are running any application on the "Installation and Server
  Management" CD, close the application before installing Server
  Administrator applications.

* This version of Dell OpenManage Install only supports upgrades from
  Dell OpenManage systems management software version 4.3 or above.
  If you are using a version prior to 4.3, you must uninstall the
  previously installed version before installing this new version.
  You can also upgrade the previously installed version to version
  4.3 first (if your version is 3.0 or higher), and then upgrade to
  this version.

* If you are running virtual media on your DRAC controller over a
  Wide Area Network (WAN) with low bandwidth and latency, launching
  OpenManage Install directly on the virtual media may fail. In case
  of failure, copy the Web install package (available on
  support.dell.com) directly to your local system first and directly
  launch Dell OpenManage Install from your local system.
  (69303)

* If you are running Red Hat Enterprise Linux version 5 virtualization
  kernel, DRAC controller will not be available from Server
  Administrator.

======================================================================
USER NOTES FOR SUPPORTED WINDOWS OPERATING SYSTEMS
======================================================================

* This version of Dell OpenManage systems management software requires
  an MSI version of 3.1 or later on your system. If the version is
  lower than 3.1, the Prerequisite Checker prompts you to upgrade to
   MSI version 3.1.

* Starting with Dell OpenManage systems management software version
  5.0, Dell OpenManage Array Manager is no longer supported on Dell.
  Upgrading to Dell OpenManage systems management software version 5.2
  will remove Array Manager from your system. Switch to using Storage
  Management Service instead. Do not upgrade to Dell OpenManage
  systems management software version 5.2 if you require Array
  Manager.

* OpenManage 5.2 requires a minimum of Windows 2003 SP1 to be
  installed on supported Windows 2003 Operating systems.
  If you are using OpenManage 4.3, 4.4 or 4.5 on Windows 2003 you must
  first apply Windows 2003 SP1 or higher before upgrading to
  OpenManage version 5.2. If your version of OpenManage is 4.2 or
  lower, upgrade to OpenManage 4.3 first, then apply SP1 and then
  upgrade to OpenManage version 5.2. Alternately, if you do not want
  to retain OpenManage settings, you can uninstall OpenManage, apply
  the Windows service pack and then install OpenManage version 5.2.

* In the Prerequisite Checker screen, you may get the following
  message, "An error occurred while attempting to execute a Visual
  Basic Script. Please confirm that Visual Basic files are installed
  correctly." This error occurs when the Prerequisite Checker invokes
  the Dell OpenManage "vbstest.vbs" (a Visual Basic [VB]) script to
  verify the installation environment and fails for some reason.

  The possible causes are:

  1. Incorrect Internet Explorer "Security" settings.

     Ensure that "Active Scripting" is enabled by clicking "Tools" ->
     "Internet Options" -> "Security" -> "Custom Level" ->
     "Scripting" -> "Active Scripting" -> "Enable"

     Ensure that "Scripting of Java Applets" is enabled by
     Clicking "Tools" -> "Internet Options" -> "Security" ->
     "Custom Level" -> "Scripting" -> "Scripting of Java Applets" ->
     "Enable."

  2. Windows Scripting Host (WSH) has disabled the running of VB
     scripts.

     By default, WSH is installed during operating system
     installation. WSH can be configured to prevent scripts
     with a ".VBS" extension from being run. On the Desktop,
     right-click "My Computer", then go to "Open" -> "Tools" ->
     "Folder Options" -> "File Types."  Look for the extension
     "VBS" and verify that "File Types" is set to "VBScript
     Script File." If not, click "Change" and choose "Microsoft
     Windows Based Script Host" as the application that runs
     the script.

  3. WSH is the wrong version, is corrupted, or is not installed.

     By default, WSH is installed during operating system
     installation. To download the current WSH version, go to:

     "http://msdn.microsoft.com/downloads/list/webdev.asp"

  4. The Scrrun.dll file may not be registered. Register it manually
     by running the following command:

     "regsvr32 Scrrun.dll"

* If you burn your own CD, be aware of the following requirement:
  MSI requires all installers to specify the "MEDIAPACKAGEPATH"
  property if the MSI file does not reside on the root of the CD.
  This property is set to "\srvadmin\windows\SystemsManagement" for
  the Server Administrator MSI package. Ensure that the CD
  layout remains the same when burning your own CD. The
  "SysMgmt.msi" file must reside in the
  "\srvadmin\windows\SystemsManagement" folder on the CD.

  For more information, go to the Microsoft website:

  "http://msdn.microsoft.com/library/default.asp?url=/library/en-us/
  msi/setup/mediapackagepath.asp"

* MSI reference counting takes effect if you install the Intel
  SNMP agent using the MSI provided by Intel, and then install the
  Intel SNMP agent again using Dell OpenManage Install. The Intel
  SNMP agent is not uninstalled during installation of the MSI;
  you must remove both installers from the system to remove the
  agent.

* When launching the MSI installation packages from your Windows
  Explorer, all MSI output will be logged into the file,
  "SysMgmt.log." It is stored at "%TEMP%."

* During installation/uninstallation, the Windows Installer Service
  may display the time remaining for the current task to complete.
  This is only an approximation by the Windows Installer Engine based
  on varying factors.

* A new console window must be opened and CLI commands executed from
  that window after an "Unattended Installation" has completed. It is
  not possible to execute CLI commands from the same console window on
  which Server Administrator was installed.

* If Server Administrator is being installed or uninstalled on a
  system where the Web download version of Dell PowerEdge
  Diagnostics (version 2.2) or Dell OpenManage Server Update Utility
  is running, the Windows Installer Service may display a message
  stating that specific files needed by Server Administrator are in
  use by Diagnostics or by the Server Update Utility. Select the
  "Ignore" option in the message box to continue. (62159)


* When installing Server Administrator on supported Windows systems,
  additional "Custom Install" components selected during a "Typical
  Install" are retained upon returning to the "Typical Install"
  option. To remove these components from the Selected Components
  list, deselect them from the "Custom Install" dialog.

* Before installing Server Administrator on Windows 2000 systems,
  verify that the "Unsigned non-driver installation behavior"
  policy is set to "Silently succeed." Otherwise, the Dell OpenManage
  Installer cannot install the Server Administrator applications
  properly.

  This policy can be found in "Start" -> "Programs" ->
  "Administrative Tools" -> "Local Security Policy." Expand "Security
  Settings" and select "Local Policies" -> "Security Options." After
  changing the policy, execute "secedit /refreshpolicy MACHINE_POLICY"
  from the command shell to invoke the security policy change.
  After Server Administrator installation is completed, this policy
  can be set to its original value.

* During installation of Server Administrator on supported Windows
  systems, if an "Out of Memory" error message displays, you must exit
  the installation and free up memory. Close other applications
  or perform any other task that will free up memory, before
  re-attempting Server Administrator installation.

* Server Administrator may conflict with the Intel IMB driver.
  You may receive an informational message recommending that you
  uninstall the Intel IMB driver before installing Server
  Administrator. You can do so through the "Device Manager."
  Perform the following steps:

  1. Open the "Device Manager."
  2. Expand the "System devices" list.
  3. Right-click the device with a name of the form "IMB Driver *"
     and select "Uninstall."
  4. Select "OK" to uninstall.

  If you choose to install Server Administrator while the Intel
  IMB driver is being installed, you may have problems running
  Server Administrator. Server Administrator services may fail
  to start or Server Administrator may have problems accessing
  sensor data.

* If you upgrade the Microsoft Installer Engine to version 3.1 on
  your system using Dell OpenManage Install, you may have to reboot
  your system in order to install other software applications such
  as the Microsoft SQL Server.

  NOTE: Dell OpenManage software does not require a reboot - the
  software will install and operate without a reboot.


* When Multi-lingual User Interface (MUI) is set to non-unicode
 languages like Simplified Chinese or Japanese, the user is
 expected to set the system locale to Simplified Chinese or Japanese.
 This enables the Prerequisite Checker messages to be displayed.
 This is because any non-Unicode application will run
 only when the system locale (also called "Language for non-Unicode
 Programs" on XP) is set to match the application's language.

* Upgrade may require a reboot if the files to be upgraded are in
  use. This is a typical windows installer behavior. It is
  recommended that you reboot the system when prompted. (66818)

* Broadcom/Intel SNMP agent installers are provided by Broadcom/Intel
  and they do not support installation of these components in the
  custom directory.
  (71022)

======================================================================
USER NOTES FOR SUPPORTED RED HAT ENTERPRISE LINUX AND SUSE LINUX
ENTERPRISE SERVER OPERATING SYSTEMS
======================================================================

* To avoid warnings concerning the RPM package key during
  installation, mount the CD or package, and import the key using the
  command:

  rpm --import /mnt/cdrom/srvadmin/linux/RPM-GPG-KEY

* If you performed a default manual install of your Linux operating
  system without using Dell Server Assistant, you will need a set of
  Server Administrator-dependent RPM files installed prior to
  installing Server Administrator.

  These RPM files can be found on the Linux operating system media.
  Alternately, these RPM files can be located under the "/srvadmin/
  linux/RPMS/supportRPMS" folder on the Dell OpenManage Server
  Administrator CD or software package.

  Install these RPM files prior to installing Server Administrator
  otherwise the installation might halt due to dependency errors.

* If you have performed a non-default install of your Linux
  operating system using your Linux operating system media, you may
  see missing RPM file dependencies while installing Server
  Administrator. Server Administrator is a 32-bit
  application. When installed on a system running a 64-bit version of
  Red Hat Enterprise Linux operating system, the Server Administrator
  remains a 32-bit application, while the device drivers installed by
  Server Administrator are 64-bit. If you attempt to install Server
  Administrator on a system running Red Hat Enterprise Linux (versions
  4 and 5) for Intel EM64T, be sure to install the applicable 32-bit
  versions of the missing RPM file dependencies. The 32-bit RPM
  versions always have "i386" in the file name extension. You may also
  experience failed shared object files (files with "so" in the file
  name extension) dependencies. In this case, you can determine which
  RPM is needed to install the shared object, by using the RPM
  "--whatprovides" switch. For example:

  rpm -q --whatprovides libpam.so.0

  An RPM name such as "pam-0.75-64" could be returned, so obtain and
  install the "pam-0.75-64.i386.rpm". When Server Administrator is
  installed on a system running a 64-bit version of a Linux operating
  system, ensure that the "compat-libstdc++-<version>.i386.rpm" RPM
  package is installed. You will need to resolve the dependencies
  manually by installing the missing RPM files from your Linux
  operating system media.

* Source packages for RPMs are available on a CD image that is
  available from the Dell Support website at "support.dell.com."

* The OpenIPMI device driver used by Server Administrator will
  conflict with the Intel IMB device driver. Dell requires that you
  uninstall the IMB driver before installing Server Administrator.

* Non-factory Installation Methods.
  You can install managed systems software using one of the two
  install methods.
  The "Installation and Server Management" CD provides installation
  methods - scripts and RPM packages to install, upgrade, and
  uninstall Server Administrator and other managed system software
  components on your managed system. Additionally, you can install
  Server Administrator on multiple systems through an unattended
  installation across your network.

   - First install method: Use the provided custom install
     script, "srvadmin-install.sh." This script allows unattended
     express installation and custom, unattended or interactive
     installation. By including the "srvadmin-install.sh" script in
     your Linux scripts you may install Server Administrator on single
     or multiple systems, in attended or unattended modes and locally
     or across a network.

   - Second install method - Use the Server Administrator RPM
     packages provided in the custom directories and the Linux "rpm"
     command. This allows custom interactive installation. You may
     write Linux scripts that install Server Administrator on a single
     or multiple systems through an unattended installation locally or
     across a network.

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

======================================================================
USER NOTES FOR UPGRADE ON SUPPORTED RED HAT ENTERPRISE LINUX
AND SUSE LINUX ENTERPRISE SERVER OPERATING SYSTEMS
======================================================================

* There are a few additional components that can be installed
  on a system that already has Server Administrator installed.
  For example, you can install Dell PowerEdge Diagnostics on a
  system that has previously been installed with managed system
  software. On such a system, while uninstalling Server
  Administrator, only those RPM packages that are not required by any
  of the newly installed components are uninstalled. In the above
  example, Dell PowerEdge Diagnostics requires packages such as
  "srvadmin-omilcore-X.Y.Z-N" and "srvadmin-hapi-X.Y.Z-N." These
  packages will not get uninstalled during an uninstallation of Server
  Administrator.

  In this case, if you try to install Server Administrator later
  by running the "sh srvadmin-install.sh" command, you
  will get the following message:

  "Server Administrator version X.Y.Z is currently installed.
   Installed Components are:
      - srvadmin-omilcore-X.Y.Z-N
      - srvadmin-hapi-X.Y.Z-N
   Do you want to upgrade Server Administrator to X.Y.Z?
   Press ('y' for yes | 'Enter' to exit): "

  On pressing 'y', only those Server Administrator packages (in the
  above example, "srvadmin-omilcore-X.Y.Z-N" and
  "srvadmin-hapi-X.Y.Z-N") that are residing on the system are
  upgraded.

  If you have to install other Dell OpenManage components as well, you
  will have to run the following command once again:

  "sh srvadmin-install.sh"

* While OpenManage 4.5 is upgraded to OpenManage 5.0 in ESX, the
  following error message may be displayed:

  error: Failed dependencies:
  openipmi >= 35.12 is needed by srvdmin-ipmi-5.2.0-NNN.rhel3

  When you face this issue, manually install the relevant openipmi
  package applicable to the operating system (in this case,
  openipmi-35.12.RHEL3-3dkms.noarch.rpm) and dkms-2.0.10-1.noarch.rpm
  (if necessary). Use the "rpm" command and then proceed with
  upgrading other Dell OpenManage components using srvadmin-install.sh
  script. These openipmi packages can be located under
  "srvadmin/linux/RPMS" directory on the CD or on the software
  package.

  You may also face this issue while upgrading from ESX 2.x to ESX
  3.0. You can avoid this issue by uninstalling Dell OpenManage 4.5
  first and then upgrading to ESX 3.0. You can later install Dell
  OpenManage 5.2 on ESX 3.0 (67844)

* While upgrading, all installed Server Administrator components,
  including ones that are not needed, but were previously installed,
  will also be upgraded. The upgrade will not attempt to detect and
  remove unwanted components.

* Under some conditions with Dynamic Kernel Module Support (DKMS),
  versions prior to version 2.0.9, device driver building may fail.
  This could prevent Server Administrator from installing. You may
  see the following error message:

  "Building module:
  cleaning build area....(bad exit status: 2)
  make KERNELRELEASE=2.6.5-7.232-smp -C src KSP=/lib/modules/
    2.6.5-7.232-smp/build MANDIR=%{_mandir}....(bad exit status: 2)

  Error! Bad return status for module build on kernel:
  2.6.5-7.232-smp (x86_64)
  Consult the make.log in the build directory
  /var/lib/dkms/e1000/6.2.11/build/ for more information."

  To resolve the device driver build problems:

  1. Update the DKMS version to 2.0.9 or later.
  2. Uninstall the kernel source on your system.
  3. Reinstall the kernel source on you system.
  4. Build and install the device driver that failed to
     build.
  5. If Server Administrator has failed to install, either

     install Server Administrator using the following script,
     "./srvadmin-install.sh"

     OR

     install the appropriate Server Administrator RPMs.
  (31564) (31829) (42077)

* Dell OpenManage Server Administrator version 5.2 does not
  support PE600SC, PE650 and PE1600SC. This is enforced by the scripted
  installs and the install will fail. This is however not enforced in
  the manual rpm installs.
  (111175)

* Most of the RPM packages have been written and tested for Dell
  PowerEdge systems and the Linux flavors that have been listed in
  this readme. If you try to install them on an unsupported system or
  an unsupported operating system, you may see unpredictable behavior
  during the install, uninstall, or during use of the RPM package.
  (68189)



######################################################################
KNOWN ISSUES
######################################################################

======================================================================
ISSUES FOR ALL SUPPORTED OPERATING SYSTEMS
======================================================================

* If you already have Adaptec Fast Console installed on your
  system, you must uninstall this application before installing
  the Server Administrator Storage Management Service.

======================================================================
ISSUES FOR SUPPORTED WINDOWS OPERATING SYSTEMS
======================================================================

* Dell OpenManage Install does not support Windows "Advertised"
  installation - the process of automatically distributing a program
  to client computers for installation through Windows group policies.
  (144364)

* If you upgrade from version "X" to version "Y" using MSP
  and then try to use the version "Y" CD (full install) or Web package,
  the Prerequisite Checker on the version "Y" will inform you that the
  current version is already installed. If you proceed, the
  installation will not run in "Maintenance" mode and you will
  not get the option to "Modify," "Repair," or "Remove."
  Proceeding with the installation will remove the MSP and create
  a cache of the MSI file present in the version "Y" package. When
  you run it a second time, the installer will run in "Maintenance"
  mode.
  (154376)

* If you choose to remove Dell OpenManage systems management software
  using the CD or Web package, it could take a few minutes before
  the system responds after you select "Remove," to continue. This may
  give you an impression that the system has stopped responding. Dell
  recommends that you remove Dell OpenManage systems management
  software using "Add or Remove Programs."
  (144970)

* When launching the Dell OpenManage Installer, 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." This is most likely due to insufficient
  COM permissions on the system. See the following article to remedy
  this situation:

  http://support.installshield.com/kb/view.asp?articleid=Q104986

  The Dell OpenManage Install may also fail if a previous installation
  of Dell OpenManage systems management software or some other
  software product was unsuccessful. A temporary Windows Installer
  registry can be deleted, which may remedy the Dell OpenManage
  Install failure. Delete the following key, if present:

  HKLM\Software\Microsoft\Windows\CurrentVersion\Installer
  \InProgress
  (144114, 124944)

* If both Server Administrator and Management Station are to be
  installed on a system, and the Remote Access Controller (RAC)
  feature is required, install the Server Administrator Remote
  Access Service. The Server Administrator Remote Access Service
  includes the functionality supplied by the Management Station
  Remote Access Console.
  (139224)

* * In the "Custom Setup" screen, you must click on an active feature
  to view your hard drive space availability or change the
  installation directory. You do not have these options for a feature
  that is not available. For example, if Feature A is selected for
  installation (active) and Feature B is not available, the "Change"
  and "Space" buttons will be disabled if you click Feature B. Click
  Feature A to view the space availability or to change the
  installation directory.
  (139020)

* When adding a feature, if you do not have sufficient disk space on
  the drive where Server Administrator or Management Station is
  installed, you will get an out-of-disk-space message suggesting
  that you select a different destination drive. To correct the
  problem, free up space on the drive where Server Administrator
  or Management Station is installed.
  (139143)

* If you have insufficient disk space on your Windows system drive,
  you may encounter misleading warning or error messages when you run
  Dell OpenManage Install. Additionally, windows installer requires
  space to temporarily extract the installer package to the %TEMP%
  folder. Ensure that you have sufficient disk space (100 MB or more)
  on your system drive prior to running Dell OpenManage Install.
  (145218)


* Dell OpenManage systems management software versions 1.x through
  4.2 must be removed to successfully install Dell OpenManage
  systems management software version 4.3 or later. Use
  "srvadmin\support\OMClean\OMClean.exe" found on your "Installation
  and Server Management" CD to remove the old version of Dell
  OpenManage systems management software.
  (138227)


* If you see the following error when trying to launch Dell OpenManage
  Install, it is recommended that you run the "OMClean.exe" program,
  under the "srvadmin\support\OMClean" directory, to remove an old
  version of Server Administrator on your system.

  "An older version of Server Administrator software is detected on
   this system. You must uninstall all previous versions of Server
   Administrator applications before installing this version."
  (149522)

* When launching the "Quick Installation Guide" or "User's Guide"
  from the Prerequisite Checker, a Windows message is displayed
  indicating that the page is blocked due to enhanced security
  configuration. You must add the IP address of your local machine
  to the "Trusted Sites" list for the pages to display or lower your
  security settings.
  (134991)

* Uninstall previous versions of Server Administrator before
  installing Citrix Metaframe (all versions). As errors may exist
  in the registry after the Citrix Metaframe installation, you
  will need to reinstall Server Administrator.
  (67690)

* When you run Dell OpenManage Install in English, German, French,
  or Spanish and get unreadable characters on the "Prerequisite
  Check Information" screen, ensure that your browser encoding has
  the default character set. Resetting your browser encoding to
  use the default character set will resolve the problem.
  (145698)

* If you have installed Server Administrator and Dell PowerEdge
  Diagnostics in the same folder, PowerEdge diagnostics may fail to
  work. Later on uninstalling Server Administrator, you may also lose
  all PowerEdge Diagnostics files. To avoid this problem, install
  Server Administrator and PowerEdge Diagnostics in different folders.
  In general it is recommended that more than one application is not
  installed in the same folder.

* After installing Dell Remote Access Controller 4 software on
  Windows Server 2003 x64 Editions, the device manager may show a
  warning state (yellow bangs) for two devices. To change the state of
  these devices to Normal, perform the following steps:

  1. Right-click the device and choose "Update driver."

  2. In the "Hardware Update Wizard" you are provided the option "Can
     Windows connect to Windows Update to search for software? Choose
     "No, not at this time" and click "Next."

  3. At the prompt "What do you want the wizard to do?" choose
     "Install from a list or specific location (Advanced)" and click
     "Next."

  4. At the prompt "Please choose your search and installation
     options," select "Search for the best driver in these locations"
     and check "Include this location in the search:."

  5. Browse for the selected driver in the "<install directory>/RAC4"
     path, typically "C:\program files (x86)\dell\sysmgt\rac4\
     rac4ser.inf". The driver will load and the device will be
     identified as RAC PCI function <n>. The value of <n> can vary.

  6. Click "Finish" to complete the hardware update.

  Repeat the same steps for the other device with the warning state.
  (32223)

======================================================================
KNOWN ISSUES FOR SUPPORTED RED HAT ENTERPRISE LINUX AND SUSE LINUX
ENTERPRISE SERVER OPERATING SYSTEMS
======================================================================

* Attempts to upgrade Server Administrator version 4.3 on a system
  running a Linux operating system may fail to update the Dell Remote
  Access Controller (DRAC) package "srvadmin-racsvc-4.3.0-785" when
  attempted from the RPM command-line. To overcome this issue, stop
  the service(s) first, and then retry the upgrade:

  srvadmin-services.sh stop

  rpm -Uhv srvadmin-racsvc-*.rpm
  (144524)

* If the default install location of Server Administrator has changed
  during installation, some of the directories in which Server
  Administrator is installed will not be deleted during its removal.
  This issue is related to the default behavior of the RPM engine.
  For example, if installed with the prefix
  "--prefix/opt/dell2/srvadmin2/abc/", the RPM will only delete the
  last directory ("abc") and the remaining directories
  ("/opt/dell2/srvadmin2") are left undeleted.

* When using the command "rpm -e 'rpm -qa | grep srvadmin'" to
  remove Dell OpenManage systems management software, some RPM
  utility versions appear not to perform a full dependency
  check before removal. This can result in some installed RPMs not
  being removed in the proper order. A message such as the following
  may be displayed:

  "WARNING:  srvadmin-rac3-components configuration not performed;
             '/etc/omreg.cfg' is missing or damaged."

  The solution is to use the Dell OpenManage uninstall script,
  "srvadmin-uninstall.sh," that is provided on the CD.
  (153056)

* Dell OpenManage Server Assistant adds a script to the root user's
  ".bash_profile" file that prompts for the installation of Dell
  OpenManage systems management software. This script may interfere
  with remote client applications that authenticate using the root
  user account on the system, but do not have a means to handle user
  prompts. To remedy this limitation, edit the ".bash_profile" file
  and comment out the line: "[ ${SHLVL}...."
  (152668)

* There may be problems uninstalling Server Administrator after an
  unsuccessful upgrade during a manual RPM upgrade. You will
  see the following error message:

  "error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit
  status 1"

  In this case, "NAME" is a feature name, for example "omacore."
  "X.Y.Z-N" is the version and build number of the feature.

  The following are possible solutions to rectify this problem:

  * Attempt to uninstall again. For example, use the following
    command:

    rpm -e srvadmin-NAME-X.Y.Z-N.i386

  * Delete the line "upgrade.relocation=bad" if present in the
    "/etc/omreg.cfg" file and attempt to uninstall again.
    (20927 24290)


* Problems may arise while upgrading Server Administrator in
  some circumstances when the upgrade is attempted and not fully
  successful. This could happen, for instance, when a user is doing a
  manual RPM update on a system requiring an updated OpenIPMI driver
  and that driver is not installed. Some features depending on that
  driver will not install, which is correct. However, older
  installed features that should have been uninstalled, may not be
  uninstalled. This leads to mixed versions of Server
  Administrator being installed on a system. This is not a viable
  installation. This is due to limitations in some versions of the RPM
  utility.

  During the upgrade, the following messages may be displayed:

  * "srvadmin-omhip:
    The required dependency key, "hapi.omilcore.version", in the
    "/etc/omreg.cfg" file is not present."

  * "Installation aborted."

  * "error: %pre(srvadmin-omhip-5.2.0-200.i386) scriptlet failed, exit
     status 1"

  * "error:  install: %pre scriptlet failed (2), skipping
     srvadmin-omhip-5.2.0-200"

  Using the command, "rpm -qa | grep srvadmin", displays the Server
  Administrator features that are installed. The following output may
  be displayed:

  srvadmin-deng-5.2.0-200
  srvadmin-omhip-4.4.0-339
  srvadmin-jre-5.2.0-200
  srvadmin-omacore-5.2.0-200
  srvadmin-cm-5.2.0-200
  srvadmin-omilcore-5.2.0-200
  srvadmin-odf-5.2.0-200

  To fix the problem, perform the following steps:

  1. Delete the older feature. For example, use the following command
     "rpm -e srvadmin-omhip-4.4.0-339"

  2. Resolve the dependency issue. In this case, install the proper
     set of OpenIPMI drivers. Locate the
     "supportscripts" directory on the "Installation and Server
     Management" CD and type "./srvadmin-openipmi.sh install".

  3. Install the uninstalled RPMs from the "custom/srvadmin-base"
     directory on the "Installation and Server Management" CD. For
     example, use the following commands:
     "rpm -ihv srvadmin-hapi-5.2.0-200.i386.rpm"
     "rpm -ihv srvadmin-isvc-5.2.0-200.i386.rpm"
     "rpm -ihv srvadmin-omhip-5.2.0-200.i386.rpm"
  (21892)

* During uninstall, problems may occur that are caused by a previous
  attempt to upgrade Server Administrator that was not successful.
  After all Server Administrator RPMs have been uninstalled, some
  Server Administrator files may not have been deleted. This is due to
  limitations in some versions of the RPM utility.

  To fix this problem:

  1. Log in as "root."
  2. Change directories to the directory Server Administrator was
     installed. For example, "cd /opt". The default directory is
     "/opt".
  3. Delete the Server Administrator directory by using the command:
     "rm -rf dell"
  (25247)

* The "Launch Server Administrator" icon on the X-Windows desktop has
  been provided to launch Server Administrator in the default Web
  browser. The corresponding Web address uses the default parameters
  "localhost" and the port number "1311." Any change in the Server IP
  parameters or a change in the port number for the Server
  Administrator will render the icon/link useless. To re-activate the
  functionality, update the icon file with the correct URL parameters.
  (107307)

######################################################################
HISTORY:
######################################################################
Version 5.1 A00
Release Date: September 2006

######################################################################
RELEASE HIGHLIGHTS - FEATURES
######################################################################

* Added installation support for the following operating system:

  - SUSE(R) Linux Enterprise Server (Version 10) for Intel Extended
    Memory 64 Technology (EM64T)

* Added installation support for the following systems:

   - PowerEdge 840
   - PowerEdge 860
   - PowerEdge 1900
   - PowerVault(TM) NX 1950


######################################################################
RELEASE HIGHLIGHTS - FIXES
######################################################################

N/A

----------------------------------------------------------------------

Version 5.0 A00
Release Date: June 2006

######################################################################
RELEASE HIGHLIGHTS - FEATURES
######################################################################

* Added installation support for the following operating system:

  - SUSE Linux Enterprise Server (Version 9) for Intel Extended
    Memory 64 Technology (EM64T)

* Added installation support for the following systems:

   - PowerEdge 1950
   - PowerEdge 1955
   - PowerEdge 2900
   - PowerEdge 2950

* Added support for Dell Remote Access Controller 5 (DRAC 5)

* Windows Installer Patch (MSP) is not available for installation. You
  can upgrade from Dell OpenManage software version 4.3 to 5.0 through
  a full Microsoft Software Installer (MSI) install.

######################################################################
RELEASE HIGHLIGHTS - FIXES
######################################################################

N/A

----------------------------------------------------------------------
Version 4.5.1 A00
Release Date: April 2006

######################################################################
RELEASE HIGHLIGHTS - FEATURES
######################################################################

* Limited installation support for the following systems on
  Microsoft Windows and Linux operating systems:

  - PowerEdge 1850
  - PowerEdge 2850
  - PowerEdge 6800
  - PowerEdge 6850

* Updated Storage Management Service support to include Serial
  Attached SCSI (SAS) controllers

Note: This release supports only PowerEdge 1850, 2850, 6800, and
6850 systems.

######################################################################
RELEASE HIGHLIGHTS - FIXES
######################################################################

N/A

----------------------------------------------------------------------

Version 4.5 A00
Release Date: October 2005

######################################################################
Release Highlights - Features
######################################################################

* Added installation support for the following operating system:

   - VMWare(R) ESX 2.5.1

* Added installation support for the following systems:

   - PowerEdge 830
   - PowerEdge 850

* From Dell OpenManage systems management software version 4.3
  onwards, added support for Windows upgrade using the Windows
  Installer Patch (MSP) file. MSP files are much smaller in size
  and are available on the Dell Support website at
  "support.dell.com."


######################################################################
Release Highlights - Fixes
######################################################################

N/A

----------------------------------------------------------------------

Version 4.4.1 A00
Release Date: July 2005

######################################################################
Release Highlights - Features
######################################################################

* Added installation support for the following new platforms:
  - PowerEdge 830
  - PowerEdge 850

Note: This release supports only these platforms.

######################################################################
Release Highlights - Fixes
######################################################################

N/A

----------------------------------------------------------------------

Version 4.4 A00
Release Date: May 2005

======================================================================
Release Highlights - Features
======================================================================


* Added installation support for the following operating systems:
   - Windows Server(R) 2003 x64 (Standard and Enterprise editions)
   - Windows Server 2003 SP1
     NOTE: Dell OpenManage version 4.3 does not install on SP1
   - Red Hat Enterprise Linux (version 3) for Intel EM64T
   - Red Hat Enterprise Linux (version 4) for Intel x86
   - Red Hat Enterprise Linux (version 4) for Intel EM64T

* Added service pack file (MSP) support for Windows upgrade from
  version 4.3.  MSP files are much smaller in size and are available
  from the Dell Support website at "support.dell.com."

======================================================================
Release Highlights - Fixes
======================================================================

N/A

----------------------------------------------------------------------

Version 4.3 A00
Release Date: February 2005

======================================================================
Release Highlights - Features
======================================================================

* Added installation support for Dell OpenManage Server Administrator
  Storage Management Service under Microsoft Windows and Red
  Hat Enterprise Linux.

* Leveraged native install technologies for each operating system
  for Server Administrator installs.

* Added Server Update Utility (SUU) 1.0 to the "Dell PowerEdge
  Updates" CD. SUU is a CD-based application for identifying and
  applying updates on your PowerEdge server(s).

======================================================================
Release Highlights - Fixes
======================================================================

N/A

======================================================================

Information in this document is subject to change without notice.
(C) 2004-2007 Dell Inc. All rights reserved.

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

Trademarks used in this text: "Dell," "PowerEdge," "PowerVault," and
"OpenManage" are trademarks of Dell Inc.; "Windows Server,"
"Microsoft" and "Windows" are registered trademarks of Microsoft
Corporation; "Intel" is a registered trademark of Intel Corporation;
"Red Hat" is a registered trademark of Red Hat, Inc; SUSE is a
registered trademark of Novell, Inc. in the United States and other
countries; "VMWare" is a registered trademark of VMWare Inc.

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

Server Administrator uses the OverLIB JavaScript library. This
library can be obtained from "www.bosrup.com".

March 2007

