Posted on 03-05-2018 04:44 AM
Posted on 03-05-2018 09:51 AM
Did the computer already exist in your Jamf Pro Server? If it did, try deleting the computer from the Jamf Pro Server before going through the prestage enrollment process. Good Luck.
Posted on 03-06-2018 11:28 AM
I would go in and check the logs on the policies. Did the logs claim that the policy had already been run on that machine? If they attempted to run and failed, what error messages were produced? Is enrollment otherwise successful on the machine?
Posted on 03-06-2018 11:51 AM
I've also seen this in my recent transition testing to DEP. It seems like it's not running a full recon of the computer on DEP enrollment, sort of just putting a place-holder in for me. The end result is that if I don't pass a
sudo jamf recon
once it boots, policies that are scoped to all computers excluding, say 10.13 if it's a new 10.13 box, apply to it.