Release Notes

• On PowerEdge systems with cabled power supply units installed (that is, PSUs which do not provide PMBus support),
power values may still be displayed in the iDRAC7 web and LCD interfaces. Due to lack of PMBus support in the
PSUs, the power values displayed on the GUI pages, including the Overview > Hardware > Front Panel page, are
not correct.
• Due to the independent nature of the alert processes (e-mail, SMTP, remote syslog), when changing the licenses
that affect alert features (example, email alerts for Express or remote syslog for Enterprise) there is no guarantee
of the timing of the features being activated or deactivated when the license changes.
• In the iDRAC Web interface, when the System Inventory page is accessed for the first time, it takes up to two
minutes for the inventory data to be collected. After the data collection is complete, refresh the page to display
the inventory data.
• For the unique auto-generated certificates to work, you must make sure to synchronize the iDRAC time with the
management station’s time to avoid certificate related issues. If the time is not synchronized, issues such as
server certificate expiration may be seen. If this issue occurs, re-synchronize iDRAC time with the management
station’s time and reboot iDRAC.
• On a Linux system, if you click on a menu item and it remains open, the Ctrl + Alt + L keystroke sent from iDRAC to
the host system does not lock the host system. The behavior is the same as using a local keyboard.
• The default time zone value is US Central Time. To make sure Single Sign-On (SSO) and Directory Service TFA
(smart card) continue to work properly, the iDRAC time zone must match the time zone where iDRAC is located,
assuming Active Directory server's time zone is already configured to match the Active Directory's location. For
example, if Active Directory server is located at US Eastern time zone and iDRAC is located at US Pacific time zone,
Active Directory server has to be configured as US Eastern time zone (this is Active Directory server configuration
and is normally configured), and iDRAC must be configured as US Pacific time zone. For more information to
configure the time zone, see the iDRAC7 User's Guide.
• If the management station is using MAC operating system, it takes more time to launch the Virtual Console due to
the following DNS search issue: http://www.eigenspace.org/2011/07/fixing-osx-lion-dns-search-domains/
• From iDRAC7 1.30.30 onwards, if you configure iDRAC using XML Import, the "user password is changed" messages
are seen in the Life Cycle log. An entry is seen for all local user index that are not configured in XML file and have
default values.
• The help page for the backup and restore feature does not provide the correct share name. See the Web Services
Interface Guide available at support.dell.com/manuals for the correct share name.
iDRAC7 - Limitations
• If floppy emulation is enabled when a bootable USB key is mounted as a Virtual Media from the Virtual Console and
if you try to delete any file from the mounted USB key (floppy), the blue screen appears immediately.
• Web server session time-out is not exact. It is either 10% more or 15 seconds more, whichever is greater.
• WinRM and RACADM commands may become unresponsive during BIOS update or when setting BIOS, NIC, or RAID
attributes through Lifecycle Controller.
• Using WS-MAN and running up to 256 jobs through the job scheduler may lead to reduced iDRAC7 performance.
• If invalid credentials are used for the maximum login attempts, the IP is blocked for the duration of the IP Blocking
Penalty Time and a message is not displayed.
• If Internet Explorer (IE) 64-bit browser is used to log in to iDRAC7 Web interface and when viewing the power
usage graph, the X and Y axis labels appear too small to read. This is a known limitation for IE 64-bit only. The
labels appear correctly in IE 32-bit browser.