Users Guide
Known issues
● To receive alert notifications in OpenManage Mobile on Android version 4.0.3, you must have a Google account registered on
the device.
● Unable to validate the GCM token if the OpenManage Mobile application is moved to the SD card, and the SD card is
removed from the device.
To validate the GCM token after re-inserting the SD card, do the following:
1. On any screen of OpenManage Mobile, tap the overflow menu.
NOTE: The overflow symbol differs from device to device. For example, it can be displayed as a symbol, or at
the lower-left or lower-right corner of the screen next to the Home button.
2. In the list displayed, tap Settings, and then tap Refresh to refresh the GCM token.
3. Edit the connections of all the OpenManage Essentials added and resubscribe to the alert filters.
● Description :Unable to power on a server if the KG key value in the RAC GUI page is set to a non-default value.
For iDRAC shown in OME OpenManage Mobile will not perform the operation with non-default values.
● If the log in page appears again after you exit OpenManage Mobile, use home button to minimize the application.
● If you have more than 100 devices in the All Devices group, the devices are sorted by health only on the first screen. From
the next screen, you can view the devices but they are not sorted by health.
● OpenManage Mobile offline data cache will be lost if the phone is rebooted or if OpenManage Mobile is inactive for long
periods.
● OpenManage Mobile offline cache can be lost if your mobile device has limited memory.
● OpenManage Mobile displays only the top 100 log entries from an iDRAC.
● OpenManage Mobile is not supported on 11th generation or earlier generations of iDRAC.
● Unable to receive push notifications if OpenManage Essentials is re- installed by retaining the same database as an earlier
OpenManage Essentials installation.
● Unable to acknowledge or delete an alert received by a user who is a member of the OMEPowerUsers group.
● Last successful remote desktop session is seen when multiple VNC sessions are running at the same time because bVNC is
an open source component and its behavior is outside the scope and control of OpenManage Mobile. OpenManage Mobile
has limited control over launch interactions and subsequent activity.
Troubleshooting OpenManage Mobile
43