Skip to main content
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight about Apple device deployments, share best practices and bounce ideas off each other. Join the conversation.

Components Installed on JDS Instances

Disclaimer: This article is no longer being updated. The Jamf Distribution Server was discontinued at the end of 2017.

The following items are installed when you install a Jamf Distribution Server (JDS) instance:

jamfds binary

JDS tasks are executed using the "jamfds" command-line application (also known as the jamfds binary). It is installed in the following location:

  • Mac: -- /usr/local/bin/jamfds (The Casper Suite v9.8 or later) -- /usr/sbin/jamfds (The Casper Suite v9.73 or earlier)
  • Linux: /usr/local/sbin/jamfds

Jamf Check-In Task

The Jamf check-in task determines how often the JDS instance checks in with the JSS.

  • Mac: /Library/LaunchDaemons/com.jamfsoftware.jamfdspolicy.plist
  • Linux: /var/spool/cron/crontabs/root

Note: On Linux, this file already exists, and the JDS Installer simply modifies it. Do not delete this file.


The certificates associated with JDS to JSS communication are stored in the following location:

  • Mac: /Library/JDS/certs/
  • Linux: /usr/local/jds/certs/

jamfds.conf and apache_aliases.conf

These files contain settings for the JDS instance. They are stored in the following location:

  • Mac: /Library/JDS/conf/
  • Linux: /usr/local/jds/conf/

api.php and jds.conf

  • Linux: /var/www/html/jds/api.php
  • Linux: /etc/httpd/conf.d/


Logs for the JDS instance are stored in the following location:

  • Mac: /Library/JDS/logs/
  • Linux: /usr/local/jds/logs/

In-House Book Storage Location

In-house books added to the JDS instance are stored in the following location:

  • Mac: /Library/JDS/shares/eBooks/
  • Linux: /usr/local/jds/shares/ebooks/

In-House App Storage Location

In-house apps added to the JDS instance are stored in the following location:

  • Mac: /Library/JDS/shares/mobileDeviceApps/
  • Linux: /usr/local/jds/shares/mobiledeviceapps/

Package Storage Location

Packages added to the JDS instance are stored in the following location:

  • Mac: /Library/JDS/shares/CasperShare/
  • Linux: /usr/local/jds/shares/caspershare/
Like Comment
Order by:
SOLVED Posted: by christopher.kaczmare

To generate a backup of JDS, is it enough to Backup following Path's?
- /Library/JDS
- /usr/sbin/jamfds
- /PathToCasperShare/ (if not within /Library/JDS/)

Or is it recommended to host a second JDS instance and keep them synced?

Best regards,

SOLVED Posted: by ajacks88

Is there a way to change the CasperShare location similar to what is possible in a File Share Distribution Point? I am running my JDS on a RHEL VM that has a 500GB /apps share mounted. But as far as I can tell there is no built-in way to change the CasperShare location.

SOLVED Posted: by jwbrcd

Hi there,

You can do one of two things here, A) Create a symlink (shortcut) from the current jds shares dir to /apps/shares. or
B) mount the 500G /apps device to /usr/local/jds/shares. Note, this is more involved and requires familiarity with Linux CLI, mounting, and editing files (fstab)... if you make mistakes, the system will have issues.

Please check these commands carefully in case I mistyped something. .

Steps for the symlink method:

  1. become root (or use sudo in front of all these commands)
    $ sudo -I

  2. Stop httpd. (note this may cause disruption for clients if they are actively getting content from this JDS, maybe try this during off-peak times)
    service httpd stop

  3. make a new jds shares dir under the 500G /apps mkdir /apps/shares

  4. Move current jds shares dir out of the way
    mv /usr/local/jds/shares /usr/local/jds/shares.old

  5. create a symlink from current shares to the new one you created under /apps
    ln -s /apps/shares/ /usr/local/jds/shares

  6. check symlink works as expected
    ls -alh /usr/local/jds/shares/

  7. this should show a symlink now that looks like this: shares -> /apps/shares

  8. rsync your current packages to the new location *note slash on end of source here. rsync -avp /usr/local/jds/shares/ /apps/shares

  9. rsync can take some time depending on how much data you have there

  10. start httpd back up
    service httpd start

  11. Open Casper Admin and check replicating to this jds again to make sure it works as expected.

  12. on the jds server check the contents of the new directory to confirm your packages are there
    ls -alh /apps/shares/CasperShare/

  13. this should show you all your packages that were in the original CasperShare that we renamed to CasperShare.old above.

  14. Once you confirm all works as expected, you can carefully delete the original CasperShare dir
    rm -rf /usr/local/jds/shares.old



Jamf wants to hear your feedback around Jamf Pro: LDAP Servers and Reports!