Unable to connect to the MDM server for your organisation.

When reinstalling MacOS I run into issues in the Remote Management section during installation. After establishing a network connection, I proceed to the Remote Management section of the installation and the setup is failing with an error "Unable to connect to the MDM server for your organisation.". Is there any way how I can resolve this issue manually? Because there is no way how to bypass this step in the setup.

  • I ran into the same issue. I ended up erasing the mac and installing the macOS again and it solved the problem.

Add a Comment

Replies

I would start with ensuring that your MDM server can access all the necessary ports it's looking for. These should be listed in the server documentation. The big ones are 443, 2195, 2197, and 5223. These are the ports Apple communicates with the MDM server over. Any of these being inaccessible is usually the cause of your error.

If these ports, and others your MDM may use, are functioning properly on your server then you may want to try monitoring the Mac's network activity with a tool such as Wireshark to determine at what point communication is failing on its end.

I have the same issue, after enrolling devices with Apple Configurator 2 into ABM and our MDM. No clue what could be the reason, our Network is not the reason, other DEP devices can enroll without issues.

Post not yet marked as solved Up vote reply of zett Down vote reply of zett
  • Having this exact same setup and issue. The device is picked up by ABM, then synced to the MDM without issue, but during activation on the Mac it just says "Unable to connect to the MDM server for your organisation". Tested connectivity to MDM from same network with my iPhone and having no issues there.

Add a Comment

Any solution to that yet? We use Intune / Endpoint

I've tried opening all ports and it still does not work. What I dont know if it depends from the time and date, as my time is not correct when trying to continue after the "Remote Management" page.

I would also love to see a solution. I'm having the exact same problem.

A solution would be nice, but a way to trouble shoot the issue would be satisfactory too. A generic error message isn't very useful without details.