The workflow to enroll an existing Mac changed slightly beginning with Big Sur (11), and again in macOS Ventura (13). If you're running macOS Sequoia (15) or later, please use this guide. If this is a brand-new Mac, then it should enroll via Zero Touch.

Before enrolling your Mac, please make sure you don't have an existing MDM on your device. Check for this by visiting:

• macOS Monterey & earlier: System Preferences → Profiles
• macOS Ventura & Sonoma: System Settings → Privacy & Security → Profiles
• macOS Sequoia: System Settings → General → Device Management

If you don't see any profiles (or a Profiles section at all for macOS Monterey and earlier), you can skip to the next section on enrolling. If you do see an existing MDM Profile, you may need to remove it by selecting it and clicking the minus button (see below). This requires administrative credentials to approve. You can usually identify your enrollment profile by name, the number of settings (generally 3), or the fact that the minus button will be interactive when it is selected. Most other profiles will not allow you to click the minus button:

macOS Big Sur & Monterey (11-12)	macOS Ventura & Sonoma (13-14)

How To Enroll - Video

Scroll down beyond the videos for written instructions with screenshots.

1. Use your favorite browser to download the custom mobile config file provided to you by Ntiva (this file is unique to your organization — or your client organization).
   
   
   
   
2. Open System Preferences, then click Profiles (often the last icon) to Install the profile. You'll need to enter your Mac Admin credentials. Note that this video details the macOS Monterey workflow:
   
   

How To Enroll - Written Instructions

Once any existing MDM has been removed, proceed with the following to get enrolled:

1. Download the custom mobile config file provided to you by Ntiva (this file is unique to your organization — or your client organization). Once it has been downloaded, you should see this notification:
   
   
2. Navigate to the Profiles list:
   
   

   macOS Big Sur & Monterey (11-12)	macOS Ventura & Sonoma (13-14)
   Click on the Apple Menu () and select System Preferences Click on the Profiles button	Click on the Apple Menu () and select System Settings Click on the Privacy & Security tab, then the Profiles button at the bottom

   
   
   
3. Locate and install the new profile:
   
   

   macOS Big Sur & Monterey (11-12)	macOS Ventura & Sonoma (13-14)
   Highlight the new profile, then click the Install button on the right side	Double-click the new profile

   
   
   
4. Confirm your selection:
   
   

   macOS Big Sur & Monterey (11-12)	macOS Ventura & Sonoma (13-14)
   Click Install	Click Enroll

You'll then be asked for your administrative credentials. Once complete, you'll see additional MDM Profiles install, and the Ignore/Install buttons will be gone:

macOS Big Sur & Monterey (11-12)	macOS Ventura & Sonoma (13-14)

NOTES

1. Once downloaded, the profile will only be visible in System Settings/Preferences for 10 minutes, so please perform all the above steps in one sitting. If you wait and the profile is no longer visible, you should be able to find the .mobileconfig in your Downloads folder. Double-click it to proceed with the above steps.
   
   
2. On a Mac with Apple silicon you may see a warning that reads:
   
   This MDM server requests the ability to manage kernel extensions and software updates. To allow this reboot into Recovery and enable MDM management in Startup Security Utility.
   
   This warning will only appear on manually enrolled Macs — our preferred enrollment method, Zero Touch, will not present this message. If you're an Admin and have physical access to this Mac, it's a good idea to get this done, but it's typically not required. Performing this action is necessary if you run software that uses legacy kernel extensions. See, Change security settings on the startup disk of a Mac with Apple silicon for details, and be sure to:
   
   
   • Click the radio button for Reduced Security.
   • Then check the two boxes:
     • Allow user management of kernel extensions from identified developers.
     • Allow remote management of kernel extensions and automatic software updates.