Solved
Hi there,
We've recently found an issue with assigning DEP/ADE settings to some devices after they've been enrolled into ABM via Apple Configurator.
The devices show up in Meraki but the moment we assign DEP/ADE settings to the device, the device reaches the profile enrollment screen during Setup Assistant but failed with the below error.
This doesn't happen 100% of the time and isn't network related.
The behaviour we see is that once we see this error and go onto ABM we see that even though the Meraki MDM profile is assigned to the device, it unassigns after this error and is removed from ADE/DEP list on Meraki.
My suspicioun is that because we're trying to deploy the MDM to the device immediately after enrolling it into ABM using Apple Configurator, that there may be a Apple push cert issue. Might be that the device is rejecting the configs based on Apple cert not being assigned or provisioned to the device just yet. I have no means to confirm this, I'm not sure on how the backend of Apple Push propagate
So, once step that many people miss is assigning the device to a network when it appears in the ADE list in Meraki. This is a step unique to Meraki SM as it has the ability to partition SM into Virtual MDM instances:
You'll note that each device is assigned to a Network. You can do this in two ways
Either assign the devices to a network like this:
or ensure that there's a default network in Organization > MDM
So, once step that many people miss is assigning the device to a network when it appears in the ADE list in Meraki. This is a step unique to Meraki SM as it has the ability to partition SM into Virtual MDM instances:
You'll note that each device is assigned to a Network. You can do this in two ways
Either assign the devices to a network like this:
or ensure that there's a default network in Organization > MDM
