Note: Regarding Running a HTTP Munki Repo on OS X Yosemite Server Tune in for the next part where I’ll discuss upgrading the Munki Clients.įor these blogs, I’d always recommend reading the documentation (as Munki is a powerful tool) over at its new home on GitHub.Īs 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. As always, I hope it helps someone out and gets you onto the new (and awesome) Munki v2.
Firefox for mac 10.10.1 software#
The icon will be shown next to the item in the new Managed Software Centre client application.įollowing on from the above, I added Firefox to the optional installs on my test Mac and this is how it looked in the new client application:.Finally, if successfully, it’ll add the path to the icon into the pkgsinfo file.If a suitable Icon is found, it’ll upload the icon into the ‘icons’ directory on the munki_repo (creating the directory if not present), with the ‘.png’ as the filename.This generally only works for DMG or standard Apple pkg installers. If not, it’ll offer to try and extract one. Munkiimport will first check if the Icon already exists matching the name of the Item.
Icon is a little different from the other two.Simply enter the desired Developer name and it’ll be added to the pkgsinfo file for the item.Again, the most benefit would be seen if this item is an optional install. Allowing you to manually specify the Developer you’d like to have item displayed under.Simply enter the desired Category and it’ll be added to the pkgsinfo file for the item.The most benefit would be seen if this item is an optional install. Allowing you to manually specify the Category you’d like to have item displayed under.This is in the form of three new (optional) questions asked when importing an item: With the new options, some changes were made to the Munkiimport command line tool to simply take advantage of these. As mentioned on the previous ‘part 2’ blog on step 7, if this Mac will not be running Munki client, simply use the ‘Customize’ option to deselect the “Managed Software Centre” and “Munki launchd agents” whilst running the installation. Administration Mac Upgradeįor your administration Mac, run the updated Munki 2 installer. You could create this manually (say if you don’t have permissions to create new directories at the munki_repo root), just ensure it has the same permissions as the other directories, for example the pkgsinfo directory. Now this folder will be created on demand when you first use the updated munkiimport tool to upload a package and create an icon for it. To be honest, there’s only one repo server-side change for a generic setup and that’s the inclusion of an ‘icons’ folder at the root of the Repo.
Firefox for mac 10.10.1 upgrade#
Server and Client OS: OS X Yosemite 10.10.1Įxample Package: Mozilla Firefox v35.0.1 Repo-side Upgrade Just for clarification, my demo setup for these instructions and screenshots is as follows: Rather then argue semantics, please assume that if I use the terms ‘Munki Server’ or ‘Munki Repo’ I’m referring the same thing, specifically the server that hosts all the Munki data you are serving to your clients. This blog is designed as an ‘updater’ blog to my previous two Munki blogs: “Configuring Munki for a Mac Server” and “Munki Configuration Part 2: Admin Mac”.Īlso, I realised in my intro blog, I used the term ‘Munki Server’ for the Munki Repo and I got a little stick about it. Welcome to the second 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!
0 kommentar(er)
