Packaging Pro Tools 12 for deployment

Hi All. Again, this is gonna be another one of those “I had to do something for a client and so I thought I’d share” blogs. Maybe I should start a new series on these 🙂

This one revolves around turning the Pro Tools 12 installation into something that can be deployed by your Mac deployment / patching solution of choice.

Please Note: These notes have been written on the assumption of using an iLok licensing management solution and so doesn’t deal with any licensing models outside of this.


Credit where credit is due (aka standing on the shoulders of giants)

Before I start, I have to confess I have pulled most of what I needed from work others have done for Pro Tools 11. Namely:


The downloaded package

So, you’ve downloaded your Pro Tools 12 package from Avid and it looks little like this:

Screen Shot 2016-02-05 at 10.47.16

This is what you’ll need:

  • The “Install Pro Tools 12.x.x.pkg” installer package

Pro Tools 12 installer





  • The “Install Avid Codecs LE.pkg” installer package. Found in the “Codec Installers” directory.

Avid codecs




  • The “Install Avid HD Driver.pkg” installer package. Found in the “Driver Installers” directory.

Avid HD driver



  • A copy of the iLok License Manager installer package (“License Support.pkg”), grabbed from here (yes it’s in a DMG, in a ZIP file).







These all need to be added as ‘postponed’ or ‘on reboot’ installations. Add all four to your deployment solution of choice.


Test deployment complete…but it still wants admin rights on first launch? 

Yup…. that’ll be the Pro Tools app trying to:

  • Add it’s “shoe” tool to the /Library/PrivilegedHelperTools directory
  • Add a Launch Daemon to start it at boot
  • Add new directories in to /Library/Application Support/Avid/Audio for Plugins
  • Add new directories to /Users/Shared

It so happens that there’s already a script for Pro Tools 11 that does this. With a few tweaks (specifically lines 4, 6, 11, 12, 17, 20, and 21) this worked brilliantly for Pro Tools 12.

A copy of the updated script can be found on our GitHub here.


Bringing it all together

So now you have all five components needed to deploy Pro Tools 12. Let’s bring that all together.

The process would need to be as follows:

  1. Install “Install Pro Tools 12.x.x.pkg” at reboot.
  2. Install “License Support.pkg” at reboot.
  3. Install “Install Avid HD Driver.pkg” at reboot.
  4. Install “Install Avid Codecs LE.pkg” at reboot
  5. Run the script “” at reboot.


For Casper:

This one is simple:

  1. Add all four packages as “install on boot drive after imaging” and the script as “At Reboot”.
  2. Set the priority for each package so that the main Pro tools installer runs first (e.g., ’10’ for “Install Pro Tools 12.x.x.pkg”, ’11’ for “License Support.pkg”, “Install Avid HD Driver.pkg” and “Install Avid Codecs LE.pkg”)
  3. Chuck all 5 items into your deployment config, or into the same policy.
  4. Test, then deploy as needed!


For Munki:

This one is also simple if you have had previous Munki administration experience:

  1. Add all four packages into your Munki repo.
  2. Use `pkginfo` or Munki Admin to add a post-install script to the “Install Pro Tools 12.x.x.pkg” pkginfo.
  3. Use the contents of the “” script for this post-install script.
  4. Again, edit the `pkginfo` or use Munki Admin to add the three ‘non-Pro Tools’ installers (specifically “License Support.pkg”, “Install Avid HD Driver.pkg” and “Install Avid Codecs LE.pkg”) as “Updates for” the “Install Pro Tools 12.x.x.pkg”
  5. Add the Pro Tools 12 installer item into the relevant manifest for your department.
  6. Test, then deploy as needed!



Hopefully that’ll help out those who are fighting Pro Tools to deploy nicely! As 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.

The usual Disclaimer:

While the author has taken care to provide our readers with accurate information, please use your discretion before acting upon information based on the blog post. Amsys will not compensate you in any way whatsoever if you ever happen to suffer a loss/inconvenience/damage because of/while making use of information in this blog.


4 Replies to "Packaging Pro Tools 12 for deployment"

  • Phil Lo

    Awesome article; saved me a ton of time to sit and figure out. Appreciate it tremendously!

  • I’m seeing an issue with this that I’m wondering if you could confirm. When following these instructions we get a problem with the Pro Tools Video engine. When first launching as a standard user, I get an error that pops up with Pro Tools projects that have a movie.

    You can also manually turn on the video engine by doing the following: Launch Pro Tools, and then try enabling the video engine ( SETUP > Playback Engine – and ‘check’ Enable Video Engine ).

    If however, I launch with an admin account first (I don’t need to auth), and then try as a standard user, it seems fine. Interestingly, even though the error pops up, it works just fine playing back videos.

    I can post a video or look into it further, just wanted to see if others were having the same issue.

  • This seems to fail to install pro tools 12 using Casper as the pkg seems to fail when installing from the terminal. I got round this by dropping into Casper Composer and then recreating the pkg with no changes.

Leave a Reply

Your email address will not be published. Required fields are marked *

I accept the Privacy Policy * for Click to select the duration you give consent until.