MDM Profile Unexpected Error <InternalError:1>

Is this a VM?

You will need to specify the model by editing the .vmx file for the virtual machine.

hw.model = “model_here”

Had this same error, turned out to be a duplicate user (username) in jamf, so the user could not be assigned to. check for duplicates, remove duplicate users, and try again. Worked immediately. Wish we had found this out before, because I spent $200 next day shipping a new laptop to this person, only for the same issue to occur when it hit DEP / MDM!!
:facepalm:
Note: you need fairly high level of permissions in jamf to delete a user, but it can be done.
Hope this helps!!

We are still experiencing this issue and don't have any duplicate usernames.

Hello everyone

Same issue here (with 2 laptops). I can't get the MDM profile to be installed
What I've already done: deleting the Mac from Jamf computers and deleting the user assigned
It seems there is no profile installed on this laptop anymore
Any help would be much appreciated
Best

Wasn't this also happening when a computer by accident ended up in the Devices group? Search for the serial number of the Mac under Computers and under Devices.

The devices list is empty. The S/N search gives no result
I found out another topic with the same error: https://www.jamf.com/jamf-nation/discussions/8066/profile-installation-failed

So for those of you that are still experiencing this, we resolved this by making sure their was an organisation name saved under the activation code window. It was an onprem instance and it somehow managed to not have an organisation name listed. Problem solved.

I've found that I've been getting this message if I try and re-enrol a device using an invitation link. either with a new link or one that I can use multiple times. I think this is a JAMF bug and we have a call open with them about this now.

I had the same issues with about 5% of my users, looks like it is a wifi issue, enrollment worked when devices were re-connected to a hotspot

I had to try enrollment again with a different browser, i think because okta was hooked into the browser since i enabled it for SSO and self service.

(then it worked right away)

This issue only showed up when someone tried to use Chrome for the initial profile download. I had them switch to Safari and it worked.

This worked for me always that's why I thought to share with you guys. 

I have deleted user device record from MDM  

Ask the user to re-enrol the device to MDM after deleting the profiles from preference by following the steps. 

In the Apple menu  > System Preferences, open the Profiles preference pane. 

In the left panel, select Self Service Configuration profile, and then click the minus (-) button to remove it. 

Restart your Mac then ask the user to re enrol it by URL.  

we are seeing this also on a machine where someone went thru the setup assistant before it was assigned an MDM, then they logged in with their apple ID making the activation lock.  We went into the apple id and icloud and tried to remove the device but it persists.  Now the Mac is assigned an MDM in ABM and when we boot, we get our remote screen, the Mac starts to enroll, Jamf binary loads but not self service.