Adam and Ryan talk about using autopkg to automate the mundane task of downloading updated versions of common software. Firefox, Chrome, anything Adobe, Flash, Java… all these applications (and many many more) need updated regularly on the systems you manage. But, you can’t just let end users do it because the newly released version may cause issues for some of your critical applications. So you may have found yourself just catching wind that a new version is out, downloading, importing it into you software management system, test the package, then deploying it out to your fleet. Well, autopkg automates the process of checking for the updates, downloading them, processing them (and importing them into your repository if you are using Munki).
In This Episode
In this episode we cover how we have set up autopkg to automate the tasks of monitoring, downloading, post-processing, and importing software updates for many of our software packages, as well as what our software update workflow looks like post autopkg.
Our AutoPKG Setup
- Setup on a Mac Mini
- Scheduled to run daily using LaunchDaemons
- Munki repository is automatically mounted to this mini
- AutoPKG downloads new versions
- post-processes the update
- Names the file how we want
- adds post/pre-install scripts
- adds to our Munki repository in the test group.
- Munki prompts to install new updates on our test user systems.
- Test users test/approve the update then manually approve it to be rolled out to all users.
Recipes are pre-built workflows that you can have autopkg run. Lots of pre-built ones are available online. You can build your own if you feel up to it.
Other software referenced
autoDMG – Used to build deployable OS X images from the “Install Mavericks.app”
Munki – Software management suite