Release Notes
When a client system is discovered using WMI protocol, the “Processor Information” table is not displayed. However,
some processor information can be obtained from the FRU table if OMCI is installed.
--------------------------------------------------------------------------------
Alerts
--------------------------------------------------------------------------------
OpenManage Essentials can receive and process alerts from systems with an IPv4 address format.
If the intensity of an alert storm increases beyond 5 traps per second, it could take OpenManage Essentials several
minutes to process all the alerts. New alerts that are received in the interim are not displayed on the console until all
the alerts in the storm are processed.
Alert Actions: Application Launch alert actions do not show the application in interactive mode if the Microsoft
Window's "Interactive Service Detection" service is stopped. To see the applications, you have to start the service.
Alerts are not received when "SNMP services" are stopped and started. To resolve this issue, restart the “DSM Essentials
Network Monitor” service.
For large number of alerts, two auto refreshes are required to show the total alerts & count on the home page. If the
alert count is large, the first refresh fetches and shows only a subset of alerts. The second refresh displays the entire
list.
If you edited sample alert actions in 1.0, you must manually clone them before migration. Those will get overwritten
with default sample actions.
The test trap from PowerVault MD 32xx/32xxi is received in OpenManage Essentials system with IP 0.0.0.0. This is an
expected behavior in OpenManage Essentials and any other trap listener.
While upgrading OpenManage Essentials from version 1.0.1 to 1.1, all the existing Dell Force10 traps are deleted
because OpenManage Essentials version 1.1 installs the tested and verified Dell Force10 trap definitions. Also, the Dell
Force10 traps from the MIB Import Utility are also removed and the severity of the traps are set as defined in
OpenManage Essentials version 1.1. After upgrading to OpenManage Essentials version 1.1, make sure that you update
the associated Event view/action filters for these Dell Force10 trap definitions, because the previous OpenManage
Essentials version 1.0.1 event filters may not work after the upgrade.
Issue:
When creating an alert action for an application launch, OME system path variables which contain % signs are not
supported. Examples of unsupported variables are:
%WINDIR%, %SystemRoot%, %APPDATA%, %HOMEPATH%, %PATH%, and so on.
Resolution:
Avoid using the system path variables with % sign and use the full absolute path to the executable file.
--------------------------------------------------------------------------------
Remote Tasks
--------------------------------------------------------------------------------
If a user from the OmeAdministrators group executes a command that requires system Administrator privileges for tasks
such as a command to stop a service, the task status is not displayed correctly. To view the correct status of the task,
click the task under "Task Execution History".
When OpenManage Essentials is installed with a remote database server, the database connection may be lost (due to
local network failures, database server reboot, and so on). If this happens, tasks may no longer run as scheduled. When
observed, normal operation can be restored by restarting the OME Windows services: “DSM Essentials Network Monitor”
and “DSM Essentials Task Manager” [498134].