JumpCloud Agent / MDM Enrollments

This incident has been resolved. To enroll devices again, customers can follow the below steps:

ADE-enrolled devices
If you have devices configured for ADE there are two options to restart the ADE enrollment;
Administrator Privileges Required* see: https://jumpcloud.com/support/set-admin-sudo-permissions
Setup a command to execute `sudo profiles renew -type enrollment`
Or
Have your users execute `sudo profiles renew -type enrollment` in a terminal window
In both scenarios the user will be prompted to complete the re-enrollment of the device. This action will require the user to have administrator privileges on the device, at that time.

Non-ADE enrolled devices
For devices that are not configured for ADE enrollment it is advisable to apply the JumpCloud MDM Enrollment policy (https://jumpcloud.com/support/create-a-mac-mdm-enrollment-policy). Note, this still requires the user to have administrator privileges to complete the MDM enrollment when they complete the enrollment process. Admin may temporarily elevate standard users to admin users by following the steps laid out in this article: https://jumpcloud.com/support/set-admin-sudo-permissions.

Additional Support Articles for Remediation
https://jumpcloud.com/support/re-enroll-apple-devices-into-mdm-and-preserve-device-record
https://jumpcloud.com/support/set-admin-sudo-permissions
https://jumpcloud.com/support/create-a-mac-mdm-enrollment-policy

We've identified the issue and implemented a fix. Users that were un-enrolled from Apple MDM may need to re-enroll their device. More information on re-enrolling Apple devices can be found below:
https://jumpcloud.com/support/re-enroll-apple-devices-into-mdm-and-preserve-device-record

We are currently investigating an issue with agent installs and Apple MDM enrollments. We will update this issue as we know more.