Release Notes

Issue 28
Description: In order to support discovery with domain credentials, OpenManage Enterprise 3.2 and later uses SSH instead
of WSMAN. Hence, all the Windows and Hyper-V devices discovered prior to updating the appliance have to be deleted and
re-discovered using their SSH credentials.
Issue 29
Description: While creating sever discovery jobs with the Host OS option in the Create Discovery Job wizard, the check box
Discover using SSH (Linux) in the Additional Settings dialog box is misleading and should be interpreted instead as Discover
using SSH (Linux, Windows, and Hyper-V).
Tasks
Issue 1
Description: The IPMI CLI command -I lanplus shell doesn't end automatically and the jobs associated with such tasks
would appear as 'In Progress' for a prolonged time on the Jobs page. [173061]
Resolution: You must run an Exit command to terminate such jobs.
Issue 2
Description: After upgrading to the latest version of OpenManage Enterprise, the existing job IDs are changed. [108055]
Issue 3
Description: Configuration > VLANs page does not update automatically after importing VLAN definitions from file or from
chassis. [153611]
Resolution: Refresh the Configuration > VLANs page or navigate to another page and return to view the newly-imported
VLAN definitions.
Firmware and driver updates
Issue 1
Description: For the discovered network switches with firmware version 10.5, the firmware version is displayed as 'NA' on the
Device Overview page. [192087]
Issue 2
Description: Inventory collection and the firmware update on chassis storage sleds is not supported in OpenManage Enterprise
if they are managed via chassis device management. [198981]
Issue 3
Description: When firmware compliance check is executed for multiple firmware baselines simultaneously, the warning alert
—CDEV9000 - This device and several others has become non compliant after running compliance task: <Baseline Name>—
is sometimes logged for these baselines on the Alerts page with any one random device in any of the firmware compliance
baseline. Sometimes the firmware baseline is not associated with the device. [185315]
Issue 4
Description: When a firmware/driver baseline with many devices is checked for compliance, the warning alerts CDEV9000 on
the Alerts page is logged for only one random non-compliant device from that baseline. [185312]
Issue 5
Description: Driver update task fails for the in-band Windows servers if their IP addresses are outside of the appliance's
Restrict Allowed IP Range. [199725]
Resolution: Before initiating driver update tasks on the in-band Windows targets, ensure that their IP addresses are included in
the Restrict Allowed IP Range (Application Settings > Security > Settings).
Issue 6
Description: In-band driver updates are only supported on Windows with OpenSSH. Driver updates on third party SSH hosted
on Windows, such as the CygwinSSH, are not supported. [157887]
Issue 7
Description: For the family of network adapter drivers, the operating system installed version, as seen in the Device Manager,
differs from the version available in the online catalog. [157824]
9