Release Notes

Issue 4
Description: When a Lead chassis retires and a backup chassis becomes the new lead on OpenManage Enterprise, the refresh inventory
marks the original backup chassis and its associated devices to be invisible and not shown in the UI. [161300]
Resolution: Discover the new Lead on OpenManage Enterprise.
Issue 5
Description: "Virtual identity by usage report" does not display the identity state as "Used" when the virtual identities were assigned to a
device from an external source. The current reports do not support the "Used" status, and instead display them as either 'Reserved' or
'Assigned'. [160507]
Issue 6
Description: The rack physical groups with long names consisting of more than 150 characters with no spaces, the appliance wizards
experiences an 'overflow'. [164157]
Resolution: Limit the number of characters used to create names.
Issue 7
Description: If a Configuration Inventory task finds external identities that fall in an existing identity pool and that identity pool is later
deleted and a new one with the same or overlapping identities is created, the new identity pool will not show those identities as assigned.
[160888]
Issue 8
Description: OpenManage Enterprise appliance does not prevent unauthorized shell access by an end user with FSD enabled. The GRUB
bootloader allows root level shell access during boot. [162922]
Issue 9
Description: Complete inventory is not collected when a sled is removed and reinserted in the chassis. [165192]
Resolution: The complete inventory is updated by running sled inventory manually/scheduled.
Issue 10
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 11
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 12
Description: Inventory refresh fails to update the chassis name change(s) in OpenManage Enterprise. [167923]
Issue 13
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 14
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 15
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 16
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 17
10