Not quite. There needs to be a communication between the JSS, client and APN.

Vote this up: https://jamfnation.jamfsoftware.com/featureRequest.html?id=4619

@bpavlov is spot on. Unless you are manually hand installing a profile by downloading it manually to a local client (or using the profiles command) you are using standard MDM commands (which requires APNs communication).

What @bpavlov is requesting in his feature request is the ability to have Casper lay on the profiles locally in a managed manner (instead of through standard MDM channels). An interesting concept for sure, but we shouldn't need it. Apparently after the likes of today though, we might.

APNS and CP's seem to be back to normal this morning.

My 10.11.4 test mac which was not applying CP's until reboot yesterday is today applying instantly, if anything it's the fastest i've ever seen a CP apply and take effect (moving the dock for visual test)

Same here. Config Profiles are working again! For what it's worth, I was having trouble applying profiles to multiple versions of Mac OS X, including 10.9, 10.10, and 10.11.

Same here as well. The Config Profiles are working again across 10.10.5, 10.11.3, and 10.11.4.

Guess I can mark this as an "Answer", just so others know what all went down, but it was more or less a group effort of yelling at Apple. So the general thought is that Apple APNS service went down yesterday which broke the MDM push capabilities. However, this morning myself and others have found that the config profiles are applying again across multiple OS X versions. I can confirm that my problem 10.11.4 is now successfully working.

We are having this issue with a new Macbook that we updated to 10.11.4 BEFORE joining it to Casper, and although the JSS says the profiles and policies were applied, they are not displaying in the Macbooks System Preferences, nor are the policies applying to the system. There is obviously something in the 10.11.4 update that is blocking Config Profiles and Policies deployment from Casper.

If the system was NOT on 10.11.4 (on 10.11.3 or earlier), policies applied fine.

So, Houston (JAMF) looks like Apple slipped on by you that you now have to catch up to w/ a new release ASAP.

@dnevius what happens if you do "sudo jamf mdm" on that computer?

I was going crazy yesterday trying to figure out what was going on. I wish we could find out!

Props to @blackholemac as this is probably what happened.

Same issue as yours.

I tried a lot to figure this out, and i found:

I think there is a bug in 10.11.4 which from MacBook Air 2015. If I use 10.11.3 instead of 10.11.4, there is no problem for enrolling to JSS.

Just tried on MacBook Air 2013, Macbook Air 2015 and MacBook Pro 2012 , work fine.

I do not think it is about APNS. because at the same time, the capper image with 10.11.3 works, the 10.11.4 does not work. they all use the same configurations.