JumpCloud policies can help you customize, manage, and secure devices in your organization. You can create a Mobile Device Management (MDM) enrollment policy to enroll existing macOS devices in MDM without using Apple\u2019s Automated Device Enrollment. <\/p>\n\n\n\n
You need to distribute and install your organization\u2019s MDM enrollment policy and users will then approve the enrollment profile. For more information, see Add Company-Owned Apple Devices to MDM with Device Enrollment<\/a>. Creating an MDM enrollment policy to do this saves you time and headaches.<\/p>\n\n\n\n
If your macOS device has been added to Apple Business Manager (ABM) or Apple School Manager (ASM) and the JumpCloud agent is installed, you can avoid wiping the device by following this procedure.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Prerequisites<\/strong>:<\/p>\n\n\n\n
To create a JumpCloud MDM Enrollment Policy for Mac<\/strong>:<\/p>\n\n\n\n
<\/p><\/div>
Devices enrolled in ADE should not be added to an MDM Enrollment policy. Adding ADE devices to an MDM Enrollment policy may result in unexpected behavior during policy deployments.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
After you create and apply a policy, the agent on an individual device continuously compares the local policy with the policy you created in JumpCloud. If a user modifies a device policy, JumpCloud automatically modifies the device policy to comply with the JumpCloud policy. This process ensures that JumpCloud policy and local devices are kept in sync.
Some policies take effect immediately while other policies may require an additional activation step, such as restarting the local system. After a policy takes effect, you can view the policy’s status or review the log file to determine if the policy requires additional attention.<\/p>\n\n\n\n
After you complete the JumpCloud enrollment policy described above, users must approve the MDM profile to unlock any user-approved MDM payloads.\u00a0<\/p>\n\n\n\n
<\/p><\/div>
Users must be bound to the device in the Admin Portal in order to be prompted to approve an MDM enrollment profile on the device.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Users need Admin permissions on their devices to approve the enrollment profile. If you want to later remove Sudo\/Admin privileges from the\u00a0user, see\u00a0Set Admin\/Sudo\u00a0Privileges<\/a>.<\/p>\n\n\n\n