Dell Systems Build and Update Utility Version 1.6 Manual

######################################################################

DELL(TM) SYSTEMS BUILD AND UPDATE UTILITY 1.6 A01 README

######################################################################

Description:

This Readme provides information about Dell Systems Build and Update
Utility.
NOTE: Dell OpenManage Systems Management software, including Systems
Build and Update Utility, is now available only on the "Dell Systems
Management Tools and Documentation" DVD.

You can use Dell Systems Build and Update Utility to perform the
following operations on your system:

* install operating system

* view hardware details

* perform firmware update

* generate hardware configuration scripts

* create a bootable image for system(s) of choice

For the latest version of this Readme, see the Dell Support website at
"support.dell.com."

######################################################################
TABLE OF CONTENTS
######################################################################

This file contains the following sections:

* Criticality

* Minimum Requirements

* Release Highlights

* Installation

* User Notes

* Known Issues

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

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

3 = Optional

Dell recommends that you review specifics about the update to determine

* Novell(R) SUSE Linux Enterprise Server (SLES) version 10 (SP3) x86_64

if it applies to your system. The update contains changes that impact
only certain configurations, or provides new features that may or may
not apply to your environment.

######################################################################
MINIMUM REQUIREMENTS
######################################################################

This section provides information about the supported systems,operating
systems, and system requirements for Systems Build and Update Utility.

======================================================================
SUPPORTED SYSTEMS
======================================================================
* The following Dell systems are supported on the "Dell Systems Build and
Update Utility" version 1.6:

PowerEdge 1800, PowerEdge 1850, PowerEdge 1855, PowerEdge 1900,
PowerEdge 1950, PowerEdge 1955, PowerEdge 2800, PowerEdge 2850,
PowerEdge 2900, PowerEdge 2950, PowerEdge 2970, PowerEdge 6800,
PowerEdge 6850, PowerEdge 6950, PowerEdge 800, PowerEdge 830,
PowerEdge 840, PowerEdge 850, PowerEdge 860, PowerEdge M600,
PowerEdge M605, PowerEdge M610, PowerEdge M710, PowerEdge M805,
PowerEdge M905, PowerEdge R200, PowerEdge R210, PowerEdge R300,
PowerEdge R410, PowerEdge R510, PowerEdge R610, PowerEdge R710,
PowerEdge R805, PowerEdge R810 , PowerEdge R900, PowerEdge R905,
PowerEdge T110, PowerEdge T300, PowerEdge T310, PowerEdge T410,
PowerEdge T605, PowerEdge T610, PowerEdge T710, PowerVault 110,
PowerEdge R815, PowerEdge R715, PowerEdge M910, PowerEdge R310,
PowerEdge M610x, PowerEdge M710HD, PowerEdge R910, PowerEdge R415,
PowerEdge R515, PowerEdge R210II, PowerEdge T110II, PowerEdge M915,
PowerVault 500,PowerVault 600,PowerVault DL 2000,PowerVault NF110/DP110,
PowerVault NX 1950.

======================================================================
SUPPORTED OPERATING SYSTEMS
======================================================================

The following operating systems are supported:

* Microsoft Windows Server 2003 R2 with SP2
* Microsoft Windows Server 2003 R2, x64 edition with SP2
* Microsoft Windows Server 2008 with SP2
* Microsoft Windows Server 2008, x64 edition with SP2
* Microsoft Windows Server 2008 R2 with SP1
* Microsoft Windows Small Business Server 2011
* Microsoft Windows Essential Business Server 2008
* Red Hat Enterprise Linux version 5 Update 5 for x86
* Red Hat Enterprise Linux version 5 Update 5 for x86_64
* Red Hat Enterprise Linux version 6 for x86_64

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* Novell(R) SUSE LINUX Enterprise Server (SLES) 11 SP1 x86-64

* VMware ESX version - 4.1 U1, 4.0 U3

of the supported systems. Click "System(s) Selection" to

* VMware ESXi Installer and Recovery, version - 4.1 U1, 4.0 U3
* Citrix Xen 5.6 FP1 HDD
* Microsoft Windows Server 2008 R2 Hyper-V x86_64 Edition

======================================================================
SYSTEM REQUIREMENTS
======================================================================

You should have a Dell system with:
* Minimum memory of 512 MB

* DVD drive

NOTE: Hard drive requirements vary by operating system

######################################################################
RELEASE HIGHLIGHTS
######################################################################

* Added support for VMware ESX 4.0 U3
* Added support for VMware ESXi 4.0 U3 Installer and recovery
* Added support for Microsoft Windows Small Business Server 2011
* Added support for Microsoft Windows Server 2008 R2 with SP1
* Added support for Citrix Xen Server 5.6 FP1 HDD

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

1. Insert the "Dell Systems Management Tools and Documentation" DVD
into your system drive and reboot your system. If the system is
supported by the DVD, the "Boot Menu" screen displays. The
"Boot Menu" screen contains the following options to boot your
system:

* "Dell Systems Build and Update Utility"
* "Optical Media (CD/DVD) Check"
* "Skip Optical Media (CD/DVD) Boot - Boot to Hard Drive"

2. When you select the "Dell Systems Build and Update Utility"
option, the "Home" page for "Dell Systems Build and Update
Utility" displays. From the "Home" page, you can access the
Systems Build and Update Utility modules:

* Server Operating System Installation
* Firmware Update
* Hardware Configuration
* View Hardware

"Dell Systems Build and Update Utility" can also be used to
create a bootable image, or export configurations for, any

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

change the system(s) of choice. The current systems is

selected by default.

and Update Utility setup screen does not get applied. The date and time

3. Each of the above modules can be configured independently,
and all the configurations can then be applied in one go.
Alternatively,the Server OS Installation can be done by itself
in one flow.
To configure any of the above modules, click "Configure"
against the module name. Follow the instructions to complete
the configuration. Context-sensitive help is provided on each
page.

4. To apply all configurations, click "Apply/Export Configuration".
Follow the instructions to apply the configurations, and
select "Continue".

5. Insert the operating system CD/DVD media if installing from
CD/DVD, when asked by the system.

6. The system reboots and the unattended operating system
installation continues.

7. When the installation is complete, your system is ready for use.

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

This section provides information to help enhance your experience
with Systems Build and Update Utility.

======================================================================
GENERAL NOTES
======================================================================

* The following languages are supported by Systems Build and Update
Utility:

* English
* French
* German
* Spanish
* Simplified Chinese
* Japanese

* See the "readme.txt" under the folder
"/server_assistant/driver_tool" for all details on the driver
extracting utility.

* For operating systems such as ESX and Windows 2008 Server, for
which the installation is not fully-automated, the native Graphical
User Installation tool provided by the operating system installation
media is used. Hence setting date and time zone in the Systems Build

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

will have to be set manually once the operating system is installed.

* If the Systems Build and Update Utility GUI disappear and a blank

wait for the devices to be listed, or a popup informing that no devices

screen is displayed, restart your system. This issue occurs if you
right-click to open a new browser window (from the "Quick Reference
Guide" window) and select "Quit" from the "File" menu.

* In order to use the RAID configuration feature of Systems Build and
Update Utility to configure RAID and install the operating system,
the "Fast Initialization" parameter of the RAID controller must be
set to "ON." This setting is the factory default of all RAID
controllers.

* Do not insert or remove any hot-swappable drives until the
operating system is completely installed while using the "Systems
Build and Update Utility". The results may be unpredictable and the
installation may fail.

* Replication is supported on systems with multiple controllers,
provided the controllers are in an initialized state. This is
applicable to both master and target systems.

* If you configure RAID manually and use Systems Build and Update
Utility to install an operating system on a master system, then you
need to manually configure RAID on the target system as well.

* Use local accounts for creating the SMB share on Windows on which
the RPMs will reside for the network download feature.

* Systems Build and Update Utility does not support the installation
of tape or Fibre Channel drivers with the operating system
installation. You can download the drivers for these devices from the
Dell Systems Service and Diagnostics Tools on the "Dell Systems
Management Tools and Documentation" DVD or from the Dell Support
website at "support.dell.com".

* The "Keyboard Type" locale option offered for a keyboard layout on
the systems Build and Update Utility home page is for the Systems
Build and Update Utility screens navigation only. The selected
keyboard layout setting is not passed to the installed Operating
System.

Even after you select any language other than English under "Select
Language" and "Keyboard Type" on the "Home" page, the input language
will be English. That is, the text you enter in the text fields in
the GUI will appear in English.

* Do not use the Dell Remote Access Controller (DRAC) virtual media
to run "Firmware Update" on the system. This procedure breaks the
virtual media connection, causing the firmware update procedure to
fail.

* In Firmware Update page, if user selects "Refresh USB devices", user should

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

could be found, before clicking any other links on the page.

* USB keys formatted with NT File System (NTFS) or file allocation
table (FAT16) are not supported.

* Any network or Windows share or CD/DVD that you use an input to the
Repository must not contain any extra file or folder that is not part
of the Server Update Utility (SUU) content.

* When you select the "No Change" option for Trusted Platform Module
(TPM) Activation, under Boot sequence and security tab, the TPM
activation token will not be saved to the ".ini" file.

* "Digitally sign communications" enabled Windows share on a system
running on Windows cannot be accessed. To access the share, disable
this feature on the Windows system.

* When you insert multiple USB keys into your system, Systems Build
and Update Utility uses the last inserted USB key which has a
repository that is applicable to the platform to which your system
belongs and is compatible with the Systems Build and Update Utility
repository.

* The selections on Set the Date and Time page in SOI will show
default values (not the earlier selected values) when the user
re-visits the page by clicking Back or Edit. The user selected
values will be stored internally and will be applied to the
system when user opts to apply.

* The Advanced Mode allows you to specify the size of the virtual disk.
The specified value will be used while creating RAID and will not be
validated against the existing disks on the system.
* OS Installation: Windows Server 2008 (32 and 64 bit), VMware ESX apply
options screen will not have OS ISO location specified as these
installation require OS ISO at runtime when OS is getting installed.
SBUU will boot to hard disk and then ask for OS ISO DVD and then user
has to supply it. These installations do not work on network. They
are for standalone servers.

* When the User selects the Embedded NIC and/or Redundant Memory
token in the BIOS page in the Hardware Config screen, the options
shown for this token are a superset. If the user selects an option
which is not supported in the current system, applying Hardware
Scripts will fail and if Exit on Failure option is selected, the
deploy operation will halt.

* When the User selects to use Operating System ISO's from network
location and during copy operation, if the network is disconnected
for a while and then reconnected, in case of NFS shares, it will
resume the copy operation but, in case of SMB/Windows share, it will
not resume the copy operation. Disconnection on a SMB/Windows share
will result in an error and user has to reboot and re-run the
operation.

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* The values configured in the multi-sys-config.csv file will be

applied only during execution. Only those options are applied that
are shown during configuration time. However, options that are not
shown during configuration, but are part of multi-sys-config.csv file
will be ignored. Note: If there is any overlap in the settings
between Configuration GUI and multi-sys-config.csv file, then
settings in multi-sys-config.csv file will override those made in
the GUI.

* The installation times for different versions of the Windows Server
2008 operating system will vary considerably. This is because of the
differences in the software and drivers utilized in different
versions of the Windows Server 2008 operating systems and the
capabilities of the installation platform. On the "Installing
Windows" screen, the "Completing installation" step, where the
drivers are installed, may take considerable time to complete.

* If you configure the BIOS or iDRAC6 entry with "Setup Password
Override" checkbox under "Power" Section and then you Export the
configurations and then import the same configuration and view/Edit
the imported configuration.
User will see the 'Setup Password Override' checkbox is not checked.

* Uncertified array disks, if present in the system, are displayed in the
SBUU RAID configuration GUI but are not used when creating RAID using
configuration scripts.

* Inactive disks, if present in the system, are displayed in the
SBUU RAID configuration GUI but are not used when creating RAID using
configuration scripts.

* The options shown in SBUU for BIOS tokens in the BIOS page in the
Hardware Config screen are a superset. The default values do not
reflect the current status of the tokens. If the user selects an
option which is not supported in the current system, applying
Hardware Scripts will fail. User should select a value that
is applicable on the current system.

======================================================================
USER NOTES FOR WINDOWS OPERATING SYSTEMS
======================================================================
* If you are using the SBUU iso image downloaded from the support site at
support.dell.com and installing Microsoft Windows 2008, you need to
download Windows OS Install Support Pack from the support site. Create
your own optical media from the Windows OS Install Support pack and
make it available to SBUU when prompted.

* During Windows installation, the system will automatically log on
to finish the post-installation tasks and will then automatically log
out. It is recommended that you do not perform any task until the
system has automatically logged out. Installation might end
abnormally if the installation process is interrupted.

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* If you enable "Console Redirection":

* A dialog box displays that an Expanded Memory Support (EMS)

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

connection has been discovered during the operating system
installation.
* You enter the organization name and computer name, an error
message displays that "unattend.txt" is incomplete and
prompts you to enter the username. Enter the username to
continue with the unattended setup operation.

* In the Advanced "Enter OS Information" screen, enter all IP
addresses for the "Trap Destination" field separated by commas. Do
not enter trailing commas, or the installation will stop when the
Windows Setup program runs.

* If you install Windows Server 2003 Web Edition using Dell Systems
Build and Update Utility Internet Information Server (IIS) is
installed by default. You should choose NT File System (NTFS) to
ensure all of IIS components install correctly.

* If your platform supports Windows HPC 2008 or Windows HPC 2008 R2
editions, select Windows 2008 (64 bit) and Windows 2008 R2 (64 bit)
respectively on the "Configure Server OS Installation" page, and
use the appropriate Windows media when prompted.

To find if your platform supports these Windows editions, see
Dell Support website at support.dell.com

* To install the Windows 2008 R2 Operating System, you must select the
Windows 2008 R2 SP1 option button to proceed.

* For Windows 2008 flavors, you cannot set the time zone option using
SBUU. This is because Microsoft does not support timezone entry in
Windows Server 2008. For more information, see
http://support.microsoft.com/kb/935369

======================================================================
USER NOTES FOR TOOL TO MAKE BOOTABLE USB (make_bootable_usb.py)
======================================================================
* The following commands/rpm should be installed for the tool to work:
udevinfo,mtools,parted (minimum version required is 1.6.25.1),
grub-install (grub) and lsusb

* By default, the boot to hard disk option (HDD) is configured to boot to
second partition of the first hard disk of primary controller master
(hd0,1). If the OS is installed in other disk/paritions the GRUB boot
entry should be edited accordingly. Please check GRUB manual for further
details

======================================================================
USER NOTES FOR RED HAT ENTERPRISE LINUX OPERATING SYSTEMS

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* At least 14.1 GB disk space is required to install Red Hat Enterprise

* Try burning the media at slower speeds

Linux.

* If you use the "Download RPMs from Network" feature, the RPMs are
downloaded to the partition called "/home." The recommended size for
this partition is 3 GB plus the size of the RPMs you want to update.
All downloaded RPMs are installed during the post install phase of
the Red Hat Enterprise Linux installer.

* Entering a double quote character (") in the "Root Password" field
of the Red Hat Enterprise Linux installation will result in denial
of access to the root "log in."

* Systems Build and Update Utility limits the maximum block device
size on a Linux system to 8 TB.

* A network download of RPMs requires that the target system have a
DHCP IP address and that the system is connected to a network.

* While configuring the hard drive on a system to install a Red Hat
Enterprise Linux operating system, if the hard drive space on your
system is used completely and the range specified in the GUI against
the "swap" partition is the same (for example [1024 -1024] MB), the
scroll bar remains to the left side.

* After selecting languages using "Select Language" option (ex: Chinese)
in SBUU for installing a Red Hat Linux operation system, the user has
to change run level using "init 5" command instead of "startx" to get \
the selected language applied.

======================================================================
USER NOTES ON PREPARING LINUX OS INSTALLATION MEDIA
======================================================================

Systems Build and Update Utility performs a media check on the Linux
operating system media that is provided during installation. This is
so that you do not copy damaged media that will cause your operating
system installation to fail. This is a default action performed by
SBUU, and you cannot disable it.

It has been observed that certain CD burning software fail to prepare
media to pass the media check.

Dell recommends that you use the optical media obtained from the
operating system vendor to install Red Hat Enterprise Linux or SUSE
Linux operating systems using Systems Build and Update Utility.

If it is necessary to burn the media using CD burning software,
ensure that you:

* Obtain the ISO image file of the media from known sources.

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* Use the "Disk at Once" or a similar option.

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

* Close the session.
======================================================================
USER NOTES FOR VMware ESX
======================================================================

* For details on the hardware support and ESX build number, see
"www.dell.com/vmware" on the Dell Support website at
"support.dell.com." Also, see the "Dell OpenManage Server
Administrator Compatibility Guide" and the "Dell Systems Software
Support Matrix."

* On a system with Embedded SD card slot, if ESXi Installer and recovery OS is
supported, it is shown in the operating system list for all controllers,
independant of whether the SD card is enabled or disabled in the BIOS.

======================================================================
USER NOTES ON Dell Utility Parition installation
======================================================================
Utility Partition will not be created if the system on which you are trying to
install does not support a Utility Partition.

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

The following subsections list the known issues with this release of
Systems Build and Update Utility.

* Do not export configuration files from PE to SC servers and
vice-versa since this is not supported.

* On Dell PowerEdge systems with internal USB, BIOS setting
configuration for internal USB Port is possible only if User
Accessible/external (UA) USB ports are set to "All Ports On".
If UA USB ports are not set to "All Ports On" and user tries to
configure BIOS setting for internal USB Port using Server
Administrator GUI or CLI, the configuration will appear to be
successful but the changes will not take effect on next reboot.
If UA USB ports settings are changed from "All Ports On" to "All
Ports Off" or "Only Back Ports On", the USB will be automatically
set to "Off" during the next reboot.

* System Build and Update Utility (SBUU) will not boot through DVD under
BIOS in UEFI mode.

* If you return to a page (including Home Page) directly from the operating
system installation page, it may take some time for the new page to load.

======================================================================
KNOWN ISSUES ACROSS ALL OPERATING SYSTEMS

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* Systems Build and Update Utility does not support RAID

array disk is removed, the firmware utility may indicate the

configuration on any system with a SAS 5/iR or SAS 6/iR controller
connected to one hard drive. To install Systems Build and Update
Utility on a system with the SAS 5/iR or SAS 6/iR controller, ensure
at least two hard drives are connected.

* Systems Build and Update Utility does not support RAID
Configuration on any system with a SATA 2S controller connected to
one hard drive. To install Systems Build and Update Utility on a
system with the SATA 2S controller, set the hard drive configuration
to "Native Mode" in the BIOS setup or configure RAID using the
"Ctrl+A" option.

* If a USB flash device is connected to the system, Systems Build and
Update Utility may fail to install the operating system. To resolve
the issue, perform one of the following actions:

- Remove the USB flash device.

- In the BIOS setup, under "Boot Order," move the "USB Device"
selection to the end of the list.

* The "View Hardware" feature in Systems Build and Update Utility
does not provide information on devices that are connected to the
chassis. The current listing of devices is not complete and does not
include devices such as Fibre Channel cards and Dell Remote Access
Controller 5 (DRAC 5).

* On PE1800 the "view hardware" feature in Systems Build And Updates
Utility does not show the CERC SATA 2S device when it is set to ATA
mode. This is due to the current limitation of CERC SATA 2S; it has
the same PCI device ID for both ATA and RAID mode.

* Use of localized special characters might cause the Systems Build
and Update Utility GUI to freeze intermittently.

* If there are multiple SAS or RAID controllers on the system,
Systems Build and Update Utility will always use the controller
listed first in the BIOS boot order list. If you want to use a
particular controller for the operating system, you must go to the
BIOS setup (F2 on boot) and set up the given controller as the first
boot device.

* Systems Build and Update Utility does not support the configuration
of partitions or the installation of operating systems on systems
with PERC 2 and PERC 3 series controllers or any type of
Fibre Channel storage adapter.

* It is not recommended to start the System Build and Update Utility
if any of the virtual disks are in a non-optimal state. Use the RAID
controller's firmware utility (Ctrl+A or Ctrl+M or Ctrl+R or
Ctrl+C during boot) to reset the RAID controller's state. If an

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

configuration has changed. Accepting these changes on the command

line may not be enough; enter the firmware utility and reset the

to your system. Ensure that you disconnect the external storage

controller.

* On CERC ATA or CERC SATA RAID controller cards, disks that appear
in "Legacy" mode will not be available for RAID configuration in
Systems Build And Updates Utility. If you wish to use any disk that
is in "Legacy" mode as part of a RAID container, you need to use
the RAID controller firmware utility to initialize these disks. Likewise,
if all disks are in "Legacy" mode, then Systems Build And Updates Utility
may fail to configure RAID on the controller.

* The Server Setup program might fail if it runs when scrubbing is
active on a RAID virtual disk.

* Systems Build and Update Utility does not identify the boot device
when PERC 4DC controller is in cluster mode and the adapter's BIOS is
disabled. This will put Systems Build and Update Utility in an
infinite "Write Disk signature" and reboot loop. Use Systems Build
and Update Utility to install the operating system on PERC in a
non-cluster mode.

* Systems Build and Update Utility cannot detect the correct slot
number of PCI slots containing Adaptec RAID controllers. The message
"Unknown Slot Number" is displayed.

* On systems with low memory (less than 256 MB) and more than one
RAID controller, Systems Build and Update Utility may fail during
RAID configuration. Install the additional adapters after the
operating system has been installed on the first adapter.

* When using the Custom install script feature, commands which do
not return cause the system to stop responding during booting of Red
Hat Enterprise Linux or while registering components on Windows
installations.

* On DELL PERC/SAS RAID controller cards, disks that appear in "Foreign"
state will not be available for OS installation in non-RAID mode. If
all disks are in "Foreign" state, Systems Build and Update Utility
may fail to install OS on the controller in non-RAID mode.

* When you use Systems Build and Update Utility with a
keyboard-video-monitor (KVM) switch, the GUI may not display due to
incompatibility with the Server Interface PODs (SIPs) used. To view
the GUI, connect your monitor directly to your system or change the
SIP.

* To ensure the successful installation of an Operating System using
Server OS Installation, disable the DRAC/iDRAC Virtual Flash.

* When you are using the Server Operating System Installation module
in Systems Build and Update Utility to install an operating system,
the installation may fail if an external storage device is connected

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

device before you begin installing the operating system.

* The Edit option shown on the SBUU homepage after Hardware

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

Configuration section is configured, will allow the user only to view
all the created Virtual Disks and user is allowed to add or remove
Virtual Disks. User will not be allowed to edit the settings of
already configured Virtual Disk.

* When an external storage enclosure is connected to the storage
controller, RAID can be configured on that controller using SBUU.
But, SBUU will not support installing an Operating System on the
Virtual Disk which is created on the controller connecting to an
external storage enclosure.

* iDRAC users created through SBUU do not get enabled. To enable
these users, user will have to go to DRAC (DRAC5 or iDRAC) GUI and
set the user privilege level to desired level (Administrator,
Operator etc).

* When you create usernames for DRAC using SBUU, ensure that they do not
contain the "&" character. However, you can use "&" to create usernames in
DRAC (DRAC5 or iDRAC) GUI.

* When you insert multiple USB keys into your system, Systems Build and
Update Utility uses the last inserted USB key which has a repository
that is applicable to the platform to which your system belongs and
is compatible with the Systems Build and Update Utility repository.

* Systems Build and Updates Utility will not allow you to delete any single
virtual disk if the last virtual disk has utilized full space in the selected
disk group. It will automatically select and delete all the virtual disks in
the selected disk group.

* BMC DUPs cannot be updated from SBUU, SBUU deployment will fail if you select
this DUP in the firmware update screen. Users should update the firmware
after installing the OS.

======================================================================
KNOWN ISSUES FOR LINUX OPERATING SYSTEMS
======================================================================

When you are using the "Dell Systems Management Tools and
Documentation" DVD through DRAC/iDRAC, Systems Build and Update Utility may
not eject the DVD before asking you to insert the operating system
media. This displays the error message, "Invalid media inserted."

To correct this, unmount the DVD from DRAC/iDRAC; then insert the correct
operating system media and mount the drive again.

======================================================================
KNOWN ISSUES FOR RED HAT ENTERPRISE LINUX OPERATING SYSTEMS

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

* When using the "Dell PowerEdge Installation and Server Management"

To workaround the issue for the PowerEdge R805, you can:

CD/DVD media for new RAID configurations, installation
of the Red Hat Enterprise Linux operating system may fail if both the
USB CD and USB floppy are connected. To avoid the installation
failure, remove the USB floppy connection before rebooting the system
with the CD/DVD for the installation process.

* Installation of Red Hat Enterprise Linux (version 4) operating
system is not supported on any system having the following
controllers:

* CERC ATA 4ch

NOTE: In the above case, the option to install Red Hat Enterprise
Linux (version 4) will not be presented in the "Select Operating
Systems" page.

* Installation of Red Hat Enterprise Linux (all versions) operating
system is not supported on any system having the following
controllers:

* Promise RAID
* CERC SATA 2S in RAID mode

NOTE: In the above cases, option to install Red Hat Enterprise
Linux operating system will not be presented in the "Select
Operating Systems" page.

* Systems Build and Update Utility does not support Non RAID (Volume)
mode on S100/S300 SWRAID controllers.
======================================================================
KNOWN ISSUES FOR NOVELL SLES10/SLES11 OPERATING SYSTEMS
======================================================================

* The Novell SLES 10 / SLES 11 operating system installation may fail
on systems equipped with multiple RAID and/or SCSI controllers,
whether installed on the system board or in PCI slots. This failure
may occur when using Server Setup or performing a manual
installation. When two or more RAID or SCSI controllers are
present, install Novell SLES 10 / SLES 11 with only one configured
RAID or SCSI controller. Configure the other controllers after you
install the Novell SLES 10 / SLES 11 operating system.

* When certain cards, notably Qlogic or Emulex fiber channel cards,
are present in PowerEdge R805 and PowerEdge M905 systems, SLES 11
(and other linux kernels later than 2.6.27) may cause the system
to reboot when drivers for those cards are loaded.

The issue occurs because the linux kernel changes the memory address
assignments to certain add-on PCI devices such that they overlap the
second I/O APIC interrupt controller in the system.

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

- Set the Optical Drive Controller (under Integrated Devices) to

On in system setup.

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

This changes the system resource assignments such that this issue
does not occur.

If this workaround fails, you can:

- Add the kernel parameter acpi=noirq to the kernel command line
to prevent the linux kernel from using the I/O APIC interrupt
controllers.

To workaround the issue for the PowerEdge M905, you can:

- Add the kernel parameter acpi=noirq to the kernel command line
to prevent the linux kernel from using the I/O APIC interrupt
controllers.

A fix for this would be available in a future update BIOS revisions
for SLES 11.

* On installing Novell SLES11 SP1, if the login Window is not gnome,
reboot the system to restore gnome as the Window manager

======================================================================
KNOWN ISSUE(S) FOR VMware ESX 4.0 OPERATING SYSTEM
======================================================================

* If you choose to install VMware ESX 4.x operating system, the
Dell Utility Partition is deleted during the operating system
installation.

* When installing ESXi flash version (using recovery media), RAID virtual
disks can not be created on the vFlash device itself. Virtual Disks can be
created only on hard drives.

======================================================================
KNOWN ISSUE(S) FOR FIRMWARE UPDATE FEATURE
======================================================================
* The "View/Edit/Reset" becomes enabled for the "Firmware Update"
even if user does not select any components for update.
When user visits the "Firmware Update", specifies the Server Update
Utility ( repository) location either using the DVD or NFS or SMB
or USB media, views the comparison report. If the server comparison
report does not have any updatable components, user cannot configure
anything in this page and user returns to the home page.
However since the user configured the repository, the
"View/Edit/Reset" option on the home page will be enabled irrespective
of user's configuration of the firmware updates.

* In the "Repository Selection" page, if you had selected NFS or SMB before
clicking "Refresh USB Devices" and no USB devices are found, then do one of
the following ­ * Insert a USB device and click "Refresh USB devices" again
* Select any of the other options and proceed

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

Notes on using syscfg and racadm commands

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

When a system is booted from Systems Build and Update Utility, the /opt
filesystem is linked to /tmp filesystem. Some functionality of syscfg and
racadm use /opt extensively.
If user mounts any other device (like a USB drive) to /tmp and issues
racadm or syscfg commands, the files in /opt will no longer be visible and the
commands will fail.

User is advised to create a temporary directory under under /mnt and mount
the USB devices there instead of mounting to /tmp

######################################################################
CORRECTED PROBLEMS
######################################################################
The following problems were reported in the 1.6 A00 version and have been
corrected in this release:

DF459993: Microsoft Windows Server 2008 installation fails on SBUU.
When SBUU starts applying the Operating System deploy configuration
on Microsoft Windows Server 2008, it fails with an unknown error.

DF457439 – The firmware/Driver Information for Controller S300
is older than the required driver version.
The Firmware/Driver Information for Controller S300 displays
the error "Driver version is out of date."

######################################################################

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

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

Trademarks used in this text: "Dell," "PowerVault", "PowerEdge," and
"Dell OpenManage" are trademarks of Dell Inc.; "Microsoft" and
"Windows" and "Windows Server" are either trademarks or registered
trademarks of Microsoft Corporation; "SUSE", "NetWare" are registered
trademarks of Novell, Inc.; "Intel" is a registered trademark of
Intel Corporation; "Red Hat" and "Red Hat Enterprise Linux" are
registered trademark of Red Hat, Inc; "VMware" is a registered
trademark and "ESX Server" is a trademark of VMware, Inc; Conexant is
a registered trademark of Conexant 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.

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]

2011 - 03 Rev. A01

file:///T|/htdocs/SOFTWARE/smsbu/1_6/EN/readme/SBU_read.txt[10/23/2012 10:51:41 AM]