Release Notes

Issue 13
Description: If a chassis template is deployed with a new static IP address on the FX2, VRTX, and M1000e chassis, then these
devices need to be re-discovered with the new IP for managing the device.
Issue 14
Description: The deployment task of an MX7000 chassis fails if proxy authentication is enabled in the configuration template
with error: 'Unable to complete the request because the input value for Password is missing or an invalid value is entered'.
[108779]
Issue 15
Description: The directory service details in an MX7000 chassis are overwritten after the device configuration template is
deployed.
Issue 16
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 17
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 18
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 19
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 20
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 21
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 22
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: 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 2
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 3
12