At 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.
During our 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’ll update it periodically.
During our JNUC 2019 talk, another item James & I detailed was how we at dataJAR easily switch between the 100+ Jamf Pro instances we host.
Enter Jamf Switcher, the app to bring the word faff to the Jamf Marketplace!
For details on how this came to be, see below.
Within a 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: JAMFSoftwareServer.log Messages.
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.
During 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.