OSX: method and comparison of third-party Profile deployment

Currently, there are at least three third-party Profile deployment methods.

A Profile Handler is a mechanism that activates directory changes by using Launchd. It stores the required profiles in the directory of the target machine and the system will automatically install them; if a profile file in the directory is removed, the script also removes it from the system. For details, refer to: examples.

Another Profile PKG is to generate an installation package so that it can be deployed in any appropriate way-either remotely or locally, using ARD or Monki/Puppet or Casper. See the https://github.com/timsutton/make-profile-pkg for details.

The last method is more violent. It uses the built-in mechanism of The OSX system to install Profiles. That is, copy the profiles file to/private/var/db/ConfigurationProfiles/Setup and delete the file:/private/var/db/ConfigurationProfiles/Setup /.ProfileSetupDone and restart the system.

Comparison:

The Profile Handler method is suitable for many situations and is also adaptive. It can be used in most cases.

The Profile PKG method can be at least applicable to The OSX Pre-Deployment scenario, that is, the use of tools such as AutoDMG to generate an OSX deployable DMG image file. You need to do some work for other methods.

The last method is generally not used.