Prerequisites
In order to set up Jamf Auto Update you will require some prerequisites, which are detailed below:
-
Jamf Pro
You will require admin access and/or be the one responsible for managing your Jamf Pro. -
Test macOS device(s)
We do recommend that you have with you at least one device reserved for testing purposes. For our operating system support details, please click here.
Configuring and setting up Jamf Auto Update
Whether you're new to Jamf Auto Update or are upgrading from a prior release, the process detailed below is largely the same.
Downloading Jamf Auto Update
The latest version of Jamf Auto Update can be downloaded via this link.
In addition to the Jamf Auto Update.zip, you will be supplied with a configuration profile that will contain details unique to your organisation and will be required to be deployed in order for Jamf Auto Update to function.
This will have either been supplied to you via email or shared via a Google Drive link.
If you have misplaced this profile, please raise a ticket with our support team.
The below will advise how to deploy Jamf Auto Update via your Jamf Pro instance, and the usage for each item found within the Jamf Auto Update.zip.
Extension Attribute
Within the Jamf Auto Update.zip there is a file named: Jamf Auto Update Status.sh.
This is a Computer Extension Attribute for Jamf Pro, the purpose of which is to assist in giving an overview as to the Jamf Auto Update status across the managed Mac computers within your Jamf Pro instance.
To upload this Extension Attribute to Jamf Pro:
-
In your Jamf Pro instance, click Settings in the sidebar.
-
In the Computer management section, click Extension attributes.
-
Click the + New button.
-
In the Display Name set the name to Jamf Auto Update.
-
Scroll down to Input Type , and change this to Script.
-
Copy and paste the contents of the Jamf Auto Update Status.sh file to the Extension Attributes script editor within Jamf Pro.
-
Click Save.
Policy Script
The file, Jamf Auto Update.py, included within the Jamf Auto Update.zip is a script, which is required to run Jamf Auto Update policies.
To upload this script to Jamf Pro:
-
In your Jamf Pro instance, click Settings in the sidebar.
-
In the Computer management section, click Scripts.
-
Click the + New button.
-
In the General tab, set Display Name to Jamf Auto Update.py.
-
Click the Script tab.
-
Copy and paste the contents of the Jamf Auto Update.py file into the script editor.
-
Click the Options tab.
-
Set Priority to After.
-
Set the Parameter Labels as per the below:
-
Parameter 4: Add to installs
-
Parameter 5: Remove from installs
-
Parameter 6: Add to uninstalls
-
Parameter 7: Remove from uninstalls
-
Parameter 8: Force
-
Parameter 9: Verbose
-
-
Click Save.
For more information on the policy script parameters, please click here.
Configuration Profiles
The configuration profiles within the Jamf Auto Update.zip and the additional profile supplied via email or a Google Drive link are required for Jamf Auto Update to function.
With Jamf Auto Update 1.3, the profiles include settings required for prior releases, and as such can be deployed to your Jamf Pro managed Mac computers ahead of Jamf Auto Update 1.3 itself.
To upload each of the supplied configuration profiles:
-
In your Jamf Pro instance, click Computers in the sidebar.
-
In the Content Management section, click Configuration Profiles.
-
Select Upload.
-
Click Choose File.
-
Select the profile to upload.
-
Click Upload.
-
Click Upload, once more.
-
Set the Category as required.
-
Click the Scope tab.
-
Scope as required.
-
Click Save.
Repeat the above for each of the supplied profiles.
Uploading the Jamf Auto Update package
The JamfAutoUpdate-x.x.pkg found within the Jamf Auto Update.zip, contains the Jamf Auto Update framework.
This framework contains the components that install/uninstall items on your Jamf Pro managed Mac computers.
To upload JamfAutoUpdate-x.x.pkg to your Jamf Pro instance, please follow one of the upload methods detailed here.
Deploying Jamf Auto Update
With your Jamf Pro instance populated with the prerequisite items, we can now look to deploy the JamfAutoUpdate-x.x.pkgto devices, starting with a Smart Computer Group.
To create the smart group:
-
In your Jamf Pro instance, click Computers in the sidebar.
-
In the Groups section, click Smart Computer Groups.
-
Click the + New button.
-
In the Computer Group tab, set Display Name to Jamf Auto Update Framework Not Installed.
-
Click the Criteria tab.
-
Click + Add.
-
Click Show Advanced Criteria.
-
Click Choose, to the right of Packages Installed By Casper
-
Set the following:
-
OPERATOR: does not have
-
VALUE: the name of the JamfAutoUpdate-x.x.pkg.
-
-
Select Packages Installed By Casper and Choose.
-
Add any additional criteria as needed.
-
Click Save when finished.
You can keep using this Smart Computer Group as new versions of Jamf Auto Update are released. The only change that will be needed will be the package name (JamfAutoUpdate-x.x.pkg).
Now we can create a policy to deploy the Jamf Auto Update framework to one of more Jamf Pro managed Mac computers.
To create the policy:
-
In your Jamf Pro instance, click Computers in the sidebar.
-
In the Content Management section, click Policies.
-
Click the + New button.
-
In the Options tab, click General.
-
Set the following:
-
Display Name: Install Jamf Auto Update Framework
-
Enabled: Check
-
Category : Set as required
-
Trigger: Recurring Check-In
-
Execution Frequency: Ongoing
-
-
Click Packages.
-
Click Configure.
-
Click Add to the right of the JamfAutoUpdate-x.x.pkg uploaded earlier.
-
Click Maintenance.
-
Click Configure.
-
Check Update Inventory.
-
Click the Scope tab.
-
Click Targets.
-
Click + Add.
-
From here we can either deploy the Jamf Auto Update Framework to all Jamf Pro managed Mac computers, or just to the test macOS device(s).
-
To deploy to all devices:
-
Click Computer Groups.
-
Click Add to the right of the Mac Computer group: Jamf Auto Update Framework Not Installed.
-
Click Done.
-
Click Save when finished.
-
-
To deploy to just the test macOS device(s):
-
Click Computers.
-
Click Add to the right of the test macOS device(s).
-
Click Done.
-
Click Save when finished.
-
Installing Jamf Auto Update Catalog Browser
Jamf Auto Update Catalog Browser is an application which can be used to browse the latest titles and versions included in the Jamf Auto Update library, as well as give details on any additional resources available or workflows applicable to that title.
It also serves as a great first title to install via Jamf Auto Update. Enabling you to test that everything is set up correctly, and giving you an Jamf Auto Update policy to clone and amend as needed.
Jamf Auto Update Catalog Browser needs to be installed on a Jamf Pro managed Mac Computer and the user needs to be an Administrator to run the application, due to the security of the file parsed to retrieve information on titles within Jamf Auto Update.
To install Jamf Auto Update Catalog Browser, we need to create a policy:
-
In your Jamf Pro instance, click Computers in the sidebar.
-
In the Content Management section, click Policies.
-
Click the + New button.
-
In the Options tab, click General.
- Set the following:
-
Display Name: Install Jamf Auto Update Catalog Browser
-
Enabled: Check
-
Category : Set as required
-
Trigger: Recurring Check-In
-
Execution Frequency: Once every week
-
-
Click Scripts.
-
Click Configure.
-
Click Add to the right of the Jamf Auto Update.py uploaded earlier.
-
Set the value of Add to installs, to: JamfAutoUpdateCatalogBrowser
-
-
Click the Scope tab.
-
Click Targets.
-
Click + Add.
-
Click Computers.
-
Click Add to right of the test macOS device(s)
-
Click Done.
-
-
Click Save.
To initiate the above policy:
-
Launch Terminal on the test macOS device(s)
-
Run: sudo /usr/local/bin/jamf policy
You should shortly receive a notification advising that Jamf Auto Update Catalog Browser has been installed.
For more information on Jamf Auto Update Catalog Browser, click here.
Definitions
Jamf Auto Update includes a patch definitions service called Definitions.
The patch definitions within Definitions use the same method to define versioning as Jamf Auto Update.
Adding Definitions to Jamf Pro allows you to report on the patching level of titles deployed via Jamf Auto Update to your Jamf Pro managed Mac computers.
To add Definitions to Jamf Pro:
-
In your Jamf Pro instance, click Settings in the sidebar.
-
In the Computer management section, click Patch Management.
- Click the + New button.
- In the Display Name set the name to definitions.datajar.mobi.
- Check Enabled.
- In Server and Port, enter: definitions.datajar.mobi/v2/ (leave port empty)
- Check Use SSL.
- Uncheck Validate Software Title Definitions.
- Click Save.
- Click Test.
- Click Test (once more), to confirm connectivity.
With Definitions added to Jamf Pro, we can add patch definitions to check the patching level of titles deployed via Jamf Auto Update to your Jamf Pro managed Mac computers.
We’ll next add a patch definition for Jamf Auto Update Catalog Browser:
-
In your Jamf Pro instance, click Settings in the sidebar.
-
In your Jamf Pro instance, click Computers in the sidebar.
-
In the Content Management section, click Patch Management.
-
Click + New.
-
Click the disclosure triangle next to definitions.datajar.mobi
-
Click the + button next to Jamf Auto Update Catalog Browser
-
The patch definition for will now have been added to Jamf Pro.
For more information on patch reporting within Jamf Pro, click here.
Further documentation
You have now successfully installed and configured Jamf Auto Update. Please ensure you review the Jamf Auto Update - Administrators Guidefor more detailed information on creating additional policies.
For information on the settings available to customise the Jamf Auto Update experience, please see the Customising Jamf Auto Update article here.
And for how to rebrand Jamf Auto Update, please see the Rebranding Jamf Auto Update article here. Additional supporting documentation can be found here.
Need further support?
Automate. Simplify. Succeed. If you still require assistance with us or have any further questions, please raise a ticket with our support team.
Alternatively, please see our frequently updated knowledge base articles for reference.