Migrating from Compliance Reporter to Jamf Protect Offline Deployment Mode

Jamf Protect Offline Deployment Documentation
Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

Jamf has discontinued support and distribution of Compliance Reporter. The last supported version of Compliance Reporter is for macOS 14.x.

Jamf now offers Jamf Protect Offline Deployment Mode, which provides endpoint visibility for macOS computers without requiring a connection to Jamf Protect Cloud.

Users with high-compliance requirements can use Jamf Pro to create, scope, and deploy Offline Deployment Mode using a schema instead of using the user interface. For more information, see Creating an Offline Deployment Mode Configuration Schema.

If you have questions or concerns while migrating to Jamf Protect Offline Deployment Mode, contact Jamf Support.

  1. Create a telemetry configuration.

    For the complete set of tasks, see Creating a Telemetry Configuration.

    To configure settings that meet parity with Compliance Reporter functionality, complete the following steps:

    1. In Telemetry Log Levels, select the log level that you used in your Compliance Reporter audit log-level configuration.
    2. (Optional) If you used verbose logging in your Compliance Reporter audit log configuration, select the Activate Verbose Logging checkbox.
  2. (Optional) Create a unified log filter.

    For the complete set of tasks, see Creating a Unified Log Filter.

  3. Create an action configuration that includes one or more telemetry or unified log collection endpoints.

    For the complete set of tasks, see Creating an Action Configuration.

  4. (Optional) Implement additional telemetry features through Jamf Protect Offline Deployment Mode.

    • Select Performance metrics to include information about the use of system resources by processes and applications.

    • Select Diagnostic and crash reports to collect specific diagnostic and crash log files.

    • If you used preference keys in your configuration of Compliance Reporter, click + Add in the Local Log File section to write a local copy of telemetry data on computers and configure local file settings.

    • In the Simple log file collection field, add additional file paths to log files that you want to collect from computers.

  5. Create an Offline Deployment Mode plan.

    For the complete set of tasks, see Creating an Offline Deployment Mode Plan.

  6. (Recommended) Assign the Jamf-managed default exceptions set to your plan for optimized analysis and volume of telemetry data.

    If you used the AuditEventExcludedProcesses event filter, create an Offline Deployment Mode exception set to optimize the volume of collected telemetry data.

    For the complete set of tasks, see Creating an Offline Deployment Mode Exception Set.

  7. Download the plan configuration profiles and the Jamf Protect installer PKG for deployment via an MDM solution.
  8. Scope and deploy the Jamf Protect Offline Deployment Mode configuration profile and package to target computers via an MDM solution, such as Jamf Pro.

    For the complete set of tasks, see Deploying Jamf Protect Offline Deployment Mode.

  9. After you have configured and tested your migration to Jamf Protect Offline Deployment Mode, contact Jamf Support for assistance uninstalling Compliance Reporter.