Release Notes

Issue 47
Description: Authentication by one-way and two-way trusts of AD users is not supported by the appliance.
Issue 48
Description: From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses. [102153]
Issue 49
Description: When PCIe cards are mapped to the FX2/FX2s chassis, migration of identities is not supported on the sleds in the same
FX2s chassis since the FQDDs differ.
Issue 50
Description: Console Upgrade from 3.0 through NFS Share fails. Also, console Upgrade through HTTPS (internal Share) fails when
upgrading from versions 3.0 and 3.1. [114683]
Resolution: Use the online method for updating, or use the HTTPS method. Ensure that the security certificates are signed by a trusted
third-party certificate authority while using the HTTPS method of update.
Issue 51
Description: The selected target devices or device groups while creating an alert policy in OpenManage Enterprise-Tech Release are
cleared when the appliance is updated. [115698]
Resolution: After updating the appliance, edit the alert policy and select the target devices or device groups to receive the group-specific
alerts.
Issue 52
Description: After you update the appliance from OpenManage Enterprise-Tech Release, the Syslog server messages do not retain the
standard format of <timestamp><hostname>_<Alert_Message>. The alerts are displayed as
"EEMI@123_[id]":Alert_Message. [115699]
Issue 53
Description: Few alerts from the PowerEdge R240, R340, T140, T340, and R740xd2 servers are received with unknown severity in the
OpenManage Enterprise appliance. [112404]
Issue 54
Description: While programmatically deploying the OpenManage Enterprise from Linux shell, if the argument provided for --name= in the
command line begins with a "$" then the argument is ignored and appliance is deployed with the name OPENMANAGE ENTERPRISE.
[121158]
Resolution: The --name= argument, which begins with "$" in the command line must be enclosed in single quotes, for example, --name=
'$OME-VM'.
Issue 55
Description: The Severity status in the Alert log for the alerts received from the PowerVault ME4 storage arrays is being reported as
Unknown by the appliance. This defect is due to the unavailability of the precanned MIBs for the PowerVault ME4 storage arrays in the
appliance console. [122657]
Issue 56
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 57
Description: When an already imported MIB is renamed and parsed through API the trap status is reported as 'Existing' instead of
'Imported.'[111854]
Issue 58
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 59
Description: SSH Private key can be applied while adding a remote script in the Script Execution page. [129366]
Issue 60
Description: The Schedule advanced filter in the Monitor > Discovery page incorrectly displays even those discovery jobs which have
completed their initial scheduled run. [128842]
13