This may be a stupid question but I am relatively new to managing computers with Jamf (only 5 managed so far). I have been testing enrolling my test MacBook Pro and unenrolling a few times to make sure everything comes down as we want it. Instead of unenrolling the device I decided to test out the "Remote Wipe" command in Jamf, which worked perfectly. However since reimaging (and reimaging a few times through the normal process, as well as unenrolling and re-enrolling) the Mac and when doing self enrollment or email enrollment I'm being asked to install the QuickAdd package instead of enrolling by installing the CA certificate and Mobile device profile.
This only seems to happen on this one computer, if I go to any other Mac it enrolls with the cert and profile. What is causing this one Mac to enroll with the QuickAdd package and is there anyway to configure which way a device enrolls? We did have a an image set up under Settings -> Computer Management -> Configurations, but we have since deleted it.
Solved! Go to Solution.
I had an odd one today where I could not for the life of me get a new 2018 MBP with Mojave enrolled into the JSS (10.9.0).
I ended up using the ?type=QuickAdd method, and it worked.
Only odd thing was this guy setup the new Mac (non-DEP) with a Time Machine backup to sparsebundle on an NFS share. User ID was a good 501 and has a securetoken. Not sure what the deal was, but once the jamf.log got to agent loading, it just halted. And the MDM Profile was approved, etc.
Sometimes it takes a step backwards to make something work... Thanks @claudiogardini for sparking a thought :)