Dell Lifecycle Controller
USC
Version 1.5.5
Readme
What’s New
Prerequisites for using USC
For Blade systems, iDRAC version 3.4
For Rack and Tower systems, iDRAC version 1.9
Supported Dell Systems and Operating Systems
For the list of Dell systems and operating systems that can be deployed on the target systems, see the
"Lifecycle Controller – Supported Dell Systems and Operating Systems" section in the "Dell Systems Software
Support Matrix" available at support.dell.com/manuals. On the Manuals page, click Software > Systems
Management > Dell OpenManage Releases. Select the relevant OpenManage release version and click Dell
System Software Support Matrix.
Only VMware ESX 4.1 or later operating systems are supported on Intel Xeon processor E7 family.
Installation and Configuration
NA
Open Issues, Limitations, and Resolutions
Fixed Issues/def
Issue 1
Description
The drivers exposed by USC are present in a read-only device labeled OEMDRV, and the device is active for
18 hours. In a Microsoft(r) Windows(r) and Linux environment, the drivers are automatically installed and
no further action is required. In Red Hat Enterprise Linux version 4.8 only, the drivers are not automatically
installed and you have to install the drivers manually after the OS installation has been completed.
Issue 2
Description
In Windows 2003 (32 bit, SBS, and 64 bit), in addition to the device labeled OEMDRV, a floppy drive labeled
FLOPPY that contains drivers is also exposed and remains active for 18 hours.
Issue 3
Description
USC supplies necessary Windows 2003 Server drivers via a temporary, internal USB device that may initially
be assigned the drive letter C: during Windows 2003 Server Setup. Before proceeding, see USC/USC-LCE
User's Guide or the Microsoft support article KB896536 for appropriate installation steps to ensure that
your operating system is properly installed to drive letter C:.
Issue 4
Description
If the boot mode is set to UEFI in BIOS (F2 setup) and if you launch System Services (F10) and Deploy OS,
the installation might fail or you may not be able to boot to the OS after the installation. Always ensure
boot mode is set to BIOS in F2 setup before launching USC and deploying the OS.