From 718e1bed1f256352993cb31070bc5ea050b951db Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Tue, 1 Apr 2025 09:16:46 -0400 Subject: [PATCH] Bootstrap package guide (#27699) It's easy to miss "distribution package" requirement --- articles/macos-setup-experience.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/macos-setup-experience.md b/articles/macos-setup-experience.md index 58a9d5fddb..3d7e24b549 100644 --- a/articles/macos-setup-experience.md +++ b/articles/macos-setup-experience.md @@ -40,7 +40,7 @@ To require a EULA, in Fleet, head to **Settings > Integrations > Automatic enrol ## Bootstrap package -Fleet supports installing a bootstrap package on macOS hosts that automatically enroll to Fleet. +Fleet supports installing a bootstrap package on macOS hosts that automatically enroll to Fleet. Apple requires that your package is a distribution package. 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. @@ -67,7 +67,7 @@ Whether you have to download or generate a package depends on what you want to d * To deploy custom scripts, you need to generate a package. The [munkipkg tool](https://github.com/munki/munki-pkg) is a popular tool for generating packages. -Apple requires that your package is a distribution package. Verify that the package is a distribution package: +Verify that the package is a distribution package: 1. Run the following commands to expand your package and look at the files in the expanded folder: