Release Notes

Issue 10
Description: After a chassis is removed from the MCM group, you must rediscover the lead and member chassis to create and deploy a
configuration template.
Issue 11
Description: The Migration Profile task fails if the user is not configured on the target device with the error: 'User Name is not
configured '. [107376]
Issue 12
Description: If the IP configuration of a discovered device is changed during template deployment (from DHCP to Static or vice versa),
the Boot to Network ISO operation fails. This happens as the appliance is unable to ping the target post template deployment. [113576]
Issue 13
Description: Unable to set Target iSCSI IQN on BIOS-iSCSI via reference server template deployment, as it fails with Invalid
AttributeValue error. The default iSCSI Target IQN format of the iSCSI controllers of devices such as PowerVault ME4012 array and
Equallogic PS array, is not accepted as a valid IQN format for deployment with IDRAC version 3.34.34.34. [132601]
Resolution: Select 'BIOS' attributes only for deployment.
Issue 14
Description: Creation of a chassis template from a reference M1000e chassis which has Firmware versions 6.10 or later fails if SMBv1 is
disabled in the appliance. [129049]
Resolution: Enable SMBv1 in the appliance using Application Settings > Console preferences > SMB settings to create chassis
templates from M1000e chassis with firmware versions 6.10 or later.
Issue 15
Description: Template Deployment with iDRAC Management IP option "Set static IP for each device" fails with error message
"connection lost" with IPV6 IP (Legacy(3.1)). It works with IPV4.
Issue 16
Description: Template Deployment with iDRAC Management IP option "Set as DHCP" fails, and the task has to be tracked from iDRAC
for final status.
Others
Issue 1
Description: When the appliance is configured to IPv6, it is unable to reach the targets like SMTP, syslog servers and share through
FQDNs which is resolvable to both IPv4 and IPv6. [153980]
Resolution: When the features that use FQDN fail, it is recommended to check the interface and use the corresponding IP. For instance,
if the primary network is enabled with only IPv6, and the FQDN expected to work on primary interface fails, user can use IPv6 address in
the place of FQDN as a workaround. This applies for secondary interface as well.
Issue 2
Description: Creating a report with chassis table columns and device table columns using a query with an 'or' will not generate a report
with expected result. [154713]
Issue 3
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 4
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 5
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 6
9