Components Installed on Managed Computers

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/jamf/bin/jamfagent—Agent launched per user account to work in conjunction with the LaunchDaemons and LaunchAgents to report on specific user data.

  • /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 so it can be found in the default search paths.

  • /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/JamfAgent.app—App bundle containing the jamf launch agent used for application usage monitoring and restricted software.

  • /Library/Application Support/JAMF/JAMF.app/Contents/MacOS/JamfDaemon.app—App bundle containing the jamf launch daemon.

  • /usr/local/jamf/bin/jamfAAD—Symbolic Link to /Library/Application Support/JAMF/Jamf.app/Contents/MacOS/JamfAAD.app/Contents/MacOS/JamfAAD.

LaunchDaemon/LaunchAgent

  • /Library/LaunchDaemons/com.jamfsoftware.task.1.plist—Used for 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.

  • /Library/LaunchDaemons/com.jamfsoftware.jamf.daemon.plist—Used for Application Usage, Network State Changes, iBeacons, FileVault information sent to the Jamf Pro server, Restricted Software, notifications, and Self Service actions.

  • /Library/LaunchAgents/com.jamfsoftware.jamf.agent.plist—Used in conjunction with the com.jamfsoftware.daemon.plist for tasks such as Application Usage, Restricted Software, and Self Service actions.

  • /Library/LaunchDaemons/com.jamf.management.daemon.plist—Launchd file used to start the JamfDaemon.app process.

  • /Library/LaunchAgents/com.jamf.management.agent.plist—Launchd file used to start the JamfAgent.app process.

  • /Library/LaunchAgents/com.jamf.management.jamfAAD.agent.plist—Launchd 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 a 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 Lists

  • /Library/Preferences/com.jamfsoftware.jamf.plist—Defines the Jamf Pro server URL, Management Framework Change ID and security settings such as SSL verification, clock skew, and package validation.

  • /var/root/Library/Preferences/com.apple.loginwindow.plist—Used to store the defined login/logout hooks for the system.

Jamf Application Support Directory

  • /Library/Application Support/JAMF/.blacklist.xml—Contains list of Restricted Software for clients using a 10.13.0 or earlier version of the Jamf Pro binary.

  • /Library/Application Support/JAMF/.jmf_settings.json—Contains a list of Restricted Software for clients using a 10.14.0 or later version of the Jamf Pro binary.

  • /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/ManagementFrameworkScripts/loginhook.sh—Script that is called by the com.apple.loginwindow.plist to enable a check-in to the Jamf Pro server at login.

  • /Library/Application Support/JAMF/ManagementFrameworkScripts/logouthook.sh—Script that is called by the com.apple.loginwindow.plist to enable a check-in to the Jamf Pro server at logout.

  • /Library/Application Support/JAMF/Offline/—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/run/—Temporary Storage for FileVault key prior to submission.

  • /Library/Application Support/JAMF/Self Service/—Contains Self Service plugins.

  • /Library/Application Support/JAMF/tmp/—Contains temporary storage for logs and other files.

  • /Library/Application Support/JAMF/Usage/—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 Log

  • /var/log/jamf.log—Contains a record of what the jamf binary does.

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

  1. Log in to Jamf Pro.

  2. Click Computers at the top of the page.

  3. Perform a simple or advanced computer search.
    For more information, see Simple Computer Searches or Advanced Computer Searches.

  4. 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 images/docs.jamf.com/10.21.0/jamf-pro/administrator-guide/images/download/thumbnails/19536832/Icon_Expand.png next to an item to view the computers related to that item.

  5. Click the Management tab, and then click Remove MDM Profile.

  6. Open Terminal on the computer you want to remove the components from.

  7. 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

  1. Open Terminal on the computer you want to remove the components from.

  2. Execute the following command:
    /usr/local/bin/jamf removeFramework

All Jamf-related components are removed from the computer.

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