Baseline v1.2
This release is identical code to the v1.2beta1 pre-release
- Added the ability to use a custom plist configuration file instead of a mobileconfig profile
- Baseline will now look for a file at
/usr/local/Baseline/BaselineConfig.plist
- If this file exists, it will be used to determine what items are processed
- This file is checked both before and after
InitialScripts
and takes precedence over an MDM delivered configuration profile - This means Baseline can now be run completely independent of an MDM profile, if the custom configuration plist is delivered (either with a custom built Baseline pkg or other means.)
- Baseline will now look for a file at
- Added
CleanupAfterUse
boolean profile key- If
CleanupAfterUse
key is configured asfalse
, then Baseline will not delete it's working directory/usr/local/Baseline
. - The LaunchDaemon will still always be deleted, in order to prevent multiple runs.
- This key defaults to
true
and can be omitted if you wish to keep the previous behavior to delete the Baseline folder.
- If
- Reordered
Restart
code to provide for the new features - Added logic to turn off verbose mode while waiting for user to log in. This should cut down on log spam significantly when Baseline is initiated while no user is present.
- The pkg preinstall script now properly boots out the LaunchDaemon if its already running. The pkg can now be run multiple times without a reboot.
- The pkg postinstall script now uses launchctl bootstrap instead of load.