we're seeing this as result to all commands (i.e. "Renew MDM profile") issued to all of our iPhones. Since they're currently in different locations all over the world a firewall issue is veeery unlikely.
We're on 10.23.0-t1595614145, Push Notification Certificate is renewed (though still Binary?)
Any help is appreciated.
Connection Settings Establish a connection to the Apple Push Notification service.
Protocol Apple will no longer support the binary APNs protocol. For more information, see the Supporting Apple Push Notification Service Over HTTP/2 Knowledge Base article.
edit: it works at least in one environment now. seems to be very slow everything in the moment
We were experiencing issues enrolling devices through DEP, manual enrolments and config profiles not deploying too so issues with APN's makes sense. We're in the EU region. I've successfully enrolled one Mac now so hopefully it's getting fixed now.
Is anyone else seeing this with manual enrolments at the moment? We can install the CA certificate, then install the MDM profile and then nothing happens after that. No configuration profiles, no Jamf binary and no self service app.
still experiencing issues with profiles not being pushed...
At least in Austria it seems to be stuck since Friday last week.
New DEP installed devices do not get most of the profiles we push.
Edit: we are on On-Prem v10.23 and use already the HTTP/2 (443) setting for connection. When testing I get an error.
I don't know if it's related, but I am trying to renew the ABM server token for our on-prem JSS and if I try to upload it says "the file received was not valid". The Automated Device Enrollment page in JSS says "Information out of date. Awaiting next sync"
Test with TwoCanoes "Push Disgnostic" seems fine (APNs tests completed with 63 passed and 0 failed)
@txhaflaire & @patrick030 Yes, we are facing the same issue. DEP enrollments are stuck on a loop, in our case directory binding is failing & after almost 10 minutes, the Computer hangs. We did a force reboot & again it gets in the same loop. When I check the computer record on Jamf, I see an Unmanaged entry & multiple failed commands for Directory Binding. Informed Jamf Support, waiting for their reply.
Thank you @patrick030 I tried cancelling the failed and pending commands, unfortunately that didn't work for us.
I had to disabled the Directory Binding payload from pre-stage & it started working last week. (as recommended by Jamf support on our case)
Today we are facing the problem again, though the AD binding is disabled.
Error message is: Push failed. Values for APN Token and Push Magic cannot be blank.
Is there anyone else facing this ?
I saw another thread: https://www.jamf.com/jamf-nation/discussions/36570/push-failed-values-for-apn-token-and-push-magic-cannot-be-blank
Still having the same issues as everyone else. Push notifications are not getting through to devices. Some do but but others do not. Apps are stuck in the 'pending' status and will not load. Hope this gets fixed soon.
Has anyone be able to get a hold of someone from Support with some real answers?
@jason.watts we were informed that (at least our profile push problem) is an issue with the current JSS on prem (10.23) we use.
And it is apparently resolved in 10.24. But since it is still in beta we did not install it on our prod environment.
I am not sure if this resolves the prestage problems too or if they are based on the same issue. We use no profiles for our prestage enrollments.
i get this information back from jamf: "I'm really sorry for the problems you've been experiencing and the manual work you've had to put in to make the workaround possible. At the moment however, there is no estimation yet concerning this PI and when it will be fixed. I'm afraid the only temporary solution is the workaround. I understand this is far from ideal. Again, my apologies for the inconvenience caused by this."
Just spoke to Jamf support who said this is not fixed in 10.24, but will be in 10.25. This is killing the setup of 2500 new devices and makes me question what we are continuing to pay for. If this is true, then its solely a Jamf issue and for them to wait on this and not issue a hot fix is truly disappointing since this most likely affects any new enrollment with DEP.
Princeton Public Schools
Jamf is premium product, and the price that we pay for per device is not justified with the various issues we are experiencing. Everything from inventory updates, APNS errors, etc. I think the quality of the product has drastically decreased with last 1 version of release (10.23.xx). Now it looks like Jamf is only focused on the IPO and the listing and the stock markets. Product quality/fixing errors is no more a priority.