Release Notes
Issue 3:
Description
OpenManage Essentials does not launch or displays an exception when the number of connections to
the OpenManage Essentials website is limited in IIS.
Resolution
The OpenManage Essentials console requires constant communication with the web server to ensure
that the data is up-to-date at all times. The communication between the console and the web server is
performed utilizing web method calls in a multi-threaded environment. As such, multiple, simultaneous
connections to the web server are required in order for OpenManage Essentials to operate properly. As a
general rule, ensure that your web server is configured for a minimum of 50 active connections.
Issue 4:
Description
When launching OpenManage Essentials, the following error is displayed: "Client Logon credentials not
authorized error". [31507]
Resolution
Restart the DSM Essentials Host service.
Issue 5:
Description
OpenManage Essentials does not launch when the IP address of the remote database is changed. [31801]
Resolution
Reinstall OpenManage Essentials and target the existing remote database with the new IP address.
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. Systems discovered using SNMP report physical
processors, and the systems discovered using CIM reports logical processors.
Issue 1:
Description
In the OpenManage Essentials GUI, if you attempt to create a discovery range with an IP address ending
in ".0", the following error message is displayed: "The last octet cannot be 0". Depending on the subnet
mask, an IP address ending in ".0" is valid for a device. [48781].
Resolution
To workaround ths issue, import a .csv file with a device IP ending in ".0". OpenManage Essentials
discovers and classifies the device properly using this method.
Issue 2:
Description
If you create a new custom device group with modular servers, and perform another discovery, all the
server objects in that group are lost. [49224]
Resolution
To workaround this issue, do not select the group node for discovery, but rather just the devices within
that group.