Automating Manual munki Imports with autopkg – Part 3: Pro Tools

In previous posts (macOS erase & install, Autodesk Maya), I discussed how I created recipes for importing different software titles that I’d previously processed manually.

In this third part, my focus is on Pro Tools. The challenge with automating this task is that any given release includes in the downloaded DMG the Pro Tools install as a PKG as well as both the required Codecs and HD Driver PKG installers. These supporting installs are tied to the specific Pro Tools release and which must be installed before Pro Tools. The core question then was using the available processors, could I create the necessary Pro Tools munki item while simultaneous making the applicable Codecs and HD Driver versions a part of the item’s requires array?

TL;DR – you can reassign any collected autopkg output variable to any other desired variable for later use.

See more info past the jump.

Read More

Automating Manual munki Imports with autopkg – Part 2: Autodesk Maya

In a previous post, I discussed how I created a .munki recipe for importing macOS installers into a munki_repo with the necessary settings to complete an erase and install.

In this second part, my focus is on Autodesk Maya, which has long been a challenge for admins. As an education institution, we have a standalone license, so while this post does not address network licensing it may still prove helpful.

TL;DR – you can create a .munki recipe that imports a DMG with an app inside but which ultimately removes the normally created installs array and instead creates an artificial package receipts array!

See more info past the jump.

Read More

Automating Manual munki Imports with autopkg – Part 1: macOS Installers (Erase & Install)

Before recently leaving my current job, I started to go through a number of my processes for manually importing various software titles in a last-ditched effort to transition these tasks into something more automated. Taking inspiration from the Adobe 2020 autopkg recipes and since the download / collection part for some software has to be done manually, I decided to work on creating autopkg recipes to more easily bring these software titles into our munki_repo.

In this series, I’m going to walk through and discuss the challenges of bringing some of these software items into munki with autopkg. The intended use of these recipes is that an admin would copy the software installer into a desired folder which the recipe would reference and process accordingly. Any of the setup of autopkg or munki is far outside the scope of this and future posts.

In this first part, my focus is on importing macOS installers, intended specifically for use in an erase & install configuration.

See past the jump for more info.

Read More