Release Notes

• Using the Internet Explorer browser, if you install Server Administrator on a system that includes an underscore in its host name,
you must use the IP address of the target system in the browser URL to launch Server Administrator, as Host names with
underscores are not supported. For example, (assuming Server Administrator is listening on port 1311): https://192.168.2.3:1311.
For more information, see the following article on the: Microsoft website http://support.microsoft.com/kb/312461
• DF152755: The Server Administrator GUI does not respond when the alerts log has many events. If the Alert Log contains
several entries and if you try to navigate to another page, the Server Administrator GUI may take about 30 seconds to display the
content.
• DF172125: Power monitoring probes are displayed on certain systems that do not support power monitoring. On certain systems
that do not support power monitoring, Server Administrator reports the two platform event lters related to a power monitoring
as System Power Probe Warning and System Power Probe Failure. These two lters are not supported on these systems.
That is, you can view and congure these lters, but no action is taken.
• DF185770: Primary User Telephone Number does not accept symbols. On Server Administrator, under Asset Information →
System Information → Primary User Telephone Number conguration allows only alphanumeric characters.
• The selection of default option for the front panel LCD in Server Administrator displays the Model Name whereas the default is a
Service Tag on the physical LCD.
• If Server Administrator does not respond or is locked to your selections on the component tree, perform the following steps:
a. Click Preferences. The Preferences page appears.
b. Click Server Administrator. The items on the front page may respond to your click.
• DF277439: Persistence of Conguration and Log File Changes in VMware ESXi On systems running the VMware ESXi operating
system, the le system is ramdisk. Modications made to the les within the le system are generally not persistent across
reboots, with the exception of designated conguration and log les. These les are updated to the disk periodically and on
system shutdown. If the system is reset without a graceful shutdown before the updated to the designated conguration are
made and before log les are updated to the disk, the changes are lost.
The following is an example of the eect of this behavior:
– On certain systems, the rst time that the thresholds for a probe are changed after Server Administrator is installed; the
current threshold values for that probe are saved as the default threshold values by writing the values to a conguration le.
When Set to Default is performed after the rst change of the thresholds, Server Administrator sets the threshold values to
the values that were saved in the conguration le as the default. If the system running the VMware ESXi operating system
is reset without a graceful shutdown before the changes to the conguration le are updated to the disk, the user- dened
thresholds become the default thresholds.
• DF315853: Some Server Administrator CLI commands, function properly only when run from the elevated console window. It is
recommended that you use the elevated console for running the CLI.
• Due to some limitations, you cannot log on simultaneously to multiple browser instances/tabs using SSO login, as only one
session remains active while the other sessions expire.
• DF489034: Intel TXT conguration fails due to Virtualization technology dependency.
• If the current Virtualization Technology attribute setting is Disabled (Virtualization Technology is part of the Processor Settings
group on the BIOS setup page); the Intel TXT attribute conguration fails on the Server Administrator user interface (System →
Main System Chassis → BIOS → Setup → System Security). To resolve this issue, congure Virtualization technology setting
to Enabled and recongure the Intel TXT attribute, if it is congurable.
• DF549057: When an operating system is installed through USC, the BIOS attributes in Server Administrator are displayed as
read-only. You can edit the BIOS attributes 18 hours after the operating system installation.
Workaround: To enable editing of the Server Administrator BIOS attributes, launch Lifecycle Controller while booting.
• DF552204: On Mozilla Firefox browsers (versions 10, 11 and 12), Server Administrator fails to launch if IPv6 address is used.
This is a known issue. For more information, see https://bugzilla.mozilla.org/show_bug.cgi?id=633001.
• BITS040169: In case of Boot/HDD/UEFI sequence, if they are read-only, then toggle buttons (+ and -) and submit button are
not visible. On the BIOS setup page, dependencies may exist between the various attributes for Bios settings. Setting an
attribute value may change the state of the dependent attributes to non-editable or editable. For example, changing the Boot
Mode to UEFI from the Boot Settings page does not allow you to congure the Boot or Hard-Disk Drive Sequence in the BIOS
Boot Settings page. When the page is non-editable, the toggle buttons on the page allows toggling the order of the boot
sequence. However, settings cannot be congured since Apply button will not available to submit the settings.
• BITS050574: On 11th generation and 12th generation of PowerEdge servers running the Linux OS, the omreport system
summary command displays RAC Command Interface as 7.1.0. "RAC Command Interface" is a DRAC4 RPM and its version is 7.1.
It is installed as a dependent package for iDRAC6 and iDRAC7 Command Interface packages.
• If a new certicate imported to Server Administrator is not active after restarting the Web server, restore the previous certicate.
To restore the previous certicate, do the following:
9