Hi all. Welcome to the third part in my Munki 2 blogs: The on-going guide to get Munki newbies up and running with a basic setup to cut your teeth on!
My Demo Setup
Just for clarification, my demo setup for these instructions and screenshots is as follows:
Server and Client OS: OS X Yosemite 10.10.1
Server app: 4.0.3
Munki Tools: 2.2
Example Package: Mozilla Firefox v35.0.1
Upgrading the Client Tools
Nice and easy, simply install the new tools. Version 2 of Munki will happily use the same settings in your preference file.
Just a word of warning, the behaviour of the Launch Daemons for Munki 2 have changed and so if you do not push out the Munki v2 LaunchD installer, you will have unexpected behaviour on your clients (not something you want).
Ah, you may have noticed that this will add an additional requirement onto the upgrade install, your clients devices will need to reboot to complete the install.
Just bear these in mind when upgrading the client installations.
Obtaining the Munki Tools
New Pretty Application!
As you may notice, the previous “Managed Software Update” application in the Utilities folder has been replaced by a shiny new, ‘Mac App Store’-like “Managed Software Centre” located in the Applications folder.
Open it up and have a look at the new layouts and additional information you can provide, like these screenshots!
Enough Client, what about Munki Admin?
Well, as always, Hannes has been keeping up with the Munki tools developer with his Munki Admin GUI solution for administrating the server. This includes setting icons, Developer and categories!
Double click one of your installer items to access the extra settings on the first tab.
There you go. As before, I hope it helps someone out and gets you onto the new (and awesome) Munki v2. Tune in for the next part where I’ll discuss upgrading the content of your Munki Repo, with the Munki 2 goodness.
For these blogs, I’d always recommend reading the documentation (as Munki is a powerful tool) over at its new home on GitHub.
As always, if you have any questions, queries or comments, let us know below and I’ll try to respond to and delve into as many as I can.
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. Amsys 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.