Release Notes

Fixes
The following issues were reported in earlier releases of Server Administrator and have been
corrected in this release:
BITS165339: IPS: 10892.mib contains a few significant SNMP validator errors
BITS145720: App Crash (Xalan-c.dll crash) after successful WMI query of OMSA & Disney
classes concurrently
BITS158302: Enhancements to Single SIgn On Desktop Icon Launch BITS164226
BITS162142: 13EST:ASR0000-The watchdog timer expired logs 3 times shown in LC and SEL
Logs
BITS167011: OMSA login not working for ESXi5.5 U2
Important Notes
*BITS169696: When Server Administrator is installed on systems running the Red Hat Enterprise
Linux 7 OS, the OS may stop responding after Server Administrator services are started. This issue
is observed when Server Administrator services are started after the installation or when Server
Administrator services are started, by default after a system restart. However, this issue is
observed only on few servers.
Notes for Server Administrator
On 12G systems with iDRAC7 1.30.30 and later versions, you can set the Platform Event
Destination as IPv4, IPv6, or FQDN.
Notes for Instrumentation Service
On 11G systems, if conflicting BIOS settings exist while configuring BIOS setup options
through Server Administrator, the update attempt may fail at system reboot and
none of the BIOS setup options may be updated.
For example, when you configure Embedded SATA Controller to RAID and Boot Mode
to
UEFI simultaneously (UEFI does not support RAID option), the conflict prevents the
BIOS
configuration updates (at system reboot).
On certain systems, user-defined thresholds set under Server Administrator become
the
default thresholds after uninstalling Server Administrator.
If you change the threshold value of a probe on certain systems, running Server
Administrator, and then uninstall Server Administrator, the changed threshold
value
becomes the default threshold value.
While modifying the warning threshold settings, the values are stored in the firmware as
discrete integer values and scaled for display. If the modified value is not a discrete
integer,
it may change when saved.
Fan redundancy can have the following states:
Fully Redundant - The sensors display this status if all the fans in the system are present
and are in a non-failure state.
Redundancy Lost - The sensors display this status whenever any system fan fails or is
removed from the chassis.
If a system with memory redundancy enabled enters a "redundancy lost" state, it may
not
be clear which memory module caused it. If you cannot determine which DIMM
to
replace, see the "switch to spare memory detected" log entry in the ESM system log
to find the memory module that failed.
If you run Server Administrator when the system is in "OS Install Mode", it may report
the
memory incorrectly. To avoid this issue, you must disable "OS Install Mode" before
running the application.
If you have to uninstall and reinstall the operating system SNMP service, then reinstall