Release Notes

Description: After the console is upgraded, there is a delay of approximately 15 minutes in the initiation of the Post Upgrade task by the
appliance. [130142]
Issue 58
Description: When an already imported MIB is renamed and parsed through API the trap status is reported as 'Existing' instead of
'Imported.'[111854]
Issue 59
Description: Ignore alert policy created for warranty, firmware compliance, and configuration compliance alerts will be ignored only if
alerts are generated from the same device from which ignore policy was created. In other cases, alerts will be received and not ignored.
[124596]
Issue 60
Description: SSH Private key can be applied while adding a remote script in the Script Execution page. [129366]
Issue 61
Description: The Schedule advanced filter in the Monitor > Discovery page incorrectly displays even those discovery jobs which have
completed their initial scheduled run. [128842]
Issue 62
Description: All the AD/LDAP groups imported from the OpenManage Enterprise versions before version 3.2, such as the version 3.1 and
version 3.0, should be deleted and re-imported.
Issue 63
Description: The .CSV files, that record the deleted alerts from the Alert log, fail to capture the Device Name and the Device IP details
of the alerts received from the undiscovered devices.[132915]
Issue 64
Description: Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays an
Application timeout error. [133201]
Resolution: When exporting large firmware compliance reports, the following workarounds can be employed :
• Allocate more memory to the appliance while installing.
• Before exporting large reports, ensure that other jobs are not running.
• Use the Firmware Compliance per Component or the Firmware Compliance per Device Report instead of exporting.
• Use filters to derive a smaller result set before exporting.
Issue 65
Description: A "Connection to server failed" error is displayed by the failed Power Action Tasks. Power Action tasks fail when they
encounter servers where no power state change is required. This error message, though misleading, does not mean that the appliance is
unable to establish contact with the server. [136816]
Issue 66
Description: The Monitor > Jobs > View Detail Execution History page incorrectly displays Could not set alert destination on the
target under Messages, even for the successfully-completed jobs created for setting of trap destinations for the MX7000 chassis.
Issue 67
Description: Deleting a device from the All Devices page would fail if there are active jobs involving the device.
Resolution: Before deleting a device from the All Devices page, ensure there are no jobs in the 'running' status involving the device.
Installation
Dell EMC OpenManage Enterprise is provided as an appliance that you can deploy on a hypervisor and manage resources to minimize
downtime. The virtual appliance can be configured from the application web console after initial network provisioning in the Text User
Interface (TUI). For steps to view and update the console version, see the Dell EMC OpenManage Enterprise User's Guide on the support
site.
NOTE:
For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the
support site.
14