Android group-level actions
You can use group-level actions to remotely issue commands to multiple Android devices at once.
After issuing commands, you can track the status of the actions in the Device history.
MaaS360® supports the following actions for various Android modes of operation:
| Action | Description | Supported matrix |
|---|---|---|
| Manage Android Devices | Reboot Devices: Reboots multiple devices at once. Users are not notified in advance that their device is being restarted. Any work that the user is working on is lost on the device. | Device Owner, Non-GMS (Android 10+ Agent 8.10+) WPCO (Android 11+ and Agent 8.10+) |
| Request Data Refresh: Refreshes the device information that is displayed on the Summary page in the MaaS360 Portal. It also retrieves the pending device payloads to synchronize and update the MaaS360 portal with real-time device details when the device comes online and has good data coverage. | N/A | |
| Copy File - Remote Server: Copy a file from a remote server to target devices. For more information, see Push Profile actions to managed Zebra and Bluebird devices. | Bluebird and Zebra Device Owner (DO) and Device Admin (DA) | |
| Push OS Upgrade - Remote: Starts an OS update on the device from a remote OS update compressed file. For more information, see Push Profile actions to managed Zebra and Bluebird devices. | Bluebird and Zebra Device Owner (DO) and Device Admin (DA) | |
| Android Custom Command: Sends custom commands for running dynamic actions on managed devices such as enabling a Kiosk, starting an app, or starting an activity. For more information, see Android custom commands. | Requires MaaS360 for Android app 7.40+ | |
| Android OTA upgrade: Deploys over-the-air (OTA) updates to corporate-owned devices. This command takes an OS binary image URL as an input and then runs the OS upgrade on devices. For more information, see Deploying OS upgrades to corporate-owned devices. |
MaaS360 for Android app 8.10+
|
|
| Migrate to Android Work Profile | Sends a migration request to an individual device or a group of devices to enforce Android Enterprise (PO mode) on those devices. Devices become out-of-compliance (OOC) if the migration is not initiated on devices within 90 days after the migration request is sent to devices. For more information, see Migrating from Device Admin (DA) to the Work Profile. | Device Admin |