(MDM) Installing the agent using a Microsoft Intune wrapper package
This section outlines the end-to-end process for deploying Forcepoint Agent on macOS using Microsoft Intune, when the agent is supplied as two separate files that must be present in the same folder at install time.
Microsoft Intune's macOS Line-of-Business (LOB) app deployment method only accepts a single file per app. It has no built-in mechanism for placing two independent files into the same folder on the target macOS endpoint before running an installer. To work around this, the two original files are combined into a single wrapper .pkg that stages both files on the target machine and then invokes the agent installer automatically. This wrapper is then code-signed, notarized, and uploaded to Intune.
| Stage | What happens | Where |
|---|---|---|
| 1. Build wrapper package | Combine the .pkg and .json files into one wrapper installer with a postinstall script. | Local test macOS endpoint |
| 2. Test locally | Run the wrapper manually to confirm the install logic works. | Local test macOS endpoint |
| 3. Sign and notarize | Apply a Developer ID Installer signature and submit for Apple notarization. | Local test macOS endpoint and Apple servers |
| 4. Upload to Intune | Add the signed, notarized package as a macOS LOB app. | Microsoft Intune admin center |
| 5. Assign and deploy | Assign the app to a device group and monitor rollout. | Microsoft Intune admin center |