Now we need to tell ManagedInstalls where to find munki. This will install the Managed Software Updates app in the clients utility folder. Go here and download the munki tools and install them. In order for clients to see the munki server you need to install the munki tools on each client. (again, my responses are in red, for a list of commands with manifestutil type help)Įntering interactive mode… (type “help” for commands)Īdded test to catalogs of manifest test_munkiĪdded Firefox to section managed_installs of manifest test_munki So now that we have Firefox in our repo we need to tell munki to offer it to our clients. First I need to create a manifest The manifest is just the file that tells munki what software to offer. ![]() Rebuilding catalogs at /Users/Shared/munki_repo ….Īfter wards you can go to the munki_repo/pkgs folder and see that munki did actually copy the Firefox installer to the right folder. Saving pkginfo to /Users/Shared/munki_repo/pkgsinfo/Firefox-18.0.2… Upload item to subdirectory path : (you could say apps/web_browsers if you wanted to create folders and organize your software)Ĭopying Firefox 18.0.2.dmg to /Users/Shared/munki_repo/pkgs/Firefox 18.0.2.dmg… My responses are in red.Ĭatalogs : test (you can put in whatever you want to name your catalog) Don’t worry if you get it wrong, this is just a test, you should do this several times to feel comfortable. You should then see a list of information after just a few seconds. Munkiimport ~/Downloads/Firefox\ 18.0.1.dmg Run the munkiimport command and then just drag the Firefox dmg on to the terminal window. Path to munki repo : /Users/Shared/munki_repo ![]() From here I”ll only list the actually command and not the usr/local/munki If you add it to the search path in step 5. Type this at the command line: usr/local/munki/munkiimport -configure We need to set up munki first with some basic information like where we want the folders to be where we are going to put software. For example if you do this step you only need to run: munkiimport –configure instead of /usr/local/munki/ munkiimport –configure PATH=$PATH\:/usr/local/munki export PATH – this step simply adds the path to the bash search path so you don’t have to add the path with every terminal command. Optional: Adding /usr/local/munki to bash search path Step 4: Turn on Web Sharing in the Sharing preferences paneĭownload and install the munki tools … YOU WILL HAVE TO RESTART IMMEDIATELY. Installing Munki On A Mountain Lion Server ![]() This entry was posted in Mac Admin, Terminal and tagged bash, Homebrew, OS X, Shell Script, Terminal, Yosemite Terminal on Maby Nic. So out of the gates you have a custom terminal. ![]() Now that you can script it, you can add it to a post deployment script or launchagent that runs on the first login. #!/bin/bash #set Terminal defaults sudo -u $USER defaults write /Users/ $USER/Library/Preferences/ "Default Window Settings" "Homebrew" sudo -u $USER defaults write /Users/ $USER/Library/Preferences/ "Startup Window Settings" "Homebrew" #set window width to 120 sudo /usr/libexec/PlistBuddy -c "Add :Window\ Settings:Homebrew:columnCount integer 120" /Users/ $USER/Library/Preferences/ defaults write /Users/ $USER/Library/Preferences/ "NSWindow Frame TTWindow Homebrew" " 366 0 0 1280 777 " #restart Terminal killall Terminal exit 0 You can simply change “Homebrew” to whatever terminal theme you want. I always find myself changing it to Homebew. I think why aren’t I scripting this? I hate the default white terminal theme that comes in OS X. Scripting The Default Terminal Theme In OS XĪnytime I find myself doing a repetitive mundane task. This entry was posted in Uncategorized and tagged bash, bluetooth, Geektool, ioreg, macOS, Magic Keyboard, Magice Mouse, Terminal on Februby Nic. MousePercent=$(ioreg -r -l -k "BatteryPercent" \ | grep -A 9 "Magic Keyboard with Touch ID" \ KeyboardPercent=$(ioreg -r -l -k "BatteryPercent" \
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |