Release Notes

New in this release
● Scope-based access control (SBAC) now allows a more efficient and secure management of the discovered devices.
Administrators can now determine the device groups that the device managers are expected to manage.
● Seamless firmware updation on Multichassis Management (MCM) chassis with support for up to 20 chassis and their sleds.
● Ability to scan and expand appliance disk size on the Text User Interface (TUI) page.
● Supported product range expanded to the following 3rd Generation Intel® Xeon® powered YX5X (15G) PowerEdge servers:
R650, R750, R750xa, MX750c, C6520.
Enhancements
●
Redfish protocol is supported for discovery, inventory, monitoring, and for limited management (Power Control, Blink,
diagnostics, and Technical Support Reports) on devices with iDRAC9 4.40.10.00 and later.
● Added a new Resource Utilization widget on the home page to graphically display the CPU and memory utilization by the
appliance.
● An additional donut chart on All Devices page to display the installed plugin data.
● Test email functionality added to SMTP configuration.
● SNMPv3 support added for alert forwarding.
● Warranty Filtering added to Warranty Settings to customize the warranty page and reports.
Limitations
● Appliance is unable to fetch the offline upgrade availability on NFS share. [203403]
● Only the OpenSSH is supported for the discovery and inventory collection of Windows-based servers and Hyper-Vs. Other
SSH protocol implementations, like Cygwin SSH, are not supported. [157991]
● Filtering does not work as expected when the following special characters are used in the naming of groups, alert policies,
profiles, templates, and other instances: ,, \, _, %, #, ', +, ), and &. The permissible special characters are : /, ?, ., >, <,
", :, ;, |, ], }, {, [, -, =, ~, `, (, ^, *, $, @, ! [162539]
● For the Japanese locale of OpenManage Enterprise, the date format displayed is in US 'short' date format instead of the
Japanese format. [163343]
● The naming of reports only allows the following special characters: '_' and '-'. A report's name cannot have special
characters such as ,, \, %, #, ', +, ), and &. For example, a report with the name "OME3.4@NIC^Report" is not allowed.
[164776]
● You can select a maximum of 25 devices per page to perform operations such as refresh inventory, refresh status, and add
devices to groups on the All Devices page. [98194]
● The appliance fails to identify locally shared folders if the folder names have spaces in them. For example, the appliance fails
to retrieve files from an offline NFS source folder named D____K (with 4 spaces between 'D' and 'K'). This happens as the
appliance ignores the spaces and interprets the name as DK. [115310]
● Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays the
Application timeout error.
● After installing or upgrading to OpenManage Enterprise version 3.3.1 on Hyper-V, power off the appliance, remove the
standard network adapter and add a legacy network adapter, and then power on the appliance. [152723]
● Firmware catalog management using Dell.com or a local network path is limited to only the Enterprise Server catalog. Other
catalogs such as ESXi_Catalog.xml.gz are not supported.[159958]
● RAID secure attributes are not supported on target devices during template or profile deployment. [157218]
Known issues
Scope Based Access Control (SBAC)
Issue 1
Description: Post upgrade of OpenManage Enterprise to version 3.6, the AD/LDAP and OIDC (PingFederate or KeyCloak)
device managers would need to recreate all the previous-version entities such as jobs, alert policies, configuration templates,
configuration baselines, profiles, firmware baselines, firmware catalogs, and reports as these entities are only available to the
administrators post upgrade. [193698]
Issue 2
5