Release Notes

Resolution: Avoid using non-English characters in the template name. If the template name has non-English characters, then
edit the template name in the edit wizard to remove them.
Issue 8:
Description: Compliance report is not generated when a configuration baseline is associated with more than 500 devices and is
timed out after an interval of 30 minutes. [81748]
Resolution: As a workaround, associate the baseline with 500 devices at a time. For generating compliance report for more
than 500 devices, clone the existing baseline and separately associate the other set of 500 devices.
Issue 9:
Description: After creating a system profile template from a server and setting TFTP as an option in the ShareType attribute of
the AutoUpdate section, or setting TFTP as an option in the AutoUpdate section in iDRAC and exporting the profile template,
the deployment of the template in both the scenarios always fails on any target server. [81956]
Issue 10:
Description: The Quick Deploy Settings cannot be configured for MX7000 Chassis by using the MX Chassis configuration
template. [83592]
Issue 11:
Description: While deploying a MX Chassis configuration template, the device specific attributes are not listed under the Edit
Attributes > Device Specific Attributes tab in the Deployment wizard. [83469]
Issue 12:
Description: If you associate devices with a different configuration baseline while the Make Device(s) Complaint task is
running, the latest baseline is considered by the task for remediation of these devices.
Issue 13:
Description: When a remediation task is run for a noncomplaint MX7000 chassis which differs in the Power Cap value with the
associated compliance baseline, and with Power Capping disabled, the task completes successfully. However, the device
remains noncompliant as the Power Cap value will not be remediated by OpenManage Essentials. [84766]
Resolution: You must change the Power Cap value with Power Capping enabled on the chassis.
Issue 14:
Description: The compliance chart for individual device groups display incorrect data when Enable Downgrades is selected
under Advanced Settings and the compliance of the groups are updated. [84767]
Resolution: Click the Summary tab and click the noncompliant section.
Issue 15:
Description: When a REST API is called to query noncompliant devices in a custom device group, incorrect noncompliance
details are displayed if the devices are present in more than one custom group. [84801]
Issue 16:
Description: If the SNMP alert destinations are not configured in MX7000 chassis, in OpenManage Essentials, drop-down list is
not available for the SNMP version attribute under Attributes > SNMPAlerts for MX7000 chassis configuration baselines and
templates. [84844]
Resolution: Manually configure the SNMP version—SNMPV1 or SNMPV2 in MX7000 chassis templates and baselines.
Issue 17:
Description: When you import a device configuration template or baseline, the previously selected attributes before exporting
the template or baseline are not retained.
Resolution: Before deploying the imported configuration template or baseline, manually select or clear the attributes from the
template.
Issue 18:
Description: Device configuration templates that are captured from a server with BOSS-S1 AHCI controller connected displays
invalid values of stripe size and LUN size under the AHCI attributes section. Do not edit the attributes of the template, and
deploy the template as-is. [84888]
Issue 19:
Description: In OpenManage Essentials version 2.5, the server, chassis and MX chassis configuration baselines and templates
will not group the new attributes introduced in newer firmware versions of iDRAC, Chassis Management Controller and
OpenManage Enterprise—Modular. [141855]
23