The Reboot action will restart your device after the end of a deployment containing this action. This may be helpful at kiosks in single-app mode that could benefit from being rebooted nightly. Manually rebooting a device that’s connected to a Launchpad will kick off any Rules that are enabled. Shortly after, automatic deployments will begin. Rebooting a device using this GroundControl action, will … Read More
At the end of a deployment, GroundControl can launch a specified app that’s installed on a device. This action applies to pre-installed apps, Enterprise Apps and ones downloaded via MDM. If the app is being downloaded from MDM, you can set the criteria for how long to wait for the app to install. If using an Enterprise App, make sure to … Read More
Only available as an option with DEP Workflows. Using APIs, this action provides the ability to send specific MDM commands to DEP devices. The MDMs below provide the ability to delete/retire the device plus more.
GroundControl allows you to install Enterprise apps (aka “In-House apps”) on your devices. Enterprise apps are internally-created applications that are usually unique to your organization. This feature is NOT supported for public apps available from the App Store. Enterprise apps are already supported by nearly all MDM systems, but MDM requires that devices download the apps over the air. OTA installation may take … Read More
This action is available only in deploying to devices with iOS 9.3 and newer. You can now hide almost all of Apple’s default apps. Due to limitations imposed by Apple, you can not hide the Settings app or the Phone app. Select apps and click the arrow to move them to the “Hide these Apps” list. To select multiple apps, hold Shift or Alt (Win) or Command … Read More
Users are able to add Custom Options to their workflows, unlocking additional functionality when deploying. Please contact firstname.lastname@example.org for more information.
This action sends an API call to your MDM server to delete or retire devices . The call is made at the beginning of the deployment. This action is useful when migrating devices from one server to another. Only MDM systems configured for API integration can be unenrolled through this action.
Once you’ve created an MDM integration in Admin, you can add it to a workflow using the “Enroll in MDM” action. For the following MDM providers, GroundControl can do even more. When you optionally add API credentials, GroundControl will interact with your MDM before and after each deployment. AirWatch with API MaaS360 with API MobileIron Cloud with API MobileIron Core with API