Installing JAMF’s JDS on OS X server is pretty easy and straightforward enough, but what happens when you have to configure 80 of them in remote locations with limited time?
Recently I found myself working with a K12 customer with many schools spread out over a large area. They decided they wanted a distribution point in each school, and opted to purchase Mac Mini servers for the task. We decided to deploy them as JDS servers, rather than use the built in AFP service, mostly due to the built-in automated syncing.
We didn’t have the time or resources to remote in to each computer to install and configure the JDS manually, so I came up with a quick solution using the Casper Suite to install and configure the JDS software automatically.
The following is a step by step guide:
Step 1 – Enroll the OS X server(s) in the JSS
This should be pretty self explanatory.
Step 2 – Create a JSS user account for the JDS
For security reasons, this should be a unique user account for the JDS servers. Make sure to give it full CRUD privileges for JDS.
Step 3 – Upload the JDS Installer.pkg to your JSS
If you don’t already have at least one distribution point, you’ll want to configure the first JDS manually in order to deploy the pkg to the rest of your JDS servers.
Step 4 – Upload the jdsConfig.sh script to your JSS
The script can be found here: https://github.com/kitzy/JDSConfig
I recommend labeling the parameters in the script as follows:
Parameter 4: JSS URL
Parameter 5: JDS User
Parameter 6: JDS Password
Parameter 7: Allow Invalid Cert
Set the script priority to after.
Step 5 – Create a policy to configure the JDS servers
The policy should install the JDS Installer.pkg, then run the script. Fill in the appropriate information in parameters 4-7, or insert the values for the variables into the script.
The script is expecting the following parameters:
Parameter 4: The complete URL of the JSS (including https:// and :8443)
Parameter 5: The JSS user we created earlier with CRUD privleges for the JDS
Parameter 6: Said user’s password
Parameter 7: Whether or not to allow an invalid certificate (the script is expecting either “yes” or “no”)
I recommend setting the policy to the check-in trigger, and an execution frequency of once per computer.
Scope the policy to your intended JDS servers and watch the magic happen.