DEP devices and “Manage with GroundControl”

Created: Modified: Knowledge Base

Before GroundControl 3.5, we permitted you to treat DEP devices as non-DEP devices, simplifying your workflows. Beginning with GroundControl 3.5, however we are enforcing several new constraints. DEP devices must now use DEP workflows.

So if you see the following failure:

Failed: The device is registered for DEP. Please use one of GroundControl’s DEP workflows instead.

…here are some options to try.

Option 1: Use the DEP portal to remove the device from your MDM server

If you have access to your company’s DEP portal, and have only a few devices in DEP, this is the simplest solution. Log into https://volume.apple.com and enter the DEP web app. Search for the device serial number. Then set the device to use no MDM server. This will keep the device in DEP, but will skip DEP registration when activating the device.

Option 2: Use MDM to remove the device from an activation profile

This option is possible on certain MDM systems, such as AirWatch and MobileIron. Log into your MDM server, find the DEP section, and “Unassign Profile” for the device.

Option 3: Change your workflow model to “Manage with DEP”

In edit mode, you’ll be able to update your workflows and switch to a DEP workflow model. For this to work, ALL your devices need to be in DEP. If you upload our supervision identity into your MDM’s DEP profile, you can perform every action that you could with the legacy “Manage with GroundControl” model, including restoring from a backup.

Option 4: Enable GroundControl’s legacy activation to ignore DEP

This option will use GroundControl’s legacy behavior to ignore DEP. It has certain drawbacks, however, such as frequent errors when activating an erased device. In your workflow, add a custom option, with the following text:

{ "ActivationPreferredMode" : "Legacy" }

Apple may not support this mode in the future. Also note this custom option is not supported for iOS 11 devices.