Release Notes

Description: On VMware vSphere, changing the appliance's time to an earlier time than the system time fails if the periodic
time synchronization in the VM is enabled. [198702]
Resolution: To set the appliance's time to an earlier time than the system time, disable the periodic time synchronization in the
VM, by launching the vSphere Client, go to Edit Settings > VM Options > VMware Tools > Synchronize Time with Host
and deselect the checkbox Synchronize time periodically.
Issue 4
Description: The traps forwarded from one OpenManage Enterprise console to another OpenManage Enterprise console are
received as Miscellaneous category alerts with message "unknown trap received...," if the Trap Forwarding Format is set as
"Original Format" in the former console. [188953]
Issue 5
Description: An error 'Error getting identity pool information (CGEN1006)' is displayed when sorting is done on an identity
pool's Usage page fields. Also, the identity pool's Usage page turn blank when View By filter is applied. [200451]
Resolution: Return to the identity pool's Usage page after navigating to another page.
Issue 6
Description: If an email alert policy is created to be executed on a specific day(s) without reselecting the Time Interval, then
the appliance might trigger the emails at incorrect time interval. [198784]
Resolution: When scheduling email alert policies, reselect the Time Interval along with the days. Or, create non-interval policies
without Days' selection.
Issue 7
Description: If SNMPv3 destination(s) is/are already added as alert forwarding destination(s) in the appliance, then in order
to add and apply a new alert forwarding destination address, the appliance prompts only the first time to re-enter of all the
previously entered SNMPv3 Authentication and Privacy passphrases before proceeding. [190690]
Resolution: Regardless of the appliance prompt, you must re-enter all the previously entered SNMPv3 Authentication and
Privacy passphrases every time the SNMP community string or port is edited on Application Settings > Alerts > SNMP Alert
Forwarding Configuration.
Issue 8
Description: For the discovered C9010 network switches, the Model field on the 'All Devices' and the 'Device Details' page is
displayed as 'Unknown.' [188383]
Issue 9
Description: When a C9010 network switch is rebooted or reloaded, the alerts received in the appliance are being categorized
as Miscellaneous with message 'Unknown trap received with enterprise OID...' [188382]
Issue 10
Description: When a Z9264 network switch is rebooted or reloaded, the alerts received in the appliance are being categorized
as Miscellaneous with message 'Unknown trap received with enterprise OID....' [ 194718]
Issue 11
Description: Post addition of the disk space using the Configure Appliance Disk Size feature in the Text User Interface (TUI) ,
deletion or reduction of the appliance's console expanded disk space is not supported . [192976]
Resolution: To remove a newly-added disk or to reverse the increase in size of an existing disk, you must revert to prior VM
snapshot that you are recommended to take as a backup before applying any disk configuration changes.
Issue 11
Description: For a logged-in AD user belonging to an imported child AD group, it is observed that multiple roles such as Device
Manager and Viewer are displayed upon a mouseover on the username on the appliance masthead right-hand corner. This
happens if the parent directory group and child directory group are imported with different privileges. For such AD users, the
role with the maximum privilege will be applied. [195183]
Issue 12
Description: After upgrading the appliance, you may notice an incorrect Elapsed Time for the Console Update Execution task
on the Job Details page. The displayed elapsed time exceeds the actual time taken for the completion of the task. [173882]
Issue 13
Description: Console upgrade fails from version 3.4.1 to version 3.6, if there are a large number (more than 2,000) unreachable
devices, in multiple discovery settings, in OpenManage Enterprise version 3.4.1. This happens as the long runtime of Discovery
task exceeds the maximum wait-time limit of 48 hours set for the initiation of other post-upgrade tasks. [201178]
13