anyone else experiencing issues enrolling Macs into JamfCloud?
so far it has occurred when using DEP, the profiles command, and manual enrollment through our URL.
The MDM profile will load and that's it. One Mac was previously enrolled into Jamf but hasn't been an issue before as we clear out enrollment records upon re-enrollment.
Same here! Had some issues with a test VM this morning. Eventually went passed enrollment after a few reboots. I didn't think much of it, I leaned more towards the VM being the problem. Later in the afternoon we needed to enroll a handful of iPads - stuck on configuration for at least 20 mins.
Unlike yesterday I now can't send any mdm commands on either platform this morning. All end up failed with the same message as above even after repeated attempts. Last I heard from support is that they're looking into it. Hopefully with some haste as this is slightly holding me up.
I prodded support more just a little while ago. Nothing definitive as it was stated it could be a product issue or something else altogether. Worrisome to say the least but I was assured QA is on it.
They should really update the status page as right now it's showing everything is operational and hunky dory.
Also submitted a ticket. I had two 2019 Macbook Airs I tried enrolling yesterday with the same issue - MDM profile gets added, workstation shows up in Jamf with pending commands and never finishes. I wiped and restored one machine yesterday and it still wouldn't enroll, but when I woke up both computers again today to try again, it miraculously finished. The second one still won't enroll no matter what. A bit annoyed that both Jamf and Apple's status pages are showing all services up right now.
Ticket in as well. It seems to be fairly random on how long it takes for Macs to eventually get a successful connection to the push server to complete mdm commands. Usually somewhere between 10 minutes and an hour, tho I've seen longer.
It's happening across different network types, different device types, different operating systems.
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
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.
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...