One of the good things I like with performing Jump Starts is the variety of customer I get to work with. This includes a whole host of requirements and environments, along with various levels of ability and experience. With more experienced customers we typically have time to look into other areas outside a Jump Start that may benefit the solution and the customer as a whole. One such example was trying to get the great AutoPKGr to work with a Jamf Cloud Distribution Point (JCDS).
Firstly a little backstory, AutoPKG / AutoPKGr utilises the amazing JSSImporter plugin in order to talk to your Jamf Pro server, map the File Share Distribution Points and upload the packages (as well as creating the policies and smart groups etc).
When Jamf released support for a Cloud Distribution Point, they also provided an interface (via the Web GUI or Admin App) to upload into an included Jamf Cloud Distribution Point (with the backend hosted in Amazon S3 buckets).
As this was included in a Jamf Cloud subscription, a lot of customers utilised this for package deployment, however this was incompatible with the JSSImporter tool.
This meant that any admins who wished to utilise both AutoPKGr and a JCDS would need to manually upload the new packages after each run.
On a recent Jump start I explored this with a customer and found out this is no longer the case. There is a beta version of the JSSImporter plugin that will work with JCDS!
Ok, it is a beta tool, and as such could always do with more testers, but you may find it suits your needs as-is. There are reports that it needs further tweaks for some admins and not for others. In my experience it tends to work fine as-is, although there’s a small time delay for the changes to show in the Jamf Cloud instance.
Setting up AutoPKGr to use the beta JSSImporter
I’ll assume you have AutoPKGr currently setup on a Mac, mostly configured and you’re familiar with AutoPKG and AutoPKG recipes.
1) Launch AutoPKGr, go to the “Folders & Integration” tab and click “Install JSSImporter…”
2) Follow the on-screen instructions to get the plugin installed. You can confirm that the plugin is installed on the “Install” page
3) Once complete, quit AutoPKGr
4) Fire up your web browser of choice and go to https://github.com/jssimporter/JSSImporter/releases
5) Find the “Bundled Dependency Testing” pre-release (version 1.0.2b2) and download the installer package here
6) Run the installer on your AutoPKGr Mac. Once complete, relaunch AutoPKGr. You’ll notice that the JSSImporter will still show as v1.0.0. This is normal and expected.
7) Go back to the “Folders & Integration” tab, click “Configure JSSImporter” and fill in your Jamf Cloud URL as well as your API username and password (recommendations for this account can be found here).
8) Click “Connect” to test the connection, then “Add Distribution Point”
9) Select “CDP” for the type and click “Add”
10) Click “Save and Close” to save these details
11) Continue the remaining setup requirements in your Jamf Pro Server (“Testing” static Computer Group etc – https://github.com/autopkg/jss-recipes#requirements-and-configuration)
12) Run some test runs with .jss recipes to ensure the packages are uploaded fine, the policies are created, the smart groups are made etc. Then you’re good to go!
More information can be found here:
This post covers how to setup AutoPKGr to use a beta JSSImporter plugin to work with a JCDP. As always, if you have any questions, queries or comments, let me know below (or @daz_wallace on Mac Admins Slack) and I’ll try to respond to and delve into as many as I can.
The usual Disclaimer:
While the author has taken care to provide our readers with accurate information, please use your discretion before acting upon information based on the blog post. I will not compensate you in any way whatsoever if you ever happen to suffer a loss/inconvenience/damage because of/while making use of information in this blog.