I remoted in to the Mac and About This Mac claimed it was 10.10.4. Yet ARD was still reporting that the Mac was at 10.10.3.
#Outset mac install
By the time I checked the logs (/var/logs/outset.log in this case), it said the install had completed. I had expected to see the OS updater to take over the display, but instead, it appeared to login to the user account without any significant delay. Because of the way our Labs are setup, we have a restricted user account login automatically after (re)boot. This was much more successful, although it did not appear so initially. So I copied it again (since outset dutifully deleted it afterwards), changed the permissions (using ARD), and rebooted. Even though Apple's installer package was happy to run in the GUI with 644 permissions (execute not set), outset insists on root:wheel ownership and 755 permissions (execute set).
#Outset mac update
So I tried tested this on one the Macs that had not yet been upgraded using ARD and, once I put the 10.10.4 update package in /usr/local/outset/firstboot-packages, I had ARD restart the Macs. You need to understand, in the words of Joseph Chilcote, this was " another usage that would have never crossed my mind." In other words, who knows if it is going to work! I figured if I could copy the 1 GB update to the Macs in questions in the background, a manually-triggered restart should do the installation for me. But 10.10.4 is a pretty important update for security reasons, so I want to push it out as soon as possible. These runs can take days sometimes, as he is routinely dealing with hundreds of 1 GB images in a batch. So all is well until I get to the 5 computers where a professor is doing batch processing in Photoshop. When OS X 10.10.4 came out, I started pushing it out to my Lab Macs using Apple Remote Desktop (no Munki or Casper yet). I've just started exploring it, but it looks like it will have great potential for us.
Instead of having to write LaunchAgents and LaunchDaemons on your own, particularly for one-off tasks, you can just drop scripts or packages into an appropriately-named folder and let outset do the work for you. I hope many of you have heard of a nice little tool from Joseph Chilcote ( on Twitter) called outset.
0 kommentar(er)
