In order for your Mac to be supported by Ntiva, it must first be enrolled. If you're running an older version of macOS please use this guide. If this is a brand-new Mac, it should enroll via Zero Touch - if automated enrollment did not occur, for any reason, follow this guide.
Before enrolling your Mac, please make sure you don't have an existing MDM on your device. Check for this by visiting:
- macOS Sequoia: System Settings → General → Device Management
- macOS Ventura & Sonoma: System Settings → Privacy & Security → Profiles
- macOS Monterey & earlier: System Preferences → Profiles
If you don't see any profiles (or a Profiles section 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 Ventura & Sonoma (13-14) | macOS Sequoia (15) and newer |
How To Enroll - Video
Scroll down beyond the videos for written instructions with screenshots.
-
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).
- Open System Settings, then click Profile Downloaded. Double-click the enrollment profile and click Enroll. You'll need to enter your Mac Admin credentials. Note that this gif details the macOS Sequoia workflow:
How To Enroll - Written Instructions
Once any existing MDM has been removed, proceed with the following to get enrolled:
-
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:
macOS Ventura & Sonoma (13-14) macOS Sequoia (15) and newer
-
Navigate to the Profiles list:
macOS Ventura & Sonoma (13-14) macOS Sequoia (15) and newer - Click on the Apple Menu () and select System Settings
- Click on the Privacy & Security tab, then the Profiles button at the bottom
- Click on the Apple Menu () and select System Settings
- Click Profile Downloaded on the left. If that is not visible, click on General and then Device Management
-
Locate and install the new profile:
macOS Ventura & Sonoma (13-14) macOS Sequoia (15) and newer - Double-click the new profile
- Double-click the new profile
-
Confirm your selection:
macOS Ventura & Sonoma (13-14) macOS Sequoia (15) and newer - Click Enroll
- 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 Ventura & Sonoma (13-14) | macOS Sequoia (15) and newer |
NOTES
- Once downloaded, the profile will only be visible in System 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.
- 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.
Comments
0 comments
Article is closed for comments.