BLUF: ASM shows 314 devices assigned to our Jamf Pro (cloud) server, but Jamf Pro is stuck at a 255-device count, preventing macOS Tahoe's native migration lockout from triggering for 50+ migration targets.
Hi everyone,
I’m running into a sync issue between Apple School Manager (ASM) and a new Jamf Pro instance. For backstory, we are migrating from several independent Jamf Cloud installs to a centralized version. While many of the devices will need to be manually touched, I have more than 50 that can be migrated between Jamf instances. Those devices are on Tahoe, have a T2 chip on Intel hardware or are Apple Silicon, and are DEP enrolled with a valid MDM Profile (not expired) on the legacy Jamf instance. I successfully migrated a separate Jamf Cloud instance into our new, centralized Jamf instance using ASM just a week ago, so the process has proven valid.
Currently, ASM shows 314 devices (all endpoint Macs save for 5 iPads) assigned to our MDM server via Device Management Services. However, Automated Device Enrollment settings in Jamf Pro are stuck at 255. I've specifically assigned our devices to to the correct Device Management Service and have assigned deadlines that have passed, yet endpoints that are on macOS Tahoe in our legacy Jamf instance do not get the expected full-display hijack from Apple stating that device management has changed.
The Question:
It feels like a stale sync issue where Jamf isn't performing a full reconciliation of the ASM library. Am I on the right trail? For that matter, has anyone else run into something like this? Some other suggestions in the Jamf community were to simply re-download the Server Token File (.p7m) from ASM, then upload it back to Settings -> Global -> Automated device enrollment. Naturally, I was leery about the notice that downloading a new token will reset your existing one/ramifications on the existing devices we have enrolled in our new instance.
Thanks for any insight!