Push failed. Values for APN Token and Push Magic cannot be blank.

same here.

First we had this issue: https://www.jamf.com/jamf-nation/discussions/36546/there-was-a-problem-communicating-with-a-push-server
And since it is resolved, I see the same error message in our environment.

It looks like that the problem was solved from Jamf support some minutes ago for us.

Update issue still NOT solved!

Same problem here today!

Same problem here, I have a case open with Jamf.

Also experiencing this. Incident ticket opened with Jamf.

Update: Someone on the MacAdmins Slack workspace shared the following workaround: In the JSS, hit Cancel on the following failed command: DeviceConfigured.

@sim.brar yes that correct. there is another discussion for this topic where i already posted the "workaround": https://www.jamf.com/jamf-nation/discussions/36546/there-was-a-problem-communicating-with-a-push-server#responseChild206007

Same issue for me since yesterday, working with the jamf support on it but still not soilved

My first ever pre-enrollment test was today, and I have the same issue. My boss wants to factory reset, and re-attempt when this is resolved, since nothing that was supposed to install happened. But since it now exists fully in Jamf I'm unclear if this is even possible. That ship has sailed yes? Can we perform a valid pre-enrollment test after the laptop has been added to Jamf already?

I just did a manual Recon adoption and had the same problem. I have a case open. Looks like I can't adopt anything into Jamf at the moment. At least not "fully".

is it working for everyone now? What did the Jamf support say?

Still not working for me, waiting for jamf support feedback

Workaround which works for the moment, from the JamF Support :

Could you please skip the enrollment at the setup assistant with the next device you will enroll (Other network options -> My device does not connect to the internet) and execute following command from the desktop: sudo profiles renew -type enrollment

@JamelB valid workaround and i´m pretty sure this will work.
The problem is that we have designed a nice "zero touch" enrolment and tomorrow is onboarding day and we have to manage remote onboardings as well...i cant tell newbies please open terminal and enter the command (some of them never used a mac)...
I cant understand why this problem is still present, i reported this already early last week to jamf.
I´m a bit frustrated at the moment with the handling of such important topics.

Holy cow this is still an issue? We have fac arriving today having issues. How has this not been solved?

Update: In the JSS, hit Cancel on the following failed command: DeviceConfigured.

The problem with the so called workaround (hit cancel on DeviceConfigured) is that the Kerberos SSO deploy still fails. It appears in Profiles as a blob of XML instead of the way it's supposed to, and no menu bar key symbol ever appears. Also, one of the Jamf Profiles doesn't install. The system does appear in Jamf, but it's not adopted fully. The sudo command does not seem to address Recon enrollments. And if Jamf has workarounds they did NOT annotate my open ticket as such.

Still same issue for me today, waiting for JamF Support... Do you have any answer on your side ?

Same problem still here. (West Europe cloud)

Process , looping while enrolling.

Chiming in here with the same issue. The "workaround" got us hobbling along until the issue is fixed. Thanks so much @sim.brar and @patrick030 !

@JamelB no, i have also no feedback on my request.

Best workaround is clearly to use this. I was able to enroll some devices today with this process.
Please note you may have to click "Cancel All" multiples times refreshing the web page for the enrollement to continue on the device. I searched the device per SN in JamF. The name in JamF should be "DEP - SERIALNUMBER".

What would set the names to DEP - serialnumber? None of mine are set to that. Using Cancel All may get them to appear in Jamf, but they are fundamentally broken on the client side so it's hardly useful. With missing and/or broken profiles.

In case anyone is stilling working at this and hasn't opened a case, PI-008754 was the product issue I received from support, though it doesn't appear in the Known Issues just yet.

I got:

In regards to the enrollment issue, the Jamf Pro Server log is confirming that what is being encountered is a known issue we have filed as PI-008661. This is reported fixed in an upcoming release of Jamf Pro.

And they would not say when it's getting pushed, but they marked my case inactive.

Hi everyone,

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."