Deploying the macOS and iOS Clients with Jamf
Configuring Jamf to distribute the Twingate Client
macOS
To distribute the Twingate macOS Client with Jamf, you will need to distribute Twingate as a package. Follow Jamf’s official documentation to configure and distribute Twingate. To deploy a package, you’ll need to upload a PKG to Jamf. You can download the Twingate PKG installer from the download page.
iOS
To distribute the Twingate iOS Client with Jamf, you will first need to add the Twingate Client app to Apple Business Manager. If you haven’t already, link Jamf to Apple Business Manager by following the steps in Jamf’s official documentation.
Once Jamf is linked to Apple Business Manager, you should be able to distribute the Twingate iOS app from Jamf.
Tips
Remove manually installed Twingate Clients
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 may run into issues like their installed Twingate Client differing from your distributed version.
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.
Pre-configuring the macOS Client
You can pre-configure the macOS Client by following the configuration profiles guide. By following this guide, you can automatically enable the VPN configuration for Twingate, enable the system extension, and pre-populate the Network that your users connect to.
Last updated 1 month ago