Owner's Manual


Issue 6:
Description
For large number of alerts, two auto refreshes are required to show the total alerts and 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.
Issue 7:
Description
If you edited sample alert actions in OpenManage Essentials version 1.0, you must manually clone them
before migration. The alert actions will get overwritten with default sample actions.
Issue 8:
Description
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.
Issue 9:
Description
While upgrading OpenManage Essentials from version 1.0.1 to 1.2, all the existing Dell Force10 traps are
deleted because OpenManage Essentials version 1.2 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.2. After upgrading to OpenManage
Essentials version 1.2, 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 10:
Description
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
Issue 1:
Description
The Task Execution History of a Power Task (Power cycle, Reboot, or Power off) displays success even
though the task is not run on managed nodes that do not have OMSA installed. [41102]
Issue 2:
Description
If an OMSA deploy task is run on a target using either incorrect parameters or a non-applicable package,
the Tasks Execution History displays success, even though the task fails on the target device.
Example scenarios:
– Installing OMSA Instrumentation on a virtual machine
– Upgrading OMSA on a target that does not have OMSA installed
– Downgrading OMSA [083482]