Release Notes

New in this release
● CloudIQ plugin support — Device group(s) can be selected to send data to CloudIQ for monitoring.
Enhancements
● Ability to view devices that have been disconnected due to Authentication failure from All-Devices page.
● Text User Interface (TUI) capabilities to selectively enable or disable debug logging for appliance and plugin services.
Limitations
● 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]
● OpenManage Enterprise version 3.6.x is unable to fetch the offline upgrade availability on NFS share. [203403]
● 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: Ownership information for device managers (AD/LDAP and OIDC) is lost on appliance upgrade.
Description: Post upgrade of OpenManage Enterprise from version 3.5 or earlier versions, 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: Alert policies and firmware baselines created by a device manager in 3.5 or earlier versions are only available to
administrator users.
Description: Post upgrade of OpenManage Enterprise from version 3.5 or earlier versions, the alert policies from the previous
appliance versions such as version 3.4 and version 3.5 are only assigned to the administrator users. Hence, these entities
created by device managers prior to the upgrade would need to be recreated. [194142]
Issue 3: After upgrade, device managers can perform VLAN operation on in-scope proxied MX7000 sleds even when the
chassis is out of scope.
Description: VLAN operation on in-scope 'proxied' MX7000 sleds is allowed for a device manager, even if the MX7000 chassis
is out of scope. [192774]
Resolution: As the operations for the proxied sleds are routed through chassis, as a best practice the admin must assign both
the chassis and the sleds in a device manager's scope.
Issue 4: Global search count is greater than the actual result count for scope-restricted device managers..
5