Jamf Components Installed on Computers

The following components are installed on all computers.

Jamf Apps and Binaries

/usr/local/jamf/bin/jamf—The binary used to execute most tasks for Jamf Pro.
/usr/local/bin/jamf—Symbolic link to the jamf binary so it can be found in the default search paths.
/usr/local/bin/jamfagent—Symbolic link to the jamf agent binary. This is no longer in use.
/Library/Application Support/JAMF/Jamf.app—App bundle that groups together components of the management framework.
/Library/Application Support/JAMF/JAMF.app/Contents/MacOS/JamfAAD.app—App bundle used for integration with Azure Active Directory (AD).
/Library/Application Support/JAMF/JAMF.app/Contents/MacOS/JamfDaemon.app—App bundle containing the jamf launch daemon. This process will be launched during the macOS startup to perform tasks for the Jamf management framework (e.g., coordinating policy execution for Self Service, monitoring for restricted software, and monitoring application usage).
/Library/LaunchAgents/com.jamf.management.agent.plist—Used to monitor user login events.
/usr/local/jamf/bin/jamfAAD—Symbolic link to /Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfAAD.app/Contents/MacOS/JamfAAD.

LaunchDaemons and Agents

/Library/LaunchDaemons/com.jamfsoftware.task.1.plist—Manages the recurring check-in to the Jamf Pro server.
/Library/LaunchDaemons/com.jamfsoftware.startupItem.plist—Used to call the StartupScript.sh management framework check-in script once during the macOS startup.
/Library/LaunchAgents/com.jamfsoftware.jamf.agent.plist—No longer in use.
/Library/LaunchDaemons/com.jamf.management.daemon.plist—Used for Application Usage, Network State Changes, iBeacons, FileVault information sent to the Jamf Pro server, Restricted Software, and Self Service-related tasks.
/Library/LaunchAgents/com.jamf.management.jamfAAD.agent.plist—Launch file only present when macOS Intune Integration is enabled on the server; used to start the JamfAAD.app process.
/Library/Preferences/com.jamf.management.jamfAAD.plist—Stores user's Azure AD preferences.
/Library/LaunchAgents/com.jamf.management.jamfAAD.clean.agent.plist—Used to delete an Azure AD ID token from the user’s login keychain and a user's Azure AD preferences for users that are not currently logged in to the computer.

Property List

/Library/Preferences/com.jamfsoftware.jamf.plist—Defines settings for the Jamf Pro management framework (e.g., the Jamf Pro server URL, Management Framework Change ID, and security settings).

Jamf Application Support Directory

/Library/Application Support/JAMF/.jmf_settings.json—Contains settings used by the JamfDaemon.app (e.g., the restricted software list).
/Library/Application Support/JAMF/.userdelay.plist—Contains policies that have been deferred.
/Library/Application Support/JAMF/bin/jamfHelper.app—Application used to display messages to an end user.
/Library/Application Support/JAMF/bin/Management Action.app—Application used to display messages to an end user in the macOS Notification Center.
/Library/Application Support/JAMF/Composer/—Contains working directory for Composer to save package sources.
/Library/Application Support/JAMF/Config/—Contains Jamf Pro server-defined iBeacons.
/Library/Application Support/JAMF/Downloads/—Temporary storage for downloaded packages.
/Library/Application Support/JAMF/JAMF.keychain—Enables certificate-based authentication with the Jamf Pro server.
/Library/Application Support/JAMF/ManagementFrameworkScripts/StartupScript.sh—Script that is called by the com.jamfsoftware.startupItem.plist to enable a check-in to the Jamf Pro server at startup.
/Library/Application Support/JAMF/Offline Policies/—Contains the contents of the policies marked to be Available Offline.
/Library/Application Support/JAMF/Receipts/—Contains receipts for all packages installed by Jamf Pro.
/Library/Application Support/JAMF/tmp/—Contains temporary storage for logs and other files.
/Library/Application Support/JAMF/usage_reports/—Contains the application usage data to be sent to the Jamf Pro server.
/Library/Application Support/JAMF/Waiting Room/—Contains temporary storage for Cached Packages.

Jamf Client Logging

/var/log/jamf.log—Contains log messages written by the jamf binary.

Note: Other logging can be accessed via macOS logging commands. To view debug logging for the JamfDaemon, execute the following command:

log stream --level debug --predicate 'subsystem BEGINSWITH "com.jamf.management.daemon"' --style compact

Removing Jamf Components from Computers

This removes all Jamf-related components from computers that have been managed by Jamf Pro and all package sources created with Composer.

Removing Jamf Components from Computers Enrolled Using a PreStage Enrollment

Log in to Jamf Pro.
Click Computers at the top of the page.
Perform a simple or advanced computer search.
For more information, see Simple Computer Searches or Advanced Computer Searches.
Click the computer you want to send the remote command to.
If you performed a simple search for an item other than computers, you must click Expand next to an item to view the computers related to that item.
Click the Management tab, and then click Remove MDM Profile.
Open Terminal on the computer you want to remove the components from.
Execute the following command:
/usr/local/bin/jamf removeFramework

All Jamf-related components are removed from the computer.

Removing Jamf Components from Computers Without an MDM Profile

Open Terminal on the computer you want to remove the components from.
Execute the following command:
/usr/local/bin/jamf removeFramework