Release Notes

• If Internet Explorer prompts you to Work Oine, Connect, or Try Again, always select Connect or Try Again. Do not select Work
Oine.
• While setting dates in the Asset Information section of the Server Administrator home page, the current time is appended to the date.
While setting dates with the CLI, the appended time is noon.
• On some systems, temperature probe values and settings are only supported for whole degrees, not tenths of a degree. On those
systems, setting a fractional value for the minimum warning temperature threshold results in the set value being rounded o to the next
whole number value. This behavior may cause the minimum warning threshold to have the same value as the minimum failure threshold.
• If you close the browser using the Close button on the browser or log o from the operating system, the Server Administrator session
is not terminated. This session is listed in the Session Management page until the session time out occurs, or DSM SA connection
service is restarted, or the operating system is rebooted.
• If you change the operating system Time Zone to a new time zone, Server Administrator session management does not display the time
in the new time zone specied. Restart Server Administrator to display the accurate time for the time zone in the Session Management
page.
• DF78425: The Server Administrator Auto Recovery feature may execute the congured action before the time interval when the
system is under heavy stress.
The Auto Recovery feature can be set to execute an action (For example, system reboot) to recover a hung system. Since the Auto
Recovery timer is now an application-level timer instead of a kernel-level timer, heavy resource stress on the system may result in an
inaccurate measurement of a short keep alive interval (less than 120 seconds), and the congured action may be triggered. The issue is
more prevalent in systems that have only one CPU with hyper-threading unsupported/disabled or systems that are subjected to
persistent stressful conditions such as, resource depletion and CPU running at 100% usage with signicantly more threads than normal
usage.
The Auto Recovery feature is not enabled by default. If the Auto Recovery feature has been enabled, increase the System Reset Timer
value to at least 120 seconds.
• 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.
Dell EMC OpenManage Release Notes
Version 9.3
9