Jamf - MDM Configuration Guide
Configuring Jamf to distribute the Twingate Client
To distribute the Twingate macOS and iOS Clients with Jamf, you will first need to add the Twingate Client app to Apple Business Manager before proceeding with the steps below.
Link Jamf to Apple Business Manager by following the steps in Jamf’s official documentation.
Pre-populating your Twingate tenant name in Twingate Clients distributed by Jamf means that end users will not need to manually enter that name in the Client. To pre-populate your Twingate tenant name, configure Jamf to push a local file containing a custom configuration to devices.
Make sure to setup the roll out of the Twingate Client for devices (and not just for users or user profiles).
If any end users manually installed the Twingate Client on their device prior to implementing Client distribution with Jamf, you should uninstall those Clients first. If you do not do so, those end users will be prompted for their Apple ID and password whenever a new version of the Twingate Client becomes available in the Apple App Store.
To remove manually installed Clients, set up a temporary policy defined specifically to remove the Twingate Client application from all devices. This policy should be deactivated once you are ready to roll out the Twingate Client via Jamf.
You should now be ready to roll out the Twingate Client application to all devices via Jamf.
Last updated 11 months ago