Release Notes

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 21
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 22
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 23
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 24
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 25
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 26
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: AD group searches fail for an hour due to slow sync when AD/LDAP groups are added using the DNS option.
Description: Searching for an active directory group name in the Import Directory Group wizard immediately after adding the
directory service using the DNS option could unsuccessful for up to one hour. This happens if there is a delay in synchronization
of the newly-added domain controller. [203928]
Issue 2: Connection State of ESXi servers that are disconnected due to authentication failure are shown as 'Disconnected.'
Description: For the authentication-related disconnected ESXi servers, the Connection State on the All Devices page is
displayed as 'Disconnected' instead of 'Disconnected (Authentication failure)'. [198421]
Issue 3: If Ping Identity is used for OIDC provider, the appliance can only be used with Administrator role.
Description: With OIDC provider PingFederate, it is observed that all the OpenID client policies associated with the
OpenManage Enterprise Client IDs are reset to the policy marked as 'Default' when the appliance console gets re-registered
with the OIDC provider. Re-registration of the appliance console with OIDC provider happens in the event of an appliance
upgrade, change in network configuration, or change in SSL certificate. [193717]
Resolution: This is an issue with the OIDC provider, hence, the administrator must reconfigure all the OpenManage Enterprise
Client IDs on the OIDC provider site to avoid any security concerns.
Issue 4: Manually setting the time to an earlier time on the VMware vSphere fails if periodic time synchronization is enabled in
the VM.
Description: On VMware vSphere, changing the appliance's time to an earlier time than the system time fails if the periodic
time synchronization in the VM is enabled. [198702]
Resolution: To set the appliance's time to an earlier time than the system time, disable the periodic time synchronization in the
VM, by launching the vSphere Client, go to Edit Settings > VM Options > VMware Tools > Synchronize Time with Host
and deselect the checkbox Synchronize time periodically.
Issue 5: Identity pool Usage page shows "CGEN1006" error on sorting for the first time.
11