EDIT: 1.5.1 released, removing the option to not post notifications for items with a category due to the category not always being written to the ManagedInstallReport.plist when installed. A PR to Munki will be needed to resolve, then this can be re-added.
Tonight brings an update to
jamJAR. This update adds an option to not post notifications for items with a category & also adds support for the forthcoming dataJAR Notifier.app (to post banner & alert notifications as needed).
This is the last Python 2 release of
jamJAR, the next release will utilise Munki’s shipping Python 3 & will also officially support Apple updates via Munki & the new workflows introduced Munki 5.
Over the past weekend in
#autopkg Slack channel in the MacAdmins Slack, some fellow admins saw their recipes erroring with a non-zero exit status of 60.
dataJAR we only run our AutoPkg recipes weekdays, but sure enough we hit the same issue come Monday.
Below is some more details, as well as a proposed fix for at least the short term.
dataJAR, I recently worked with a customer which wanted to make use of Jamf Pro’s Enrollment Customization option.
However, with everything setup, we were presented with the message
“Error <kCFErrorDomainCFNetwork:303>” whenever trying to load any of the defined PreStage Panes.
I reached out to Jamf Support, but they hadn’t see this issue & searching the
macadmins Slack didn’t bring up anything either.
Long story short (& in an attempt to not create my own
DenverCoder9 moment), we discovered the issue to be down to the environments ingress controller being configured with HTTP/2 support by default.
As soon as we disabled HTTP/2, everything worked as expected.
Hope this helps someone else too.
We’ve just released a little update to Jamf Switcher, bringing the app to 1.1
This update strips /?failover from a JPS URL when writing to the com.jamfsoftware.jss.plist for the Jamf Applications, but keeps /?failover when opening Safari.
1.1 is available now, &
Jamf Switcher should prompt for the update when launched or can be installed via the “Check for updates” menu from within Jamf Switcher itself or manually downloaded from here.
With the release of Jamf Pro 10.20.0, Jamf has fixed
[PI-007508]. This is the PI for DEP Sync failing due to TLS changes being needed for on-prem installs & one which I blogged here.
The fix from Jamf forces TLS1.2 for connections to Apple for DEP/Automated Device Enrollment.
So, if you made a change to your TLS settings as I mentioned in my
previous blog post, you can remove those changes.
dataJAR, we’ve been running all datajar.mobi deployments with no TLS settings enforced via our setenv.sh for a couple of weeks now & all is syncing as expected.
Munki Catalog Browser is the last project that we released during our JNUC 2019 talk & is an app which allows a local macOS admin to easily list items in your devices Munki catalogs as well as exporting to CSV.
dataJAR, this is used to pass an up-to-date list of items available for deployment via our Auto-Update Framework.
dataJAR we migrated from multi-context Jamf Pro deployments to Kubernetes the January after Jamf Pro 10 was released. Migrating & updating customer Jamf Pro instances at the same time.
JNUC 2019 talk we detailed why we did this, & we have a repo showing the raw files which allow the how to happen. These can be found, here.
However, that repo has a large explanatory gap.
As such, if containerising Jamf Pro is something that is of interest, I’d recommend Jamf’s own
Kubernetes Manifests repo.
Ours can be used to cross reference, & we update ours periodically.
JNUC 2019 talk, another item James & I detailed was how we at dataJAR easily switch between the 100+ Jamf Pro instances we host.
Jamf Switcher, the app to bring the word faff to the Jamf Marketplace!
For details on how this came to be, see below.
few posts here & during our JNUC 2019 talk, James & I detailed how we at dataJAR deal with managing 100+ Jamf Pro & released a few repos with various items we use day-to-day.
This blog post is concerned with one of those repos, which is titled:
The repo can be accessed via the hyperlink above.
This repo contains a list of messages which can appear in the JAMFSoftwareServer.log, with a note as to what action might be required due to the messages being generated.
For more details see below, else click the link & PR’s are welcomed to expand the repo.
JNUC2019, I had the honour of once again presenting alongside my colleague, friend & founder of dataJAR James Ridsdale.
The talk was on some of the methodologies
dataJAR employs to fully manage 100+ Jamf Pro instances as a distributed team whilst maintaining a high standard throughout.
During the talk we released a few GitHub repos with items that we use day-to-day to help our fellow admins. These will be covered in further detail over the few weeks.
A link to the talks video can be found below, alongside the talks main GitHub repo.