Enable Intune for multiple agent installations, allowing for automatic deployment of the Atera Agent on numerous Mac devices enrolled in Microsoft Intune. This lets you roll out the agent across your managed Macs without manually installing it on each device.
Note:
- Installation via Intune is available for Windows and Mac devices. To install the agent on Windows devices, see Install the Atera Agent using Intune.
- Unlike the Windows .msi flow, Intune doesn't offer a native deployment path for the Mac agent. You can deploy it by wrapping Atera's Mac install command in a shell script (recommended) or by uploading the .pkg installer as a line-of-business app.
- Silent installation is available for macOS agent versions 1.8.5.7 and later. The .pkg installs silently by default - no command-line argument is required.
- On Apple silicon (M-series) Macs, Rosetta is required. It's usually already installed; if it's missing, Atera will attempt to install it automatically.
- If a device already has the agent installed before you set up installation via Intune, leftover files from the previous installation may cause issues. To avoid this, perform a full cleanup of the device before proceeding.
- Atera doesn't offer support for any installation issues related to Intune. If you do encounter any issues, see:
Prerequisites
- Local admin permissions on target Macs (required for agent install).
- macOS agent version 1.8.5.7 or later for silent install support.
- Rosetta installed on Apple Silicon (M-series) Macs - usually pre-installed, but Atera will attempt to install it automatically if missing.
- An active Intune enrollment for the target Mac devices.
- Admin access to Atera for the relevant site.
- Admin access to Atera for the relevant customer.
Get the Mac install command from Atera
To get the Mac install command or installer file:
1. Click Install agent on the menu bar (top of any page).
The Install the Atera Agent window appears.
2. Select Mac (.pkg). Then click Next.
3. Assign the agent to a site and folder (optional). Then click Next.
3. Assign the agent to a customer and folder (optional). Then click Next.
4. Copy the install command, or click Download to download the .pkg installer file - depending on the deployment method you choose below.
Note: The install command and installer file are tied to the site selected during creation. Generate a fresh command or installer for each site you're deploying to, so devices register under the correct site in Atera.
Note: The install command and installer file are tied to the customer selected during creation. Generate a fresh command or installer for each customer you're deploying to, so devices register under the correct customer in Atera.
Choose your deployment method
You have two practical options for getting this into Intune:
Option A: Wrap the install command in a shell script (recommended)
- Create a .sh script that runs the copied Terminal install command silently.
- Package it as a custom script in Intune (Devices > Scripts > Add > macOS shell script).
- Assign it to your target device group.
Option B: Package the .pkg directly
- Download the Atera .pkg installer.
- Upload it to Intune as a line-of-business app (Apps > macOS > Add > Line-of-business app).
Note: Unlike the Windows .msi flow, there's no documented silent-install argument for this path. The .pkg installs silently by default (v1.8.5.7+).
Assign and deploy
1. Assign the script or app to the appropriate device group in Intune.
2. Set the install to run in system context (not user context) to avoid permission prompts.
3. Push to a small test group of Macs first.
Verify installation
1. Check Intune's app/script install status - it should show Installed or Succeeded.
2. Confirm the device also appears in Atera under the correct site. There's a known gap where Intune reports success but the agent doesn't register in Atera - this usually points to a mismatched or expired install command (e.g., pulled from the wrong site).
2. Confirm the device also appears in Atera under the correct customer. There's a known gap where Intune reports success but the agent doesn't register in Atera - this usually points to a mismatched or expired install command (e.g., pulled from the wrong customer).
Note: If a device shows installed in Intune but not in Atera, re-pull a fresh install command from the correct site and re-run manually on one machine to confirm it registers before troubleshooting at scale.
Note: If a device shows installed in Intune but not in Atera, re-pull a fresh install command from the correct customer and re-run manually on one machine to confirm it registers before troubleshooting at scale.
Troubleshooting tips
- Duplicate/leftover files from a prior agent install can cause silent failures. Fully uninstall any existing Atera agent before redeploying via Intune.
- If the script runs but nothing shows in Atera, double-check you're using the .pkg/command generated for the correct site - a mismatched site is the most common cause of "installed but invisible" devices.
- If the script runs but nothing shows in Atera, double-check you're using the .pkg/command generated for the correct customer - a mismatched customer is the most common cause of "installed but invisible" devices.
- For persistent issues, Atera's Community forum has real-world scripts and troubleshooting threads from other admins who've solved the same Intune-Mac gap.
