Read me

• To log on to Server Administrator using the VMware ESX 4.1 operating system as server administrator,
restart the DSM SA Connection Service.
• To log on to the Remote Node using the VMware ESX 4.1 operating system as Remote Enablement
Agent, wait for about five minutes for the ‘sfcbd’ to add permission for the new user.
Issue 2 (DF354388): Remote Server Administrator Web Server connection to managed node hangs, if a
redundant virtual disk containing syslog dumps fails.
If you configure the syslog to store logs on a remote virtual disc (VD), and remove the remote VD without
reconfiguring the syslog to a valid location, the Server Administrator web server screen stops responding.
To continue using the Server Administrator Web server, restart the management services on the managed
node.
Issue 3 (DF550588): On ESXi 5.0 U1 operating system, the performance of Server Administrator is slow.
On ESXi 5.0 U1 operating system, the Server Administrator is slow. VMware has reported this as a known
issue. For more information, refer to the Knowledge Base article at - http://kb.vmware.com/kb/2016538
Issues for Server Administrator Web Server running on all Linux
Operating Systems
Issue 1 (DF275424, DF332775): Domain users unable to log in to Windows MN from Linux Web Server.
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.
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
Issue 1: 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.
Issue 2: After installing Server Administrator from the command prompt, typing an "omreport" or
"omconfig" command from the same prompt can cause an error. Open a new command prompt window
and type commands.
Issue 3: 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.