Release Notes

Description: The firmware update task using the HTTP and HTTPS local shares fails, if these local shares were configured
using proxy settings and are not listed in the proxy exception list. [151332]
Resolution: The HTTP and HTTPS local shares which are configured using the proxy settings, need to be listed in the proxy
exception list before initiating any firmware update tasks using these shares.
Issue 14
Description: Firmware upgrade fails when iDRAC firmware versions older than 2.40.40.40 are upgraded directly to 2.63.60.61
with an error message Unable to verify Update Package signature. This failure happens as the firmware versions older than
2.40.40.40 cannot validate the latest SHA-256 digital signature of the Dell Update Packages. [146564]
Resolution: First upgrade the older iDRAC firmware versions to 2.40.40.40 before attempting an upgrade to iDRAC firmware
version 2.63.60.61.
Issue 15
Description: The Update Firmware button remains enabled even when there are no firmware catalogs available for upgrade or
downgrade. [108218]
Issue 16
Description: The firmware rollback on the PowerEdge MX7000 sleds is not supported. Also, rollback on sleds is not supported
when the onboarding state of the sleds is Proxied.[116172]
Issue 17
Description: A job for firmware rollback on the PowerEdge MX7000 sleds, though allowed in the appliance, would fail. This
happens because the firmware rollback is not supported on the MX series sleds discovered as part of MX7000 chassis discovery
or in proxied state. [136820]
Issue 18
Description: When updating MX7000 chassis in the MCM mode, always make sure that the lead chassis is updated as the final
step after updating all the member chassis. Also, chassis and sled firmware updates must be initiated separately. [168883]
Issue 19
Description: The Firmware Update task fails on the MCM member chassis with error message 'Syncing data with passive MM
Task Failed. Completed With Errors'. [169333]
Configuration management
Issue 1
Description: For the MX7000 chassis managed with OpenManage Enterprise - Modular versions 1.31.00 or earlier, the
remediation task (Make Devices Compliant MX7000) fails with an error message — "error while applying Setting: Users|
Directoriesnull|null Required fields are missing (UserName or Password)." [193435]
Resolution: Disabling the "User Directories" section in the compliance template and then initiating the Make Compliant task
successfully completes the remediation task.
Issue 2
Description: If only VLANs are assigned to a target device during profile deployment, then these VLANs are not reclaimed by
the appliance when the profile is unassigned from the device. This behavior is not seen if other identities were assigned along
with VLAN definitions during the profile deployment. [174360]
Issue 3
Description: User Password attributes can't be set on the MX7000 and the Chassis Management Controller Deployment
templates. [200293]
Issue 4
Description: If only VLANs are assigned to a target device during profile deployment, then these VLANs are not reclaimed from
the device when the profile is migrated to a new device. This behavior is not seen if other identities were assigned along with
VLAN definitions during the profile deployment. [174576]
Issue 5
Description: Profile redeployment on FX2, VRTX, and M1000e chassis with edited VLAN configuration (tagged and untagged
values), clears only those VLAN values which were set during the initial deployment of the profile. The other VLAN values on the
ports that were not set during the initial deployment of the profile are not cleared during redeployment. [175692]
Issue 6
10