Update setup experience documentation for bootstrap package (#41158)

Co-authored-by: Magnus Jensen <magnus@fleetdm.com>
This commit is contained in:
Dale Ribeiro 2026-04-08 09:47:37 -04:00 committed by GitHub
parent 61c89ae083
commit d37745dfd7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -48,6 +48,8 @@ Fleet supports installing a bootstrap package on macOS hosts that automatically
This enables installing tools like [Puppet](https://www.puppet.com/), [Munki](https://www.munki.org/munki/), or [Chef](https://www.chef.io/products/chef-infra) for configuration management and/or running custom scripts and installing tools like [DEP notify](https://gitlab.com/Mactroll/DEPNotify) to customize the setup experience for your end users.
By default, the bootstrap package is not installed during [MDM migration](https://fleetdm.com/guides/mdm-migration) or when a host is enrolled by running `sudo profiles renew -type enrollment`. To change this behavior, you can set the [`fleet_allow_bootstrap_package_during_migration`](https://fleetdm.com/docs/configuration/fleet-server-configuration#fleet-allow-bootstrap-package-during-migration) server configuration.
Fleet's agent (fleetd) is also installed during [MDM migration](https://fleetdm.com/guides/mdm-migration) and when the enrollment profile is renewed manually by running `sudo profiles renew -type enrollment`. If you [manually install fleetd](#manually-install-fleetd), fleetd won't be installed.
The following are examples of what some organizations deploy using a bootstrap package: