Deploying shft with Kandji
This guide covers deploying the shft app and configuration profile through Kandji.
Prerequisites
- Kandji account with Custom Apps and Custom Profiles access
- The shft
.pkginstaller - The shft configuration profile (see Configuration profile reference)
- Target Macs enrolled in Kandji
Step 1: Upload the shft package
- In Kandji, navigate to Library
- Click Add New → Custom App
- Set the app details:
| Field | Value |
|---|---|
| Name | shft |
| Installation type | Package (.pkg) |
| Install as | Auto Install or Self Service (your preference) |
- Upload the
shft-<version>.pkgfile - For audit purposes, set the audit fields:
| Field | Value |
|---|---|
| Audit type | File exists |
| Audit path | /Applications/shft.app |
- Click Save
Step 2: Create the configuration profile
- In Kandji, navigate to Library
- Click Add New → Custom Profile
- Upload the
.mobileconfigfile. To create it:
Build a .mobileconfig file using the example in Configuration profile reference. Customise the values for your organisation.
Alternatively, create the profile directly in Kandji:
- Set the profile details:
| Field | Value |
|---|---|
| Name | shft Configuration |
| Description | Configuration profile for shft migration tool |
| Install on | User Level |
-
Upload the
.mobileconfigfile -
Click Save
Step 3: Assign to blueprints
Both the Custom App and Custom Profile must be assigned to the appropriate blueprints.
- Navigate to Blueprints
- Select the blueprint(s) that contain your target Macs
- In the blueprint, enable both:
- The
shftCustom App - The
shft ConfigurationCustom Profile
- The
Blueprint strategy
| Approach | Blueprint assignment |
|---|---|
| All Macs | Add to your default blueprint |
| Refresh devices only | Create a dedicated "Device Refresh" blueprint and assign target Macs to it |
| By department | Add to department-specific blueprints |
Step 4: Verify deployment
- On a target Mac, open Kandji Agent and trigger a check-in (or wait for the next scheduled check-in)
- Verify shft is installed:
ls /Applications/shft.app - Verify the profile is applied:
defaults read com.shft.config - Open shft and confirm your branding appears
Kandji-specific notes
Auto Apps vs Custom Apps
shft is deployed as a Custom App because it is not currently in Kandji's Auto App library. If shft becomes available as an Auto App in the future, you can switch to that for automatic updates.
Self Service
To make shft available in Kandji Self Service:
- When creating the Custom App, set Install as to
Self Service - Add a description and icon for the Self Service listing
- Users can install shft on-demand from the Kandji Self Service app
Device assignments
If you need to deploy shft to specific devices rather than blueprint-wide:
- Use Kandji's Assignment Map to assign the Custom App to individual device serial numbers
- This is useful for ad-hoc device refreshes outside of a planned rollout
Profile verification
To verify the configuration profile was delivered correctly, check in Kandji's device detail view under Profiles. The shft Configuration profile should appear as installed.