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
######################################################################
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.
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:
======================================================================
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
* 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
* 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
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
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
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
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.