A Mac missed MDM enrollment during setup
A Mac was and added to with on an iPhone. The Mac appeared correctly in after reaching the desktop, but MDM enrollment had not been set up during the first setup flow.
The Mac was later assigned to ManageEngine as its MDM in , and it also synced into ManageEngine. The practical problem is how to apply the new MDM without wiping the Mac again, because another reset would disrupt the employee using it.
The command `sudo profiles renew -type enrollment` is being considered, but the key question is whether it creates the same forced MDM enrollment as a or whether the user could remove it later. The field also shows “Off” with a red warning sign, raising a second question: whether the Mac is still tied to the employee’s personal Apple ID and how the organization can control device lock status.
Key points
- The Mac is already in , but MDM enrollment was missed during setup.
- ManageEngine was later assigned as the MDM, and the Mac synced into ManageEngine.
- The goal is to apply MDM without wiping the Mac again.
- `sudo profiles renew -type enrollment` may help, but the concern is whether the resulting enrollment is forced or removable.
- The warning raises concern about a personal Apple ID still being connected to the Mac.