Release Notes

New in this release
Server-initiated discovery—With this feature, new servers in a datacenter can notify OpenManage Enterprise and can get
automatically discovered. Servers should have a firmware version of 4.00.00.00 or later.
Configuration management with Profiles—This feature enables pre-creating profiles with device specific settings (including virtual
identities) for deployment to devices later. Profile management allows for easy migration of settings from one device to another.
In-band driver update support for the devices running on 64-bit Windows versions.
Non-virtual identity attributes can inherit values from the source template and can be edited prior to deployment or auto-deployment.
Secure attributes of templates, such as passwords, can be edited.
Identify and mark 'assigned' identities in the device configuration inventory.
A pre-canned 'Virtual Identity Usage by pool' report is included in Reports.
Enhancements:
VLAN setting changes in templates can be immediately propagated on modular systems.
Support for YX4X XC (14G XC) platforms. For more information, refer to OpenManage Enterprise version 3.4 Support Matrix.
Improved virtual identity assignment—virtual identities which are not assigned from OpenManage Enterprise, are automatically
identified and marked as 'assigned.'
Improved robustness and scaling for server configuration inventory.
In the event of a console upgrade failure, the pre-installed state of the appliance is restored.
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]
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
Discovery and inventory
Issue 1
Description: Discovery of Windows server(s) using non-admin credentials fails with an error message 'Unable to connect to the device
over SSH because a connection error occurred.' This must be interpreted instead as 'Unable to perform the requested action because the
device management endpoint authentication over SSH failed'. [158088]
Issue 2
Description: The Guest information for the discovered Hyper-V 2012 R2 servers is not available on the device's Hardware page. [159535]
Issue 3
5