Introducing Munki Theme Maker
For many Mac administrators in a variety of sectors an open source tool called Munki, a patch management tool, is more than prolifically used. Our mantra of being a technology agnostic consultancy agency exposes us to a wide range of Mac tools. Munki is one that we internally have used for years.
Last year at the Mac Admins Conference at Penn State we gave a talk and showed off a script that we had been using internally to take the Munki product and make it fit more seamlessly into the look and feel of any organization. On that note we are pleased to announce the next step release of that then script.
Munki Theme Maker takes the concepts of the script that we demonstrated and wraps it with an elegant GUI interface making it easy for even the novice Mac Admin to take it off the shelf and start creating a custom and branded experience for their Mac users.
Munki Theme Maker allows you to create custom color based scheme themes for Munki. This app picks up on the amazing work of the Munki project and the Munki Rebrand project. The theme maker allows you to have a more modern color schemed UI made for your brand. Change the background color, featured item color and the sidebar link colors. The default new theme includes new icons on the top header row. More modern and clean rounded corner look and feel. Adding the sidebar to category pages as well as the main header slideshow or header graphic area.
Usage
Upon launching the app you must set all variables. If any variables or customized items are missing it will fail to run. The most important items are the Source Folder (Where Munki is downloaded and compiled), the Output folder where you will get 2 copies of Munki the unbranded and the branded and themed versions. The App Name (the new name of the Managed Software Update App that you wish it to be). The signing certificate authority (for use when signing the final package - Developer ID Installer) and the App certificate authority (for used to sign the binaries of Munki - Developer ID Application).
Pick the colors of the theme in the next tab (Colors) and then finally set the icon that you will use for the final touch. Once all set hit “Generate” and let the Munki Theme Builder do its thing.
It will download and clone into your source folder Munki, Munki Rebrand and the base Munki Theme with all injectable files. Injection happens, and then Munki builds.
The App has backwards compatibility for Munki version 4.1.4 as of writing this through to version 5.0.0. We plan to relase new baseline themes and modifications for each dot iteration of the Munki core release.
Open Source
We are opening this up to the Mac Admin’s community with hopes that Munki Theming and or native support for easy to manage themes for the Munki GUI interface will become more prolifically used and supported. Version 1.0 is now available for download in full source mode or as a precompiled and signed (not notarized ) download. Pull requests are welcome!
Here is a little video of it in action. We hope you love it!
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.03 · Low AI Influence
Summary
Munki Theme Maker is a GUI interface for creating custom and branded themes for Munki. It allows users to change the background color, featured item color, and sidebar link colors. The default new theme includes new icons on the top header row and a more modern and clean rounded corner look and feel.
Related Posts
Setting up Ollama on macOS
Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.
