Release Notes

Supply Information section. To display the correct information, discover the server using either SNMP, or

both SNMP and CIM protocols. [300080]

Issue 34:

Description: Even after performing inventory on the discovered Linux servers N number of times, the

Linux servers are still listed under Non-Inventoried systems.

Resolution: To resolve this issue perform the following steps:

For Red Hat Enterprise Linux 5.5, SUSE Linux Enterprise Server 10, SUSE Linux Enterprise Server 11

1. Mount the OpenManage Server Administrator DVD in the Linux server.

2. Install 'srvadmin-cm' rpm.

3. Restart the OpenManage Server Administrator services.

4. Ensure that the OpenManage Server Administrator inventory collector is working fine (Run ./

invcol -outc=/home/inv.xml from /opt/dell/srvadmin/sbin/invcol location)

5. Re-inventory the Linux server in OpenManage Essentials.

6. Now the Linux server will be either listed under Compliant systems or Non-Compliant systems.

Issue 35:

Description: An exception might be seen in the OpenManage Essentials Console, when a discovered

virtual machine of a VMware Classic ESX server is selected from the Unknown node in the All Devices

tree. [516274]

Issue 36:

Description: The RAC Console application launch point is available when SNMP protocol is used to

discover the DRAC (Dell Remote Access Controller) devices. [515308]

Issue 37:

Description: To properly discover, inventory and classify a Dell server running ESXi 5.0, you must install

the OpenManage Offline Bundle and VIB 6.5 A02 available at support.dell.com. For more information,

see delltechcenter.com/ome.

Issue 38:

Description: When you create a custom group, you have the ability to select a pre-defined device search

query or the ability to select individual devices and groups to form your newly created custom group.

If you select a device search query as your basis for your custom group content and you subsequently

decide to modify the device search query, the results of the modified device search query is not reflected

in the custom group. You will have to delete the custom group and recreate it using the newly modified

device search query group.

If you create a custom group using a device search query, you subsequently modify the device search

query and then attempt to edit the custom group that used the device search query in question, the

original device search query group gets deleted. So, once you create a custom group based on a device

search query, do not edit it. If you need to modify it, delete it first and then re-create it.

Issue 39: