Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

When does Fleet install/uninstall Escrow Buddy & swiftDialog (#39144)

Browse Source 
Write this down:
https://fleetdm.slack.com/archives/C075T40SYB1/p1769798237575329?thread_ts=1769731771.081799&cid=C075T40SYB1
This commit is contained in:
Noah Talerman
2026-02-06 09:16:56 -05:00
committed by GitHub
parent 3f2b671fb3
commit 0d6d1cb6e5
3 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/enforce-disk-encryption.md
+4
View File
@@ -132,6 +132,10 @@ When migrating macOS hosts from another MDM solution, in order to complete the p
Share [these guided instructions](https://fleetdm.com/guides/mdm-migration#how-to-turn-on-disk-encryption) with your end users.
## Advanced
Fleet uses [Escrow Buddy](https://github.com/macadmins/escrow-buddy) to escrow disk encryption keys from macOS hosts. Escrow Buddy is installed only on macOS hosts that are assigned to a team in Fleet with disk encryption enforced. If a host is then transferred to a team that doesn't enforce disk encryption, Escrow Buddy stays installed.
<meta name="category" value="guides">
<meta name="authorGitHubUsername" value="noahtalerman">
<meta name="authorFullName" value="Noah Talerman">
articles/mdm-migration.md
+2
View File
@@ -57,6 +57,8 @@ Configuration:
Fleet's agents must have [updates enabled](https://fleetdm.com/guides/fleetd-updates) (default), for the end user migration workflow to work.
Fleet uses [swiftDialog](https://github.com/swiftDialog/swiftDialog) to instruct end users to enroll. swiftDialog is only installed on macOS hosts when the end user migration workflow starts. When the workflow is disabled, swiftDialog stays installed. swiftDialog is also installed for macOS [setup experience](https://fleetdm.com/guides/setup-experience#swiftdialog).
![Fleet's MDM migration dialog](../website/assets/images/articles/mdm-migration-dialog-494x327@2x.png)
End user experience:
articles/setup-experience.md
+7 -1
View File
@@ -42,7 +42,7 @@ 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.
The bootstrap package and Fleet's agent (fleetd) are 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](#advanced), fleetd won't be installed automatically.
The bootstrap package and Fleet's agent (fleetd) are 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 automatically.
The following are examples of what some organizations deploy using a bootstrap package:
@@ -253,6 +253,8 @@ To manage setup experience software and script using Fleet's best practice GitOp
## Advanced
### Manually install fleetd
> **Experimental feature**. This feature is undergoing rapid improvement, which may result in breaking changes to the API or configuration surface. It is not recommended for use in automated workflows.
By default, Fleet's agent (fleetd) is automatically installed during automatic enrollment (ADE) on macOS hosts. To deploy a custom fleetd agent on macOS hosts that automatically enroll, you can use a bootstrap package.
@@ -270,6 +272,10 @@ How to deploy a custom fleetd:
If you deploy a custom fleetd, also add the software and scripts you want to install/run during out-of-the-box macOS setup to your bootstrap package. Fleet won't install the software and run the script [configured in setup experience](#software-and-script).
### swiftDialog
Fleet uses [swiftDialog](https://github.com/swiftDialog/swiftDialog) to show end users [software install](#install-software) and [script run](#run-script) status. swiftDialog is only installed on macOS hosts if there is setup experience software or a script. After setup experinece, swiftDialog stays installed.
<meta name="category" value="guides">
<meta name="authorGitHubUsername" value="noahtalerman">
<meta name="authorFullName" value="Noah Talerman">