One MacBook Pro. Completely re-imaged, fails all efforts to enable MDM. Multiple recons. Removed hard drive, swapped into alternate MacBook Pro, MDM successful. Original machine with error continues to refuse to install mdm with different hard drive.

Error as follows : Executing Policy MDM enable
Creating directory structure for /Library/Application Support/JAMF/Downloads/
Downloading http://jss.blahblahblah.noneya/CasperShare/Scripts/MdmUserLevel01.command...
Running script MdmUserLevel01.command...
Script exit code: 0
Script result: Getting management framework from the JSS...
Enabling MDM at the user level...
Error installing the user level mdm profile: profiles install for file:'/Library/Application Support/JAMF/CF926C2A-0670-4692-B4DF-E152ED13B630.mobileconfig' and user:'root' returned 1 (The operation couldn’t be completed. (InternalError error 1.))
Problem installing MDM profile.
Problem detecting MDM profile after installation.
Retrieving inventory preferences from https://jss.blahblahblah.noneya:8443/...
Finding extension attributes...
Locating applications...
Locating accounts...
Locating package receipts...
Locating hard drive information...
Searching path: /Applications
Locating software updates...
Locating plugins...
Searching path: /Library/Internet Plug-Ins
Locating printers...
Locating hardware information (Mac OS X 10.11.6)...
Gathering application usage information...
Searching path: /Users
Submitting data to https://jss.blahblahblah.noneya:8443/...
4392
The management framework will be enforced as soon as all policies are done executing.

We discovered all this after re-imaging, deleted the machine from our JSS and then attempted to recon it back. It does pull from our JSS and Self Service does work, but we can't manage the device. I will be contacting our rep tomorrow, to let him know.

FWIW, APNS is slow, from what we're hearing from Apple/JAMF, millions of kids returning to school this week, so commands queueing up and delayed. Tool several hours for a list of Configuration Profiles to install on a few test computers. Hope things speed up again by next week.

MDM Capability: NO

This worked for us.

Delete these folders:

/var/db/Configuration Profiles
/Library/Managed Preferences

Reboot
Login as admin
Open Terminal sudo jamf manage

Thank you, that did the trick.

Facing MDM capability = "No"issue post formatting any MAC. Prior to formatting, the machines are successfully getting enrolled with MDM capability = Yes. But when same MAC is formatted and enrolled again, we are getting MDM capability = No.
Please suggest a way ahead.

Same issue as ashish.more. Not sure what is going on here

Same problem here. Enrolled a quick lab of 30 machines, realized students could access system preference panes, mdm capable no on some machines but yes on others. In system preferences under profiles it gives the option to “approve” the mdm profile so I’m assuming this fixes it?

I’m saying assume because it can’t be approved remotely, it says it has to be manually on the computers mouse or trackpad. Ugh

Has anyone tried that and had success? I’ve run commands, been through multiple support emails but still no luck.

Hello @Howard.Trevor did you ever figure this out?

I have 124 out of 840 Macs showing as MDM capable no. I have a support ticket with Jamf support opened a few minutes ago. I was hoping to have bounced across a solution that doesn't involve me doing anything manually to these computers.

@mconners the only thing that worked for me was to unmanaged the machine, delete from jamf, run a quick Unix command from ARD, and then enrolled again with a quick add pkg.

My issue was apns problem. Renewed the certificate and for some reason it was saying it was the wrong one. Found that out 1 day before expiration, so I only had to fix anything that was enrolled during that 7 day period.

We run into this very occasionally with the odd machine. We are on-premise and ran into it in v9.98, and also now v10.3.0.

Support recommended renewing the APNS certificate. This seems a bit odd as the expiry date of the certificate is often in the next year, but this seems to resolve the issue (until it crops up again a few months later.....)