Read me
Table Of Contents
Workaround: To enable editing of the Server Administrator BIOS attributes, launch Lifecycle Controller
while booting.
Issue 38: DF552204: On Mozilla Firefox browsers (versions 10, 11 and 12), Server Administrator fails to
launch if IPv6 address used.
This is a known issue. For more information, see https://bugzilla.mozilla.org/show_bug.cgi?id=633001.
Issues for Server Administrator Running on All Microsoft Windows
Operating Systems
Issue 1: Execute all Server Administrator CLI commands from a 32-bit Windows command prompt. You can
access the 32-bit command prompt by clicking "Start-> Programs-> Accessories-> Command Prompt" or by
clicking "Start-> Run" and then typing "cmd.exe". Attempts to run the CLI commands from the DOS
command "command.com" may generate unpredictable results.
Issue 2: The DSM Server Administrator Connection Service may hang on system startup if both Oracle and
VERITAS Backup Exec are installed on the system. To manually start the DSM Server Administrator
Connection Service on a system running Windows, click "Start-> Programs-> Administrative Tools-> Service",
right-click "DSM Server Administrator Connections Services" and select "Start".
Issue 3: You may not have appropriate privileges on the Server Administrator GUI if:
1. You belong to an Active Directory group that is part of another group.
2. You try to launch Server Administrator using the desktop icon when single sign-on is enabled.
Issue 4 DF551365: Server Administrator does not display the IP Address for Network Adapters that are used
for virtual machines
Description: In a Microsoft Hyper-V environment, the Server Administrator Network page may indicate
network adapters that are connected to a network and display Ethernet statistics but, the IP address is
displayed as 'Unknown'. This is because Hyper-V virtualizes adapters that are bonded to its virtual switch.
The Server Administrator only discovers physical network adapters and displays their IP addresses that are
fully-controlled by the operating system and not by hypervisors.
Issues for Server Administrator Running on Microsoft Windows 2003
Operating Systems
Issue 1: You can ignore the following warning message:
A provider, omprov, has been registered in the WMI namespace, Root\CIMV2\Dell, to use the LocalSystem
account. This account is privileged and the provider may cause a security violation if it does not
impersonate user requests correctly.
This can be ignored as the Managed Object Format file used to register the provider ("omprov") states that
the provider only reads the inventory data; it does not perform any functions on the server that require
user impersonation.