Problem: My device did not go through Automated Device Enrollment (ADE)
Reasons: Some of the reasons we have seen ADE/ABM to fail on unboxing experiences or when a device is re-provisioned.
- If you add a device into ABM using Apple Configurator, it "ties" the device to the "Apple Configurator" MDM Server, so when you rebuild you get an error saying "Cannot reach MDM Server" because its tied to Apple Configurator "MDM Server" which isn't a real thing, and unless your locally connected it will fail. Also, since its now tied to this server, only way to untie it AFAIk is to rebuild the machine, so easiest way to do this on the new OS is run through the wizard, go to System Preferences > Menu Bar > Erase all contents and settings > presuming its tied to Addigy MDM now and showing up in the Addigy console under Settings > ADE > Devices, it should register properly. Is this a bug? great question, but definitely seems like a janky implementation to allow us to retroactively register devices into ABM.
- A Network / Connection Issue is preventing the automated enrollment.
- Device was powered on before the device was associated to an ABM instance (Apple has done this in the factory sometimes)
- Do not turn on the device before registering it to the ABM MDM Server and it shows in Addigy.
- The device gets to hot.
- Make sure they connect to Internet before going through the wizard.
Pretty much don't let the user touch the device until its all ready to rock and roll, or let apple touch it, and then ensure there is minimal network connection problems. Sometimes it helps if you just open them up first and then ship them out to the user to ensure they follow the steps correctly.