Unable to view BLE enabled servers in Android 7.0 adn 7.1.1
Sometimes, on devices running Android version 7.0 or later Quicksync 2 does not detect bluetooth low energy (BLE) enabled servers.
Workaround:
Restart the device and try again.
Unable to add OpenManage
Essentials to OpenManage Mobile
If you are
unable to add an OpenManage Essentials to OpenManage Mobile, you can
try the following workarounds:
Workarounds:
Verify network configuration: To add an OpenManage Essentials server to OpenManage Mobile, OpenManage
Essentials must be available on the specified web port (default 2607)
and not stopped by any firewall or other security mechanism. Make
sure that VPN and/or wireless network is connected, enabled, and configured.
Verify if you are able to connect to the OpenManage Essentials host
from your device by using a web browser.
Verify credentials: Make sure
that the user name and password are correct to log in to the remote
system. If you use domain credentials, make sure that the domain name
is entered in the correct format supported by your directory server
(such as companyname or companyname.com).
Verify OpenManage Essentials version: OpenManage Mobile requires the latest OpenManage Essentials version 2.1 and above.
Unable to add iDRAC
to OpenManage Mobile
If you are unable to add
an iDRAC to OpenManage Mobile, you can try the following workarounds:
Workarounds:
Verify network configuration: To add an iDRAC to OpenManage Mobile, iDRAC web server must be enabled. Ensure the port ID number in the iDRAC UI and the OpenManage Mobile device are the same. Ensure that VPN and/or wireless
network is connected, enabled, and configured. Verify if you are able
to connect to the iDRAC host from your device using a web browser.
Verify credentials: Make sure
that user name and password are correct to log in to the remote system.
If you use domain credentials, make sure that the domain name is entered
in the correct format supported by your directory server (such as
companyname or companyname.com).
Verify iDRAC version: OpenManage
Mobile requires iDRAC version 7 or later with Enterprise or Express
license, which is available in most 12th generation or later PowerEdge
servers.
Unable to add iDRAC
to OpenManage Mobile using iDRAC Quick Sync Read
If you are unable to add an iDRAC to OpenManage Mobile using iDRAC
Quick Sync Read, you can try the following workarounds:
Workarounds:
Update the iDRAC firmware. For more information about
updating the iDRAC firmware see, iDRAC User’s Guide.
Update the OpenManage Mobile to the latest available
version.
The Near-Field Communication (NFC) chip in the mobile
device should be in contact with the iDRAC Quick Sync activation switch.
Refer to your mobile device’s documentation to find the location of
the NFC chip.
Remove the protective casing from the mobile device.
Slow data retrieval
There is a delay of several minutes in retrieving
data.
Workaround: Internet connection on
your phone may be slow. Use OpenManage Mobile on WiFi or 3G or later
network.
Operations such as viewing event logs
through OpenManage Essentials require OpenManage Essentials to retrieve
data from the managed nodes and sometimes there is a delay of several
minutes in retrieving data.
Updated information
not displayed in OpenManage Mobile
Information
displayed in OpenManage Mobile does not match the information displayed
in OpenManage Essentials or iDRAC.
Workaround: OpenManage Mobile
uses a data cache to improve performance. Tap Refresh on the overflow menu of the screen to update displayed information.
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.
Incomplete device information
The operating system name or hostname
is not displayed.
Workaround: To receive
the hostname or operating system name, you might need to install OpenManage
Server Administrator (OMSA) on the managed node.
Incomplete information for devices
managed by OpenManage Essentials.
Workaround: Make sure that data is correctly inventoried in OpenManage Essentials.
For more information, see OpenManage Essentials User’s Guide.
Unable to register
for push notifications
Unable to register for
push notifications.
Workaround: To register for push notifications from an OpenManage Essentials, perform the following steps:
Tap .
Tap Settings.
Tap Notifications.
In OpenManage Mobile ensure Allow Notifications is enabled.
Delay in receiving
push notifications
Either alert notification is not
received, or there is a delay of several hours in receiving alerts.
Workarounds:
Verify OpenManage Essentials operation: Make sure that OpenManage Essentials is receiving alerts, and it
is successfully transmitting the alerts to the Dell Message Forwarding
Service. For more information about transmitting alerts from OpenManage
Essentials to the Dell Message Forwarding Service, see OpenManage
Essentials User’s Guide. During normal operation, it takes up
to two minutes for the alerts to transmit from OpenManage Essentials
to Dell Message Forwarding Service.
Understand provider limitations: The Dell Message Forwarding Service uses provider notifications
services including Google Cloud
Messaging. Google imposes a notification limitation
on a per device and per application basis. If your alert notifications
are more than 100 per day, select a more specific filter to reduce
the number of alerts transmitted to your mobile device.
Verify phone network connectivity: Push notification requires an internet connection on your phone
or a wireless connection (that may not be available in certain areas,
such as remote locations and places with poor signal).
Carriers, internet service providers, and networking equipment may
end the connection to Google servers if your mobile device
is inactive. Notifications cannot be received until the connection
is restored.
A message is displayed in OpenManage
Essentials if it is unable to communicate with a specific device as
it is not registered.
Workaround: If OpenManage
Mobile is backed up and restored on to your mobile device, the GCM registration token may need to be refreshed. Go to the Settings screen and tap Refresh to reinstall the GCM token. You must have an internet
connection for this request to be successful.
NOTE: If you refresh the GCM token, edit the connections of all the OpenManage Essentials
added and resubscribe to the alert filters.
Unable to log in to
OpenManage Mobile
You cannot log in to OpenManage
Mobile if:
Don’t keep Activities option is selected in Settings > Developer options screen.
Workaround: Make sure that Don’t
keep Activities option is not selected in Settings > Developer options screen.
You forget your OpenManage Mobile
password.
Workarounds:
To retrieve your OpenManage Mobile
password, tap Forgot Password. Your password
hint is displayed.
If you are unable to retrieve your
OpenManage Mobile password using the password hint displayed, delete
the OpenManage Mobile data, and then create a new password. To delete
the OpenManage Mobile data, go to Settings > Apps > OMM, and then tap Clear data.
NOTE: If application data
is deleted or application is reinstalled, you need to add the OpenManage
Essentials and iDRAC instances again to OpenManage Mobile.
Unable to retrieve
iDRAC data
OpenManage Mobile displays a connection
not successful message if you refresh an iDRAC details screen multiple
times to retrieve data.
Workaround: Refresh iDRAC Details screen after one minute.
If incorrect
credentials are entered while adding an iDRAC or while performing
power operations on an iDRAC, the iDRAC might disable all incoming
requests and appear disabled for some time. For more information about
this behavior, see iDRAC User’s Guide. iDRAC will be enabled
after some time. Wait till the iDRAC is enabled, and then retry the
operation with correct credentials.
VNC connection failed!
Error message “VNC connection failed!” is displayed
when you attempt to launch RDP session for an iDRAC if VNC RDP session
is already running or if another active bVNC session is running on
a different mobile device for the same iDRAC because iDRAC VNC only
supports one connection at a time. You cannot connect to the same
iDRAC using any instance of a VNC client, whether from the same mobile
device or a different device.
Workaround: Reset the iDRAC to establish the connection.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\