Configuration Profile Overview

Baseline is designed to work off of a configuration profile. This configuration profile should be of the "System" scope/type.

If using the provided PKG, or an unmodified version of Baseline.sh, then the preference domain/payload type should be defined as com.secondsonconsulting.baseline

See the Example Configuration Profiles folder on the project for reference.

Using iMazing Profile Editor

Baseline is now included by default in the official iMazing Profile Editor Profile Manifest repository.

Jamf JSON Schema

Jamf users can make use of this automatically generated JSON schema based off of the official Profile Manifest.

Using a .plist File Instead of a Configuration Profile

A plist can be used in place of the mobileconfig profile by placing it in /usr/local/Baseline/BaselineConfig.plist. A file placed here will supercede a mobileconfig profile. There is an example plist file provided in the "ExampleConfigurationFiles" folder of the project repo. iMazing Profile Editor "Export Configuration Payload as Plist" feature can be used as well.