Release Notes

Table Of Contents

* If Server Administrator is being installed or uninstalled on a system where the Web download version of Server Diagnostics

(version 2.x) or Server Update Utility is running, the Windows Installer service may display a message stating that specific

files needed by Server Administrator are in use by diagnostics or by the Server Update Utility. Click "Ignore" and continue.

(62159)

* On the Windows 2008 SP2 SBS operating system, the listener creation link on the prerequisite checker screen does not

work. See the Server Administrator Installation Guide for creating the HTTPS listener using the winrm command line utility.

(332601)

User Notes for Supported Red Hat Enterprise Linux,

SUSE Linux Enterprise Server and VMware ESX

Operating Systems

* The OpenIPMI device driver used by Server Administrator will conflict with the Intel IMB device driver. You must uninstall

the IMB driver before installing Server Administrator.

* When Server Administrator is installed on a system, dependency issues related to RPMs may occur. To resolve these issues,

install the missing RPMs from SYSMGMT/srvadmin/linux/RPMS/supportRPMS. If the RPMs are not available in this directory,

install these from the operating system media. (341495)

* On SUSE Linux Enterprise Server for srvadmin-omilcore rpm, upgrade from Server Administrator 6.5 to Server

Administrator 7.0 using the “rug” command fails. (DF524371) This is due to a known limitation with the “rug” command

which does not allow a package to be upgraded across multiple architectures.For more information, see:

http://www.novell.com/documentation/zlm73/lm72faq/data/bgcp03i.html#bkgdkc7

* Conflicting version requirements for libsmbios library Server Administrator is dependent on libsmbios. On Linux OS variants,

if there is a mismatch in the version requirement of libsmbios, installing Server Administrator results in warnings. It is

recommended to uninstall libsmbios versions (and the dependent software) before installing Server Administrator.

* The USB arbitration service of VMWare ESX 4.1 makes the USB devices invisible to the Hypervisor. So, when DUPs or the

Inventory Collector runs on the MN, the partitions exposed as USB devices are not displayed, and it reaches the timeout

after 15 to 20 minutes. This timeout occurs in the following cases:

When you start "DSM SA Shared Service" on the VMware ESX 4.1 managed node, it runs the Inventory Collector. While the

USB arbitration service is running, you must wait for 15 to 20 minutes for the Inventory collector to complete the execution

before attempting to stop this service, or uninstall Server Administrator. When you manually run the Inventory Collector

(invcol) on the VMware ESX 4.1 managed node while the USB arbitration service is running, you must wait for 15 to 20

minutes before the operations end. The invcol output file has the following:

<Message> Inventory Failure: Partition Failure - Attach partition has failed</Message>

</SPStatus><SPStatus result="false" module="MaserIE -i">

<Message>Invalid inventory results.</Message>

</SPStatus><SPStatus result="false">

To fix the issue, stop the USB arbitration service and run the DUPs, or Inventory Collector. Do the following to stop the USB

arbitration service:

1. Use ps aux | grep usb to find out if the USB arbitration service is running.

2. To stop the USB arbitration service during booting, use chkconfig usbarbitrator off.

3. Reboot the server after stopping the usbarbitrator to allow the DUPs and/or the Inventory collector to run.

If you require the usbarbitor, enable it manually. To enable the usbarbitrator, run the command - chkconfig usbarbitrator

on. (373924)