Release Notes

• Mozilla Firefox 6 on Windows XP 32-bit SP3, Windows Server 2003 SP2, Windows Server 2008 SP2, Windows
Server 2008 x64 R2, Windows Vista SP2, Windows 7 x64.
•
Mozilla Firefox 7 on Windows XP 32-bit SP3, Windows Server 2003 SP2, Windows Server 2008 SP2, Windows
Server 2008 x64 R2, Windows Vista SP2, Windows 7 x64.
•
Mozilla Firefox on SLES 10 x64 SP3, SLES 11 x64 SP1, RHEL 5.5 and RHEL 6.0 x64 Native version.
•
Mozilla Firefox 15 on Windows XP 32-bit SP3, Windows Server 2003 SP2, Windows Server 2008 SP2,
Windows Server 2008 x64 R2, Windows Vista SP2, Windows 7 x64.
•
Mozilla Firefox 16 on Windows XP 32-bit SP3, Windows Server 2003 SP2, Windows Server 2008 SP2,
Windows Server 2008 x64 R2, Windows Vista SP2, Windows 7 x64.
What’s New
• OpenSSL upgraded to v1.0.1p.
•
Added support for generating self-signed certificates using SHA2 hash with 2048-bit strength.
Fixes
• Delay in response from the Dell Troubleshooting tool when WS-MAN commands are triggered.
•
Lifecycle Controller version is not displayed on the iDRAC web interface after Lifecycle Controller is updated
using the Remote Enablement (RE) Services.
•
Exporting the server profile using the WS-MAN interface fails.
•
Rolling back the firmware for QLogic NetXtreme II using the WS-MAN interface fails.
•
Power polling using Dell OpenManage Power Center 3.0 fails intermittently.
Important Notes
• To use Virtual Console with Java plug-in, the supported JRE version is 1.6.0_20 or higher.
•
For Remote Enablement auto-discovery, make sure that the user ID on the provisioning server does not contain
any spaces, as iDRAC6 user IDs may not contain spaces. If a user ID containing spaces is configured on the
provisioning server, the auto-discovery process may be successful, but the resulting iDRAC6 account is not
usable.
• The iDRAC6 can be updated using the DOS utility when DOS is booted using PXE. However, the new firmware
image has to be on a local media on the system for this to work properly. Local media can be a RAMDISK, HD,
or a USB key on the server. When the image is stored on non-local devices like a network drive, PXE server
drive, and so on, the iDRAC6 update on multiple systems must be sequenced that is, it should be done one system
after the other. After the first system completes the update, the second system starts the update. After the second
system completes the update, the third system starts the update and so on.
•
On systems running Windows operating systems, the Explorer window(s) for any media does not close
automatically if you remove the media. You must close the window(s) after you remove the media. On systems
running Linux operating systems, the file browser window(s) for any media closes automatically if you remove
the media.
•
iDRAC6 Linux DUPs do not support VMware ESX 4.0 operating systems. If the Linux DUP for iDRAC6 is run
on VMware ESX 4.0, the DUP fails. You can update iDRAC6 using one of the following interfaces:
o
Chassis Management Controller web interface
o
iDRAC6 web interface
o
Remote RACADM