Profile manager Cannot enroll devices no more after server app update 3.0.2

same Problem here, whats going on?

I have installed the Mac Server 3.0.2 update too and now I have also MDM problems.

My existing managed iOS devices are not getting pushed updates anymore (Information request or Lock request).

When looking at the Profile Manager I see several active tasks waiting to start but they are not executed.

I tried to Add some new devices, but i get the 404.

i resetted the server tasks so i lost the device configuration. That didnt solve the Problem.

I'm having the same problem. Looks like it's a bug. We should probably all report it to apple support.

I called support on this and it has already been escalated to the engineering team.

I've fixed this on my server.

1. Make sure you have a working backup (just in case)
2. Go to your Network Settings and make a note of your DNS Server
3. Move the Server Application to Trash
4. Empty Trash
5. Go to your Network Settings and make sure you have a valid DNS Server (mine was set to use itself for DNS so I had to change it to Comcast's DNS Server)
6. Open the App Store and install the Server Application from your purchases
7. Open the Server Application, once it finished updating things, you will need start DNS
8. Go back to your Network Settings and change your DNS Server back to your server (or what ever it was before)
9. Go back to the Server Application and renable all your services (You may have to enable Push Notifications also)

I hope that helps some of you.

Forgot one thing, I'm not sure this helped but I also ran the command at the bottom of this KB article before doing the above steps: http://support.apple.com/kb/HT6043

I just had to start them again. Deleting the Server Application doesn't delete any of the services data.

The only issue I had was the calendar wasn't working after installing the Settings for Everyone profile. I found that it wasn't set to use SSL. So I turned off Calendar and Contacts Services (since they are the same backgroud service) went into Certificates and set the Calendar and Contacts to None, clicked Okay, and then set the Calendar and Contacts certificate back to my certifcate and restarted the services. After that I removed the Settings for Everyone profile and added it back to the Mac and everything is working now.

HI Hines,

I had the same problems after the 3.0.2 update: enrolling of devices not working, unable to push configurations from Profile Manager, etc.

The update was a simple 3.0.1 => 3.0.2 on already updated OSX Mavericks to 10.9.1 and it seemed that all was ok, not like this situation: https://discussions.apple.com/thread/5486733?answerId=24450438022#24450438022

Services used:

-Web

-Profile Manager with 20 iPads/iPhones already enrolled and with some in-house app pushed

I followed a solution similar to what suggested from Hines, apart from point #6. I was unable to re-download Server.app from App Store, greyed-out button.

So I was very happy to have another mac to download a fresh copy of Server.app.

Then:

-Deleted and thrashed the old version

-Message "all services stopped"

-Reboot

-Copied fresh "Server.app" to /Applications

-Started "Server.app" that made some initial auto configuration

-Services restarted

I just had to restart the postgres service and seems that I didn't lost any data/config (I hope, I'm already checking!)

=begin RANT

I know that Apple is essentially an hardware manufacter manly for consumer target now but that a simple minor update broke an entire software meant to be solid, like a server must be, is just plain unacceptable.

I know that OSX Server is very cheap and we can't pretend too much....but F**K...i loosed my sleep tonight!

=end RANT

If it's grayed out in purchases, try option clicking purchases.

Thank you for this.. It appears to have fixed the MDM enrollment error I was having. Did all the steps you suggested without doing the command line and it seems to be working.

Thanks Again!!

Thanks for your help to resolve this however this is a bit of a cumbersome way to resolve the problem. I worry it may happen again following future updates.

With best wishes, Julius

I did all the steps and at first it worked, but a few days have passed and I'm getting the 67693 Error again.

This really *****. 😟

For anyone that is using this in a local enviroment (ie dev server). If you have a dhcp assigned LAN address, if it changes it will cause this same issue. Just fixed this issue on my system after a network blip. Set my LAN to static and all is good. Did not have to restart any services.