Release Notes

Resolution: The complete inventory is updated by running sled inventory manually/scheduled.
Issue 17
Description: If a pending scheduled deployment task for a profile is deleted, any identities that were reserved to the profile are
freed back to pool. [167265]
Issue 18
Description: For sleds that are discovered as part of the MX discovery and are in a fully managed mode, any static IP changes
on the sleds through the proxy mode (chassis), are not updated in the OpenManage Enterprise console. [167259]
Resolution: Re-discover the chassis to update the appliance with the new IP details of the sleds.
Issue 19
Description: Inventory refresh fails to update the chassis name change(s) in OpenManage Enterprise. [167923]
Issue 20
Description: Creation of templates using an MX7000 chassis that is configured to both IPv4 and IPv6 fails if the appliance is
configured to use only IPv6. [167525]
Resolution: Ensure that both the appliance and the MX7000 chassis are configured to use the same protocol(s).
Issue 21
Description: The OpenManage Enterprise alert policies in de-branded MX7000 chassis are not deleted automatically when the
chassis is off-boarded and the chassis data is purged in the appliance. [166435]
Issue 22
Description: For the YX3X servers, few of the Subsystem Health section details, available on the individual device's Overview
page, such as the Storage, Temperature, and License details are displayed as 'No Data available,' even when their health status
is 'OK.' [155425]
Issue 23
Description: The 'From' address used for all email actions, such as Reports, Update, Discovery and Alert Policies, is dependent
on the SMTP server configuration. For some SMTP server configurations, the 'From' address is the Sender Email ID specified in
the Application settings (Application Settings > Console Preferences > Email Sender Settings > Sender Email ID) and
for others it is the username used for SMTP server authentication (Application Settings > Alerts > Email Configuration >
SMTP Server Network Address). [164204]
Issue 24
Description: There is currently a discrepancy between the actual number of MIBs imported and the MIB count displayed on the
Monitor > MIB page. [160040]
Issue 25
Description: When NIC teaming is enabled on MX7000 chassis along with VLAN configuration, deploying of VLAN from the
OpenManage Enterprise console will overwrite the NIC teaming configurations to 'No teaming'. The LACP or other teaming
options would need to be reconfigured from MX7000.
Issue 26
Description: Appliance is unable to download the console upgrade from HTTP or HTTPS intranet share, when the intranet
share address is blocked in proxy filtering. [152092]
Resolution: If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download.
Issue 27
Description: Profile creation, editing and assigning requires the Boot to network ISO password has to be re-entered. [161247]
Issue 28
Description: After a fresh install or an upgrade to OpenManage Enterprise and configuration of network interface to DHCP,
any prior static IP settings will not be retained. [148789]
Issue 29
Description: The Timezone and NTP Server Address fields added to the Application Settings > Network > Time
Configuration section will remain blank and will not be displayed for a few minutes if the entered NTP server IP address is not
reachable. [151221]
Issue 30
12