Release Notes
Issues for Server Administrator Web Server running on all Linux Operating Systems
•
DF275424 and DF332775: Domain users unable to login to Windows MN from Linux Web
Server.
o
Negotiate authentication is not supported while remotely managing a
Windows-based managed node from a Linux-based Server Administrator
Web server. If you run the Server Administrator Web server on a Linux based
operating system and try to manage a remote Windows managed system as
domain user, a "login failed" message is displayed.
o
You can manage a Windows/Linux- based managed system remotely from a
Windows-based Server Administrator Web server.
Issues for Server Administrator Running on All Supported Operating Systems
•
On Dell PowerEdge T110 II systems, the following Server Administrator bios settings are
not consistent with the F2 bios setup settings:
o
Watchdog timer: Server Administrator displays the option as disabled, but F2
bios allows to change the setting.
o
Embedded Video Controller: Server Administrator provides options to enable
or disable, but in F2 bios the option is greyed out.
o
TPM Security: Server Administrator does not allow to change the settings, but
F2 bios allows to change the settings.
o
System Profile State: Server Administrator does not allow to make changes,
but F2 bios allows to make the changes.
o
Memory Testing: Server Administrator does not support this feature, but F2
bios supports this feature.
o
SRIOV option: Server Administrator does not display this information, but F2
bios displays this feature.
•
Due to non-availability of resources, inventory collector may terminate unexpectedly and
restart. If this occurs, the folder "C:\Temp\invcol" may be left as an artifact. The presence
of this folder does not affect the functionality of the inventory collection. The folder can
be deleted if required.
•
After installing Server Administrator from the command prompt, typing an "omreport" or
mconfig" command from the same prompt can cause an error. Open a new command
prompt window and type commands.
•
If the command log page in the Server Administrator GUI displays an error message
indicating that the XML is malformed, you must clear the command log from the CLI using
the "omconfig system cmdlog action=clear" command
•
After a "Reset to Defaults" operation of the Integrated Remote Access Controller, the first
user configuration operation fails if it is a single-user configuration item (such as enabling
or disabling a user or changing user name). Always change a combination of two-user
configuration items (such as enabling or disabling a user and changing user name)
concurrently during your first configuration operation.
•
While typing the command "omreport system version -outc <filename>",ensure that you
specify an absolute path name for the output file; else, the output file is empty. For
example, c:\out.txt.
•
Typing "omreport system esmlog/alertlog/cmdlog -fmt tbl" command on the CLI can
result in XML parsing errors if the size of the log is very large. Use the GUI or the "omreport
system esmlog/alertlog/cmdlog" CLI command to view the contents of the log.
•
For complex "omconfig" CLI commands that contain multiple set commands in one
command line, the CLI may report a success status for the command even if a part of the
command failed. To avoid this issue, run only one command per command line. The
current settings can be confirmed by performing the corresponding "omreport" command.