Release Notes

Issue 27
Description: When an already imported MIB is renamed and parsed through API the trap status is reported as 'Existing' instead of
'Imported.'[111854]
Issue 28
Description: Ignore alert policy created for warranty, firmware compliance, configuration compliance alert will be ignored only if alert is
generated from the same device from which ignore policy was created. In other cases, alert will be received and not ignored. [124596]
Issue 29
Description: SSH Private key can be applied while adding a remote script in the Script Execution page. [129366]
Issue 30
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 31
Description: In order to leverage performance improvements made in the Active Directory login, users have to delete and re-import the
user groups in OpenManage Enterprise version 3.2.
Issue 32
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 33
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 34
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 35
Description: Expect a delay while deleting a large number of devices by selecting the "Across all pages" option. This delay in completion of
the job is due to the deboarding of the already onboarded devices by the appliance before their deletion. [136847]
Issue 36
Description: With this release, context-sensitive help on Power Manager plugins is currently not available. [136300]
Issue 37
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 38
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.
Dell EMC OpenManage Enterprise Version 3.2 Release Notes 7