Corporate-owned devices without Google Mobile Services
You can use MaaS360 to manage Android devices in countries where Google services are not available or on devices that use Google Mobile Services (GMS)
What are non-Google Mobile Services (GMS) devices?
Non-GMS devices are Android devices that do not have preinstalled Google services that include applications like Google Mail, Google Maps, and Google Play Store. This setup might be due to regional restrictions, the manufacturer choices, or the custom operating systems.
- Devices that are shipped without GMS. For example, the Amazon Kindle.
- Devices that are connected to a closed network where they cannot communicate with GMS.
What is Android Debug Bridge?
The Android Debug Bridge (ADB) is a command-line tool that communicates with Android devices that are connected to your computer. ADB is a part of the Android Software Development Kit (SDK), and it enables the developers to interact with the Android devices. The developers can install and debug apps, and can also access the device shell. The ADB tool helps to enroll corporate-owned non-GMS devices into the MaaS360 portal.
Enrolling non-GMS devices
The following step-by-step instructions help you to enroll non-GMS devices by using a QR code and by using the ADB tool.
Enrolling non-GMS devices by using a QR code
- From the MaaS360 Portal Home page, navigate to .
- Click Other Enrollment Options and select . The Android Device Enrollment wizard is displayed.
- In the Enrollment mode section, select a QR code.
- In the Device management section, select Device Owner without Google Managed Services (Non-GMS). For information about other enrollment settings, see Choosing the enrollment method using Android Device Enrollment Wizard.
- Click Create. The QR code is generated.
As an administrator, you can either enroll the Android devices, or download and share the QR code with users to allow them to self-enroll their devices.
Enrolling non-GMS devices by using the ADB tool
- Prepare your Android device and computer.Important: Enable USB debugging in the device, connect to a stable network, and connect the device to your computer using a USB cable. On your computer, install the Android SDK Platform-tools package and verify that you can access the ADB commands.
- Download the JSON script from the MaaS360 portal.
- From the MaaS360 Portal Home page, navigate to .
- Click Other Enrollment Options and select . The Android Device Enrollment wizard is displayed.
- In the Enrollment mode section, select Android Debug Bridge.
- In the Device management section, select Device Owner without Google Managed Services (Non-GMS). For information about other enrollment settings, see Choosing the enrollment method using Android Device Enrollment Wizard.
- Click Create. The JSON file is generated.
- Download the latest MaaS360 for Android app (APK file).
- Run the following command to verify that your device is connected:
adb devices
Note: If the list of attached devices is blank or shows unauthorized, you must enable USB Debugging and accept the connection when prompted on the device. - Run the following command to install the latest MaaS360 for Android app (APK file) on the
device:
adb install -r <path of the downloaded APK file>
For example,
adb install -r C:\Users\MaaS360\Downloads\7.50-600-release.apk
- Run the following commands to enroll the device:
- Enter the ADB shell:
adb shell
- Set MaaS360 for Android app as the device owner:
dpm set-device-owner com.fiberlink.maas360.android.control/com.fiberlink.maas360.android.control.receivers.Maas360DeviceAdminReceiver
- Run the following single-line command to push the content from the JSON file that is downloaded
from the MaaS360 portal to the device as specified in Step 2,
am broadcast -n com.fiberlink.maas360.android.control/com.fiberlink.maas360.android.control.receivers.MaaS360ADBReceiver -a com.fiberlink.maas360.android.PROVISION_VIA_ADB –es EXTRA_ADB_PROVISION_JSON ‘<YOUR MAAS360 JSON CONTENT>’
For example,
am broadcast -n com.fiberlink.maas360.android.control/com.fiberlink.maas360.android.control.receivers.MaaS360ADBReceiver -a com.fiberlink.maas360.android.PROVISION_VIA_ADB --es EXTRA_ADB_PROVISION_JSON '{"disallow_enrollment_skipping":true,"enrollment_corp_id": "01000100","enrollment_account_type": "deviceAccount","ae_container_type":"NON_GMS_DEVICE","android.app.extra.PROVISIONING_LEAVE_ALL_SYSTE M_APPS_ENABLED":false,"ae_enrollment_flow":"ADB_ENROLLMENT","enrollment_request_mechanism": "useAdvanced","enrollment_ownership": "Corporate Owned","android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.fiberlink.maas360.android.control/com.fiberlink.maas360.android.control.receivers.Maas360DeviceAdminReceiver"}'
- Enter the ADB shell:
- Start the MaaS360 app and complete the device enrollment process.
Tracking non-GMS devices in the MaaS360 Portal
After enrollment, the container type for the non-GMS devices is displayed as Device Owner - Non GMS on the Device Summary page.

Advanced Search
MaaS360 helps you to filter non-GMS devices and create a smart device group with the advanced search option.
- From the MaaS360 Portal Home page, navigate to .
- Use the following search criteria:
- Hardware Inventory
- Container Type
- Equal To
- Device Owner - Non GMS
- Click Search. The Search Results page is displayed.
- Click Create New Device Group. The Device Group Details window is displayed.
- Provide details about the new device group, including the name, description, and whether the group is public or private, and then click Save.
The app feedback channel is extended to the Non-GMS devices which collects the feedback that is received from the configuration settings and sends it directly to the IBM MaaS360 portal.
Unavailable features
The following features that rely on GMS are unavailable in the MaaS360 Portal.
Realtime notifications
MaaS360 uses push notifications to run remote actions in near real-time on GMS devices. Push notifications are not supported in environments where GMS is unavailable. MaaS360 relies on the device heartbeat to run tasks, which might take up to 4 hours to complete.
App management
Google Play apps, Private channel apps, and web apps for Android Enterprise are not supported. You can deploy Enterprise apps for Android and web apps (non-Android Enterprise) through the App catalog.
- Managed app configuration
You can use app configurations to remotely push configuration settings for Enterprise apps.
For more information about setting up app configurations in MaaS360, see Setting up app configurations.
- Android OEMConfig
You can use Android OEMConfig to remotely deploy OEM-specific settings to the non-GMS devices.
For more information on using OEMConfig apps to apply advanced configuration policies in MaaS360, see Using OEMConfig apps to apply advanced device configuration policies in MaaS360.
MDM policies
The following MDM policy is not supported:
- Enable Device Attestation
Device Actions
The Distribute App action supports Enterprise apps only.
The following remote device actions are not supported:
- Enable App Config Status
- Force App Config Feedback