Deploying Jamf Connect Sync


You can install Jamf Connect Sync with the signed package installer provided by Jamf. This package is signed by a valid Apple Developer identity and will install Jamf Connect Sync in the Applications folder of target computers.


You can deploy Jamf Connect Sync to target computers in your environment using your preferred MDM solution.

Complete the following instructions to deploy Jamf Connect Sync:

  1. Open the Jamf Connect DMG.

  2. Open an example PLIST file with a text editor. Examples can be found in the DMG and product documentation.

  3. In the PLIST file, specify your Okta authentication server using the AuthServer preference key.

  4. (Optional) Add and edit additional preference keys to further customize the experience for your users.
    For more information, see the Configuring Jamf Connect Sync.

  5. Upload your Jamf Connect Sync PLIST file to your MDM solution. If using Jamf Pro, use the "Custom Settings" payload.
    For more information about custom configuration profiles, see the Deploying Custom Configuration Profiles using Jamf Pro Knowledge Base article.

  6. Upload the provided license key configuration profile to your MDM solution.

  7. Scope the uploaded profile from step 6 to the same computers targeted in step 5.

  8. Upload the PKG files for Jamf Connect to your preferred MDM solution.

  9. Create a policy to deploy packages from step 8 and scope the policy to targeted computers.

Launch Agent

You can install a launch agent that instructs macOS to launch Jamf Connect Sync on log in. You can create your own XML file or use the launch agent included in the product download.

Note: If NoMad Pro was previously installed on the computer, the launch agent will uninstall this application before installing Jamf Connect Sync.


Jamf Connect Sync requires a valid license to be deployed with the application. Your Jamf account manager will provide a license key configuration profile, which can be deployed as either a preference key or a file in the Jamf Connect Sync application support folders.

The order of precedence for license discovery is the following:

  1. Jamf Connect Sync preferences

  2. A .jamfconnectlicense file in /Library/Application Support/com.jamf.connect.sync

  3. A .jamfconnectlicense file in ~/Library/Application Support/com.jamf.connect.sync

Note: To store the license in the preferences configuration profile, you must convert the license file to base64 format, and then use the LicenseFile key in your configuration profile.

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2019 Jamf. All rights reserved.