Welcome to the documentation for Fleet, the lightweight telemetry platform for servers and workstations.
Install osquery and FleetGet started
Can't find what you need?Support
In Fleet you can enforce custom settings on your macOS hosts using configuration profiles.
To enforce custom settings, we will do the following steps:
How to create a configuration profile with iMazing Profile Creator:
Download and install iMazing Profile Creator.
Open iMazing Profile Creator and select macOS in the top bar.
Find and choose the settings you'd like to enforce on your macOS hosts. Fleet recommends limiting the scope of the settings a single profile: only include settings from one tab in iMazing Profile Creator (ex. Restrictions tab). To enforce more settings, you can create and add additional profiles.
In iMazing Profile Creator, select the General tab. Enter a descriptive name in the Name field. When you add this profile to Fleet, Fleet will display this name in the Fleet UI.
In your top menu bar select File > Save As... and save your configuration profile. Make sure the file is saved as .mobileconfig.
In Fleet, you can upload configuration profiles using the Fleet UI or fleetctl command-line tool.
The Fleet UI method is a good start if you're just getting familiar with Fleet.
The fleetctl CLI method enables managing configuration profiles in a Git repository. This way you can enforce code review and benefit from Git's change history.
In the Fleet UI, head to the Controls > macOS settings > Custom settings page.
Choose which team you want to add the configuration profile to by selecting the desired team in the teams dropdown in the upper left corner. Teams are available in Fleet Premium.
Select Upload and choose your configuration profile. After your configuration profile is uploaded to Fleet, Fleet will apply the profile to all macOS hosts in the selected team. Thereafter, the profile will be applied to new macOS hosts that enroll to that team.
In this example, we'll add a configuration profile to the "Workstations (canary)" team so that the setting only gets enforced on hosts assigned to this team.
apiVersion: v1 kind: team spec: team: name: Workstations (canary) mdm: macos_settings: custom_settings: - /path/to/configuration_profile.mobileconfig ...
Learn more about team configurations options here.
To enforce settings on hosts that aren't assigned to a team ("No team"), we'll need to create an
apiVersion: v1 kind: config spec: mdm: macos_settings: custom_settings: - /path/to/configuration_profile.mobileconfig ...
Learn more about configuration options for hosts that aren't assigned to a team here.
mdm.macos_settings.custom_settings key to your YAML document. This key accepts an array of paths to your configuration profiles.
fleetctl apply -f workstations-canary-config.yml command to upload the configuration profiles to Fleet. Note that this will override any configuration profiles added using the Fleet UI method.
In the Fleet UI, head to the Controls > macOS settings tab.
In the top box, with "Latest," "Pending," and "Failing" statuses, click each status to view a list hosts:
Latest: hosts that applied the latest settings.
Pending: hosts that will apply the latest settings when the hosts come online.
Failing: hosts that are failing to apply the latest settings.
If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the Fleet repo.