Updating Your Jamf Protect Offline Deployment Mode License

Jamf Protect Offline Deployment Documentation

Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

Your Jamf Protect license is stored as a value in the offlineToken field of a Plan's Configuration Profile. Without a valid offlineToken value, Jamf Protect will stop operating after a brief grace period. You can run sudo protectctl info -v to view the expiration date and status of your license.

When you renew your Offline Deployment Mode license, the new offlineToken does not automatically update on all computers in your fleet. Instead, the plan must be redeployed from Jamf Protect, or redeployed using a configuration profile in Jamf Pro.

In Jamf Protect, the offlineToken appears in Administrative > Downloads.

Requirements

You must have a Jamf Protect Offline Deployment Mode tenant to complete this task.

  1. Contact Jamf to renew your Jamf Protect Offline Deployment Mode license.
  2. Deploy the new license key using one of the following methods:
    • Download and deploy a configuration profile with the new license.
      1. In Jamf Protect, navigate to Plans and download the plan configuration profile, which contains the new offlineToken.

      2. In Jamf Pro, navigate to Computers > Configuration Profiles.

      3. In the Scope tab, edit the scope of the configuration profile to remove all devices and save the changes, then delete the profile.

      4. Upload the configuration profile that contains the new offlineToken. See Deploying Jamf Protect Offline Deployment Mode.

      5. Edit the scope of the configuration profile to add all devices to the new profile.

    • Manually update the license and deploy the configuration profile using Jamf Pro.
      1. In Jamf Pro, navigate to Computers > Configuration Profiles.

      2. In the Applications & Custom Settings payload of the configuration file, update the profile using the offlineToken value from the Administrative > Downloads tab in Jamf Protect.

      3. Click Save.

The configuration profile is deployed to the target devices with the new offlineToken. When you run sudo protectctl info -v, the Status is Protected.