Read me

Issue 3
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 4
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 the 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 5
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.
Issue 6
Description
You may see a no optical device found error if you have a bad DVD/CD in the optical drive. This error does
not mean that there are no optical devices on the system. If you remove the bad media, then this error is
resolved.
Issue 7
Description
For Red Hat Enterprise Linux version 4.8 operating system, you may need to install kernel source before
installing the drivers present in OEMDRV.
Issue 8
Description
For RAID Configuration and Platform Updates, PERC 6.1 Firmware or later is required.
Issue 9
Description
To maintain compatibility with other iDRAC configuration tools, it is recommended that only digits (0-9),
alphanumeric (a-z, A-Z) and hyphen (-) characters be used when entering a "Name" or "Password" string.
When entering a "Domain Name", such as 'x123.com', a period (.) character is also permissible.
Issue 10
Description
When attempting a Platform Update via an FTP server, specifying a valid proxy server but selecting an
invalid proxy type causes USC to halt for a long period (possibly over 30 minutes) before it returns to
normal operation.