pmg setup install --system once to put administrator-owned shims first on the machine PATH.
The MDM scripts README in the PMG repo is the source of truth. Scripts and supported MDMs are updated there first.
Jamf
Use multi-file scripts for macOS. Pass Cloud credentials as script parameters.
JumpCloud
Use multi-file scripts for macOS, Linux, or Windows.
Intune
Use standalone scripts for all three platforms, or a Windows Win32 app.
Scripts
Run the scripts as root on macOS and Linux, or as SYSTEM or an administrator on Windows. Windows deployment requires PMG v0.29.0 or later. See the MDM scripts README for platform requirements and cleanup limitations.- Multi-file (Jamf, JumpCloud, Intune Win32 apps): Deploy the shared lib for your platform alongside the install or uninstall script. The entry scripts source the shared lib at runtime and fail without it. Use them when your MDM can ship sibling files.
- Standalone (Intune): Use a prebuilt installer, or generate one with managed config and optional Cloud credentials embedded, then upload that one script. Use them when your MDM accepts one script per policy.
config.yml beside the scripts or embed it with the standalone generator’s --config option. Keep your other policy settings in the file. The installer replaces the managed config with the bundled file.
Cloud sync
PMG blocks packages without Cloud credentials. MDM deploys can also sync data to SafeDep Cloud. With Cloud credentials configured, the install script attemptspmg cloud sync after setup. On Windows, this runs for signed-in users only. A successful sync adds the device to Endpoint Hub without waiting for a package manager event. Installs sync to Package Guard.
Cloud sync from an MDM fleet needs the SafeDep Cloud Enterprise plan. See pricing. To use Cloud sync, you need an API key and Tenant ID from app.safedep.io/settings/api-keys.
On Windows, Cloud credentials must be accompanied by a config with cloud.enabled: true. This applies to runtime and embedded credentials. The system install always creates a managed config, which pmg config set cloud.enabled true cannot change. On macOS and Linux, the installer enables sync automatically when credentials are supplied and no managed config exists. If you supply a managed config, set cloud.enabled: true in it.
For Windows standalone scripts with runtime credentials, keep --config and omit --embed-cloud-credentials when generating the installer. See Globally Managed Configuration.
To repeat the sync without installing or configuring PMG again, pass --cloud-sync-only to the install script. Use this option only for users who already have PMG and cloud sync enabled. Run the normal installer to configure new users. On Windows, run it after those users sign in to store their Cloud credentials.
A successful MDM install status does not confirm Cloud sync. If a Windows endpoint does not appear in Endpoint Hub, check
pmg config get cloud.enabled and run pmg cloud sync in the session of a signed-in user with credentials configured. Cloud sign-in and sync failures do not fail the normal installer.Certificates
The MDM scripts do not install a persistent MITM CA (pmg setup cert install). On macOS this needs interactive Keychain authorization, so it cannot run through MDM. Have each user run it in their own session when needed. On Linux, PMG’s ephemeral CA is usually enough. Run pmg setup cert install --system as your normal user only if a tool needs a persistent CA in the system trust store. Windows package managers use the injected ephemeral CA, except Go, which needs a user-run pmg setup cert install.
Manage settings from the cloud policy
With the cloud policy, your security admin changes the package rules and the dependency cooldown of PMG in SafeDep Cloud, with no new MDM package. To use it on the fleet, change the managedconfig.yml that you ship with the scripts:
config.yml
cloud.enabledandcloud.policyturn on the cloud policy.global_lockdown: truestops users from changing the managed config with mostPMG_*environment variables, the policy flags such as--sandbox, and project allowances.- Do not set the dependency cooldown in this file. Under
global_lockdown, a key that the managedconfig.ymlsets wins over the cloud policy. Sodependency_cooldown.enabledordependency_cooldown.daysin this file stops your security admin from changing the cooldown in SafeDep Cloud. PMG reports the field as locked, andsafedep endpoint policy showshows the exception.
cloud.policy: false. The cloud policy needs the SafeDep Cloud Team or Enterprise plan. See pricing.
