enrollments not completing today

I was out of office Monday-Tuesday, but noticed enrollment issues when testing workflows in both Test and Prod environments today. Depending on PreStage/workflow (NoLoAD vs Jamf pre-fill account), I can coax things through by cancelling Pending (and Failed? ... which is what was recommended by support team). Even aforementioned troubleshooting doesn't seem to be of benefit in all cases ... and definitely isn't scalable by any stretch.

I'm still seeing this problem on July 2. I can't enroll a device (MacOS) since it's stuck on "Waiting for Management Server" and "Connecting to Server". Technically I'm still in the service window time but if this has been going on since yesterday, I don't think it's going to get fixed by the closing of that window.

Edit: Seems service is backup it's now 10:21 UTC

I'm still getting the error

"There was a problem communicating with a push server"

Yep. Same here. It's very inconsistent. I'll have one iPad or Mac process a few commands then another device will error on everyone or it will process one then fail the rest. Fun stuff!

Do note that the maintenance event yesterday was for JCDS not this issue.

Nothing changed this AM. Issue persists. Jamf status page indicating everything operational ... so no taking ownership of this problem from Jamf at this point.

Also receiving this error when running Update Inventory command to my iPads.

We are seeing this issue. At this point I cannot complete an iPad enrollment! "There was a problem communicating with a push server"

Have seen slowness in completing enrollments since 6/29, since the 10.22 update. Gave up yesterday hoping that last night's maintenance would address this. Apparently things are now worse.

Have opened a support case. Agent tells me that only a few customers have reported this problem and it is unknown if it related to 10.22 or not.

We are now dead in the water...

Which Jamf Pro cloud region are you all on? Curious if they all have this issue or just one. We are on us-east-1.
Enrollments are obviously impacted by this issue, but also our normal daily commands like install app, update inventory, restart device, they all have high failure rate currently. "There was a problem communicating with a push server"

I was experiencing the same issue yesterday after a client reported it. My test VM would not enroll. Kept getting stuck in a loop at the Setup Assistant enrolling via DEP.
As of this morning, after the critical maintenance window completed, at first it was still giving me the same problem. But after shutting down the VM completely, deleting the existing computer entry in Jamf Pro, and booting it back up, it finally enrolled successfully and got past the Setup Assistant.

So, it's working now for me at least, but you may have to take some extra measures to get it to work again if you're still seeing the issue. I should note that in the past I've never had to delete an existing computer entry before to work around a DEP issue. It usually would just enroll and update the existing record.

@rafgar We're on us-east-1 as well. The support agent mentioned that it was sporadic and that people where affected in different ways by whatever this is.

The maintenance window specifically mentioned JCDS. I don't think it was intended to correct the issue we are all having. From what I could gather from the support agent they haven't narrowed down the issue and they were bringing more bodies into the mix to get it fixed quicker.

Still happening for us today as well.

https://status.jamf.com is showing they are doing some work on the issue this afternoon.

We're having the same issues you guys are all referencing. Zero response from JAMF. Our ticket: [ ref:_00D80cOw4._5000h1h1IBg:ref ] is just sitting there. Nothing. How many posts in this thread? Pushing 40 now and nobody from JAMF has said a word.

I've had to send my summer help home without pay. We've got 900 devices to get through which shouldn't take more than a few days, but at this point without word as to when we'll be back up and running I can't even plan. Not only is JAMF screwing up my very narrow deployment window but this is also throwing off my entire summer schedule.

has anyone tried this yet?

Symptoms: After enrollment begins the device simply hangs on connecting to your jamf pro url...

Fix

1. In Jamf Pro, go in to Settings > Global Management > Automated Device Enrollment, and click on Public Key.
2. Log into Apple School / Business Manager
3. In the sidebar, select Settings
4. Click into your MDM server
5. Edit
6. Under MDM Server Settings, upload the public key
7. Click Apply at the top
8. Click Download Server Token
9. Go Back in to Jamf Pro
10. Settings > Global Management > Automated Device Enrollment
11. Click on the specific Device Enrollment instance
12. Edit
13. Upload Server Token File
14. Upload the server token that was downloaded from Apple
15. Save

Only took 4 days to officially acknowledge.

@dptech While I'm not in the same kind of bind you're in I did struggle this week to keep a college intern busy because of this. Mindless busy work like cleaning keyboards is fun especially when you're the person that needs to come up with it!

@JoshRouthier Yep I just received a response from support saying they have updated the page. I had mentioned to him that this should be shown as an issue on that page especially with the growing number of affected customers.

Having this issue here as well - nothing works to get the machine enrolled. :/

Physical macOS 10.15.5 Automated Device Enrollment went well in PROD. VM in TEST environment also went through said workflow successfully. I'm calling things good ... for now at least.

@PE2000 I just tried your fix. Thanks for trying. We're seeing same errors as before.

Yes confirming I just enrolled a physical machine and all went well!

Please can you post which region you are on if you are continuing to experience problems with APNs? The Jamf Status Page shows a known issue with APNs on region us-east-1 but if anyone is in another region and experiencing APNs reliability issues, it would be useful for others to know.

@grahamrpugh We are us-east-1, known issue, I've been unable to deploy new devices since the 27th of June. I finally heard back from JAMF tech support yesterday but they mistakenly replied to someone else's ticket and didn't acknowledge this issue at all.

When we go to enroll a new device, we get to the remote management, the laptop just sits there saying it's connecting to the server over and over.

the log files show:

2020-07-03 14:29:57,509 [ERROR] [ina-exec-49] [lientCommunicationServlet] - Comm Device null. remoteip:[xx.xx.xx.xx],device:[MAC=7C:D1:C3:E7:FF:95,82:0D:41:E6:7B:80,7C:D1:C3:E7:FF:96,UUID=DB9B7EC1-8D03-5F12-BA2B-497956A18A81,NoSerial]

2020-07-03 14:30:01,170 [INFO ] [duledPool-0] [VppLicenseMonitor ] - Running license monitor

2020-07-03 14:30:29,673 [INFO ] [duledPool-0] [VppLicenseMonitor ] - License monitor completed after 28.5 seconds

2020-07-03 14:30:53,342 [ERROR] [ina-exec-34] [dmControllerProcessorImpl] - Exception parsing MDM request

com.jamfsoftware.jss.exceptions.operations.MDMActionCreationException: com.jamfsoftware.jss.mdm.actions.exceptions.DeviceNotFoundException: Unable to find device with management ID: e7b45d5f-285e-4ea1-9c57-71dc0608895b

at com.jamfsoftware.jss.mdm.actions.MDMActionFactory.createActionForRequest(MDMActionFactory.java:292)

at com.jamfsoftware.mdm.jss.controller.LegacyMdmControllerProcessorImpl.getMdmRequestAction(LegacyMdmControllerProcessorImpl.java:232)

at com.jamfsoftware.mdm.jss.controller.LegacyMdmControllerProcessorImpl.handleRequest(LegacyMdmControllerProcessorImpl.java:108)

at com.jamfsoftware.jss.mdm.enrollment.MDMController.process(MDMController.java:98)

at com.jamfsoftware.mdm.jss.controller.MdmToggleController.put([MdmToggleControll

I also was able to enroll a machine. I'm not 100% convinced this is completely fixed yet. We will test a ton on Monday.

@dptech I was able to enroll a machine and several iPads without any issues. Commands sent to existing devices also completed without failing. Looks like the issue has been resolved from where I'm sitting.