Download the latest release, which you push out with a management suite such as Munki or Jamf Pro.

A typical deployment would look like this:

• install the outset release pkg
• install any custom pkg(s) containing your scripts or packages to the outset processing folders.

When the Mac next boots or a user logs in, Outset will process the custom files from the appropriate processing folder.

It's recommended that Outset be deployed with an associated configuration profile to enforce outset and inform the user that this service is managed by your organisation.

Deploy a Managed Login Items MDM payload with the following rule:

<key>Rules</key>
<array>
    <dict>
        <key>RuleType</key>
        <string>LabelPrefix</string>
        <key>RuleValue</key>
        <string>io.macadmins.Outset</string>
        <key>TeamIdentifier</key>
        <string>T4SK8ZXCXG</string>
    </dict>
</array>

• When Outset is installed, the launchd jobs are automatically invoked. Any existing scripts already installed into their respective working directories will be run in the expected context. Be sure to test your setup thoroughly before deploying Outset to live systems.

• on macOS 13+ If deploying via MDM pre-stage (enrolment), the launch agents may not appear in System Settings -> General -> Login items correctly as a single entry or with the outset icon

  

  This should not affect Outset's behaviour. Once enrolment is complete, re-installing Outset should resolve the issue.

  The outset 4.0.1 install PKG mitigates against this behaviour by installing launchd plists instead of using SMAppService