@jhein Check this thread

Why not 9.82? Is there something stopping you from updating to the latest JSS version? I'm not saying that is definitely the issue, but it would be worth seeing if using the latest 10.11 approved Casper Suite version will resolve this for you.
We only just began playing with 10.11.4 today, so I'll need to see if we see a similar issue. We're on JSS 9.82.

EDIT: Ok then, nevermind. Looks like there is some issue with 10.11.4. Oy Apple!

Yes, I am seeing similar behaviour. I haven't had the chance to diagnose it properly but so far I saw 3 MacBooks that our support guys rebuilt to 10.11.4 and enrolled today that would not have any profiles pushed to them despite being in scope and showing as "pending".

Thank @bentoms, will bookmark that and look into it.

@mm2270, No real reason for not updating the JSS, just had not gotten to updating it yet. I am going to try on some 10.10 Macs first before doing that but will keep that in mind. If you could reply back with your finding after playing around with it, that would be awesome!

Thanks @bentoms !

I am also seeing this issue.

Same thing for me, JSS 9.82.

10.11.4 - Add CP to scope and nothing happens on the Mac. Reboot and it applies
10.1.5 - Add CP to scope and the profile gets delivered but does not take effect until a logout/login.

Not sure when this started happening though.

Just tested again after posting and now 10.10.5 works as expected.

Add or remove a CP for a Mac and it instantly gets applied/removed.

exactly the same issue here!
JSS 9.82 and OS X 10.11.4, no profiles applied...

Seeing the same here across all of our builds..
JSS 9.82

OS X 10.10.5 - Production net new devices pull no config profiles.
OS X 10.11.3 - Test build, no CP's.
OS X 10.11.4 - Test build, no CP's.

Any more news on this?

It is looking like, from other posts and what has been said here, that it is an Apple issue. I have not tested out 10.10 builds yet, am getting ready to, but did notice that on the 10.11.4 the MDM Capable is set to "No" when I check the machine in JSS, so maybe something was changed with how the MDM is setup in 10.11.4.

Just tested 10.10.5, and it pulled profiles down like a champ. So it looks like it is more 10.11.4 that messed everything up... Way to go Apple.....

Just checked that setting across all of the OS X builds mentioned above.....any net-new device that we image comes up as 'MDM Capability: NO' no matter the version of OS X.

Following the other post referenced above but will updated this thread too...basically a me too, but occurring randomly and updated to note that our Apple SE acknowledged an issue on Apple's end but had no other immediate details.

I can confirm that after reimaging a test machine with 10.11.4 that it gets our MDM profile and a couple others, but after creating a new test CP it has not yet applied. JSS running 9.82. After restarting the machine the profile got applied.

@aporlebeke My "occurring randomly" in my post above can be best described by your post only it occurred on a freshly reimaged 10.11.3 MacBook. I blew the MDM profile out of System Preferences--->Profiles pane and ran sudo jamf mdm and it loaded all fine, but on one or two MacBooks running same 10.11.3 image, that doesn't work.

No answers but at least someone else is seeing what I thought was my unique issue. Waiting on Apple for a fix it looks like.

@aporlebeke That's my experience too. Devices enroll and get the JSS MDM, but others don't hit the box.

Devices also show "MDM Capability: Yes" in inventory.

Well, I guess it's a good thing it's only March and we don't have to worry about sealing up our image just yet. Hopefully there aren't any new issues like this when the fix this in 10.11.5 ...

Seeing much the same result. We just finished imaging a number of our labs and had a tough time getting our CPs to apply. Reboot fixed them sometimes, but it's been a bumpy ride.

I hope 10.11.5 isn't the fix...we'll need something much sooner than that. Things were working just fine in 10.11.3 two weeks ago.

I hadn't updated my base image yet to 10.11.4 yet and have little plan to until Apple gets this under control.

Blackholemac

So this is interesting. I've been able to confirm this issue on my personal laptop running 10.10.4. I've restarted once and I still haven't gotten the new config profile ... so is this a larger Apple issue and not just isolated to 10.11.4?

It is definitely larger...10.11.4 isn't even in our workflow yet...it shouldn't need to be...haven't had a full chance to vet yet.

I personally think APNS has a cluster node down somewhere for what it's worth.

... and yet it works when I push to some hard-wired machines ... what is going on??

Its probably not your network...I was reimagine using thunderbolt Ethernet dongles...I had the problem there too..given the sporadic nature of this problem a node, cluster or group of cluster nodes on APNS about has to be down.

@blackholemac but I thought config profiles came directly from the JSS to clients and did not require APNs?