Hi,
We use 1 Jamf instance for multiple school facilities, sometimes a device needs to be moved to a different location within our Jamf instance.
Though since about 2 months ago, we are unable to move devices.
This is the error:
The device could not be moved because it is not associated with a server token in the main location.
Anyone have an idea what's going on?
I checked all our certificates, enrollment and purchase all valid
As this is involving server tokens you want to call Jamf. Maybe worth trying to renew enrollment on the devices with terminal and the profile command.
Sounds like you might have multiple DEP/ADE tokens in play? I tend to like one DEP/ADE token on the top level and let the device be automatically moved to location on enrollment.
Sometimes moving the device in DEP/ADE and resetting(iOS)/running some terminal commands(Mac) might be the easiest to move devices between tokens.
Does the device need to be moved to a different location in Apple School Manager first?
Does the device need to be moved to a different location in Apple School Manager first?
@ShawnNeal Shouldn't matter, the devices are assigned in ASM to an MDM through ADE token. If the device is visible in the list for the MDM token in ASM, it should also be visible after next ADE sync in Jamf School.
My guess is that the device in question is assigned to a ADE token used for one sublocation in Jamf School, and that there is another ADE token assigned to the top level. But only a check in ASM and then Jamf School would confirm this. Otherwise, Jamf support would probably fix this faster than a forum post, as AJPinto mentioned initially.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.