Release Notes

Issue 8:
Description
While upgrading from OpenManage Essentials version 1.0.1 or 1.1 installed with remote SQL Server 2005
to OpenManage Essentials version 2.1, the following message is displayed:
“SQL Server 2005 is detected on the target system. The minimum version of SQL Server supported by
Essentials is SQL server 2008.” [31161]
Resolution
In this case, you must manually migrate the data from SQL Server 2005 to other supported SQL Server
versions, and then upgrade to OpenManage Essentials version 2.0. For more information, see the
Frequently Asked Questions section in the OpenManage Essentials version 2.0 User's Guide.
Issue 9:
Description
After upgrading OpenManage Essentials to version 2.1, the Microsoft Hyper-V servers are not grouped
under Microsoft Virtualization Servers in the Devices portal's device tree. [31770]
Resolution
The Microsoft Hyper-V servers are automatically grouped under Microsoft Virtualization Servers on the
next discovery or inventory, if scheduled. You can also select "Perform Inventory Now" on the respective
discovery IP range to resolve the issue manually.
Issue 10:
Description
After upgrading from OpenManage Essentials version 1.0.1 to 1.2, while accessing hardware logs for any
server, you start seeing one or more exceptions in the console.
Resolution
1. Stop “OmeDAService “, “OmeHostService“, “DSM Essentials Task Manager” and “DSM Essentials
Network Monitor”, services.
2. Restart the IIS server.
3. Start “OmeDAService “, “OmeHostService“, “DSM Essentials Task Manager” and “DSM Essentials
Network Monitor”, services.
4. Launch the OME console.
Launching OpenManage Essentials
Issue 1:
Description
If the host name of the management station is changed after the installation of OpenManage Essentials,
you will be prompted to provide the system credentials when OpenManage Essentials is launched.
[38871]
Issue 2:
Description
OpenManage Essentials launches in Internet Explorer even if any other browser is set as the default
browser. [35491]