Release Notes
2.
Restart IIS server.
3.
Start “OmeDAService “, “OmeHostService“, “DSM Essentials Task Manager” and “DSM Essentials Network
Monitor”, services.
4.
Launch the OME console.
Issue:
The Deploy Server Administrator task runs forever
Resolution:
Make sure install arguments are valid for Deploy Server Administrator task. For more information about Deploy Server
Administrator task and install arguments refer to OpenManage Essential's user guide or to Deploy Server Administrator
white paper at http://en.community.dell.com/techcenter/extras/m/white_papers/20069180/download.aspx. If
arguments are invalid, stop the task and create a new task with valid arguments.
--------------------------------------------------------------------------------
Discovery and Inventory
--------------------------------------------------------------------------------
The processor count in OpenManage Essentials differs for managed systems that contain processors with multiple cores
or HyperThreading enabled. The count differs based on whether the managed system is discovered using the CIM or
SNMP protocol. The systems discovered using SNMP reports physical processors, and the systems discovered using CIM
reports logical processors.
When the name resolution on an IP address to a host name fails using DNS, OpenManage Essentials attempts to resolve
the name using the NetBIOS name query. This action may cause the device to appear in Essentials with the NetBIOS
name even if it does not have a DNS entry. [138013]
For Remote Access Controllers (RACs) that have instrumentation installed and that are running on the host operating
system, the RAC IP addresses are shown in the "RACDevice" table. [134365]
For NIC information on systems, Essentials uses the operating system's provider(s) to retrieve data rather than Server
Administrator. This behavior can result in discrepancies in reporting NIC information between Essentials and Server
Administrator. For example:
3.
On Linux systems, adapters may be named differently between
OpenManage Essentials
and Server
Administrator. For example,
OpenManage Essentials
may report a NIC adapter as "eth0," while Server
Administrator shows the actual manufacturer name of the NIC.
4.
If more than one NIC card is not configured with an IP address, OpenManage Essentials may show only one of
the cards with an IP address of 0.0.0.0.
5.
OpenManage Essentials may not report disabled NIC adapters.
While performing discovery, if a device is discovered using "host name," and if its IP Address changes at a later time,
OpenManage Essentials displays two devices after the next discovery cycle. One device displays the old IP address and
status as Power Down, while the other displays the new IP Address. This problem is likely to affect systems that have
DNS-DHCP IP addressing and for which the IP addresses frequently change. A workaround to eliminate duplicate device
is to delete the device with the old IP address. [148069]
The choice of protocols specified for discovering and managing the devices can result in varying levels of manageability.
For instance, if you choose to manage devices in your network using only WMI, the devices with only SNMP agent
(example DRAC) are classified under the "Unknown" group and consequently, you may not get application launch
(example RAC console) functionality for the device. To avoid such issues, make a careful choice of the protocols while
configuring discovery ranges, keeping in mind the devices (and protocols supported by agents running on those devices)
that you are going to manage. [153729]