Yesterday I cloned out 9.22 into a sandbox and updated it to 9.23. Ever since the update, we can't enroll devices in MDM with the sandboxed machine.
It just reports: The computer was not enrolled in MDM with the JSS. The device certificate did not install.
I've tried these directions, but that didn't change anything. https://jamfnation.jamfsoftware.com/discussion.html?id=8836
Running 'jamf manage' just keeps reporting the same, and failing.
Anyone else seeing this? Any fixes found yet?
Did a webex with jamf support today. We couldn't find the cause of the problem, everything looks how it should. We're gonna keep working until we figure it out; they said they're heard of a bunch of cases of this happening on 9.23.
Is the MDM cert on the client? Can you see an apns token assigned to that device in the database? If both those pieces are in place the MDM should show as MDM capability Yes. If both those are in place and you are still seeing No than I would deduce a 9.23 issue. For shiggles... can you verify the status of your ports and any firewall/proxy on the sandbox? I assume no differences from your prod environment? You can still communicate with the APNS?
The MDM cert never makes it to the client - check the log snippet I posted in my thread:
Feb 7 15:45:16 testclient.local installd: ./postinstall: The computer was not enrolled in MDM with the JSS. The device certificate did not install.
Hello. Are all of the affected machines 10.8.x???
We had the same problem but it only affected ML machines.
We discovered that if the Mac had WiFi connected and the Ethernet port in use, it would never enroll.
We turned off the WiFi port, rebooted, ran sudo jamf manage, and the MDM enrolled just fine.
Has anyone tested this or had any success with Mavericks? I've been trying every suggestion I've gotten, including reenrolling with Wifi off as local admin, and it's still failing. QuickAdd fails, and jamf -manage just reports that the MDM could not be installed.