macOS Auto-Start

On macOS, auto-start has two parts. The Pult Agent .pkg sets up launch at login, and a managed login item deployed through your MDM keeps users from switching it off.

How Auto-Start Works on macOS

Which Installers Set Up Launch at Login

The .pkg installs a system-wide LaunchAgent at /Library/LaunchAgents/com.pult.agent.plist. The .dmg contains only the app. Get the .pkg from Download.

Check a Mac Before You Enforce

Run on the Mac:

/usr/sbin/pkgutil --pkg-info com.pult.agent
ls -l /Library/LaunchAgents/com.pult.agent.plist

• pkgutil prints the package receipt. The version: line must show 0.2.10 or later (a wrapper .pkg built with a version override shows that override instead). If it prints No receipt for 'com.pult.agent' found at '/'., the agent was not installed from a .pkg.
• The LaunchAgent file must exist and be owned by root and wheel. This is the check that decides: without the file, the agent does not start at login.

To check your whole fleet, use the detection script in Version Detection with REQUIRE_PKG_RECEIPT="true", or the Extension Attribute in Jamf Pro Deployment.

Enforce With a Managed Login Item

Deploy a configuration profile that adds the bundle identifier com.pult.agent as a managed login item. The rule matches the LaunchAgent that the .pkg installs.

Microsoft Intune

1. In the Microsoft Intune admin center, open Devices → Configuration. Under Manage devices, click Create → New policy. Set Platform to macOS and Profile type to Settings catalog.
2. On the Basics tab, enter a name such as Pult Agent Auto-start. Optionally add a description.
3. On Configuration settings, click + Add settings. In the settings picker, search for Managed Login, then select Login → Service Management - Managed Login Items. Enable Comment, Rule Type, and Rule Value.
4. Click + Edit instance and configure the rule:
   • Comment: Pult Agent
   • Rule Type: Bundle Identifier
   • Rule Value: com.pult.agent
5. Continue through Scope tags (optional). On Assignments, choose device or user groups (for example All devices). Finish Review + create.

Kandji

1. In Kandji, open Library and click + Add Library Item.

2. Search for login and pick Login & Background Items under Profiles.

3. Scroll to Background Items and click Add Background Item.

4. In the Add Background Item dialog, set:

   • Identifier Type: Bundle Identifier
   • Identifier: com.pult.agent
   • Comment (optional): Pult Agent

   Save the dialog.

5. Under Assignment, use Assignment Maps to attach the profile to the correct Blueprint(s). Verify the background item appears as expected, then click Save.

Jamf Pro

1. In Jamf Pro, go to Computers → Configuration Profiles → New.
2. On the General tab, enter a name such as Pult Agent Auto-start and pick the appropriate distribution method.
3. In the left sidebar, click + Add Payload and select Login Items.
4. Add an entry:
   • Bundle Identifier: com.pult.agent
   • Action: Add to managed login items
5. On the Scope tab, target the desired computers, smart groups, or buildings. Click Save.

Verification

After the profile is deployed:

1. On a target Mac, open System Settings → General → Login Items.
2. The Pult Agent appears in the list, marked as managed by your organization.
3. The user can't switch it off.
4. Log out and back in. The Pult Agent icon appears in the menu bar without being opened.

Agent Doesn't Start at Login

Work through these checks in order:

1. LaunchAgent missing. If /Library/LaunchAgents/com.pult.agent.plist doesn't exist, the agent was installed from the .dmg or from a .pkg older than 0.2.10. Install the current .pkg. If the file exists but isn't owned by root and wheel, macOS ignores it; rebuild the wrapper as described in Build the macOS MDM Package, Step 3.
2. Switched off by the user. If the file exists but the Pult Agent is switched off in System Settings → General → Login Items, deploy a managed login item as described above, or switch it back on.
3. Both in place. Confirm /Applications/Pult Agent.app exists, open it with open -a "Pult Agent", and check the logs (see Troubleshooting).