![]() The cookie is used to store the user consent for the cookies in the category "Other. This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. 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. 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. 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. Add the Pro Tools 12 installer item into the relevant manifest for your department.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”.Use the contents of the “ProTools12_Post-Install-Script.sh” script for this post-install script.Use `pkginfo` or Munki Admin to add a post-install script to the “Install Pro Tools 12.x.x.pkg” pkginfo.Add all four packages into your Munki repo.This one is also simple if you have had previous Munki administration experience: Chuck all 5 items into your deployment config, or into the same policy.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”).Add all four packages as “install on boot drive after imaging” and the script as “At Reboot”.Run the script “ProTools12_Post-Install-Script.sh” at reboot. ![]() Install “Install Avid Codecs LE.pkg” at reboot.Install “Install Avid HD Driver.pkg” at reboot.Install “License Support.pkg” at reboot.Install “Install Pro Tools 12.x.x.pkg” at reboot.So now you have all five components needed to deploy Pro Tools 12. With a few tweaks (specifically lines 4, 6, 11, 12, 17, 20, and 21) this worked brilliantly for Pro Tools 12.Ī copy of the updated script can be found on our GitHub here. It so happens that there’s already a script for Pro Tools 11 that does this. Add new directories in to /Library/Application Support/Avid/Audio for Plugins.Add a Launch Daemon to start it at boot.Add it’s “shoe” tool to the /Library/PrivilegedHelperTools directory.Test deployment complete…but it still wants admin rights on first launch? Add all four to your deployment solution of choice. ![]() These all need to be added as ‘postponed’ or ‘on reboot’ installations. 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).Found in the “Driver Installers” directory. The “Install Avid HD Driver.pkg” installer package. ![]() Found in the “Codec Installers” directory.
0 Comments
Leave a Reply. |