Pro Tools 2021.7 Helper Tool Install Prompt

Good morning!

Yep, figured out the same thing this weekend. Tried to upload an image was got an error "You do not have permission to upload images." But my screenshot looks identical to yours @rrouleau.

For anyone else that runs into this, package up the items in @rrouleau screenshot 🙂

Running into the same issue on a small Media lab. Each user is prompted for the Pro Tools helper to be installed with admin creds. The files listed in the above solution have been installed using the pkg method shown. Anyone know a way to get this installed for all/new users and prevent the prompting? 

Thanks!

Just curious if you happened to move to the 2022 version and have to re-visit this?  I tried to implement your fix in the 2022 version, but when I launch Pro Tools, the helper error is gone but the application never launches (only bounces and bounces and then ends).

Also, I was curious the scripts, settings and snapshots folders on the left under sources, where did those come from?  Do they contain files that are needed?

Thanks!

@bbarciz  I am no longer using a package to deploy the avid shoetool file.

I have now added a Files and Processes Execute Command to our Protools installer package to copy the file over (This works for our environment with PT 2022.7).

ditto /Applications/Pro\\ Tools.app/Contents/Library/LaunchServices/com.avid.bsd.shoetoolv120 /Library/PrivilegedHelperTools/ 

Screenshot Attached:

Thanks for the idea.  Do you not have to do anything with the plist file into the LaunchDaemons folder?

I don't recall where I got this Pro Tools postscript install, but it still works for me via Self Service:

#!/bin/bash
# Copy the com.avid.bsd.ShoeTool Helper Tool
PHT_SHOETOOL="/Library/PrivilegedHelperTools/com.avid.bsd.shoetoolv120"
/bin/cp -f "/Applications/Pro Tools.app/Contents/Library/LaunchServices/com.avid.bsd.shoetoolv120" $PHT_SHOETOOL
/usr/sbin/chown root:wheel $PHT_SHOETOOL
/bin/chmod 544 $PHT_SHOETOOL
# Create the Launch Deamon Plist for com.avid.bsd.ShoeTool
PLIST="/Library/LaunchDaemons/com.avid.bsd.shoetoolv120.plist"
FULL_PATH="/Library/PrivilegedHelperTools/com.avid.bsd.shoetoolv120"
rm $PLIST # Make sure we are idempotent
/usr/libexec/PlistBuddy -c "Add Label string" $PLIST
/usr/libexec/PlistBuddy -c "Set Label com.avid.bsd.shoetoolv120" $PLIST
/usr/libexec/PlistBuddy -c "Add MachServices dict" $PLIST
/usr/libexec/PlistBuddy -c "Add MachServices:com.avid.bsd.shoetoolv120 bool" $PLIST
/usr/libexec/PlistBuddy -c "Set MachServices:com.avid.bsd.shoetoolv120 true" $PLIST
/usr/libexec/PlistBuddy -c "Add ProgramArguments array" $PLIST
/usr/libexec/PlistBuddy -c "Add ProgramArguments:0 string" $PLIST
/usr/libexec/PlistBuddy -c "Set ProgramArguments:0 $FULL_PATH" $PLIST
/bin/launchctl load $PLIST
mkdir -p "/Library/Application Support/Avid/Audio/Plug-Ins"
mkdir -p "/Library/Application Support/Avid/Audio/Plug-Ins (Unused)"
chmod a+w "/Library/Application Support/Avid/Audio/Plug-Ins"
chmod a+w "/Library/Application Support/Avid/Audio/Plug-Ins (Unused)"
mkdir /Users/Shared/Pro\\ Tools
mkdir /Users/Shared/AvidVideoEngine
chown -R root:wheel /Users/Shared/Pro\\ Tools
chmod -R a+rw /Users/Shared/Pro\\ Tools
chown -R root:wheel /Users/Shared/AvidVideoEngine
chmod -R a+rw /Users/Shared/AvidVideoEngine
# Get rid of old workspace
rm -rf /Users/Shared/Pro\\ Tools/Workspace.wksp

rm -rf "/Applications/Avid/Application Manager/AvidApplicationManager.app"
rm -rf "/Applications/Avid/Application Manager/AvidAppManHelper.app"
exit 0

Hello,

I am working towards creating a Pro Tools installation policy and have had no luck getting it to work at all on my end. Could you provide a screenshot(s) that shows how you've configured your packages (if this is still the same way you're deploying this)? Any help would be greatly appreciated.

My process is to download the .dmg from AVID

I pull the .pkg out of the .dmg and rename it.  

Upload the .pkg to JAMF.

I deploy the .pkg with the post script that I have written further down in this thread.

Hello!

So the process that I have used it to pull the pkg out of the download and upload that into Jamf.  I also do this with the plug-ins (add-ins, whatever they are called).

Then in my policy, I install that pkg file for the main application along with the pkg files from the plug-ins that are requested.

I then have a restart step in place.  I'm not entirely sure why this is to be honest. I was thinking it had to do with the upgrade in Pro Tools version in the past.

I then run a files and process step to execute the following command:

ditto /Applications/Pro\\ Tools.app/Contents/Library/LaunchServices/com.avid.bsd.shoetoolv120 /Library/PrivilegedHelperTools/

I think there was info about this farther up on this forum page.

I then have a note that after the software is installed, a technician must install the helper item on first launch on each computer.  I don't think I successfully found any way around this (or didn't dig much because our install base of this is only a couple of labs of computers).

Hope that helps! Feel free to reach out with any further questions.

Thank you very much for the info.

Since I basically need all of the plug ins, I ended up splitting them into two policies of 20 plug ins each. 😵 They all look to have installed properly  😀

I ended up using the script that @mhinsz provided below and it seems to have worked, I'm not sure if I should also use the one you've provided as well or what the real difference would be.

I've got another question though, we use an iLok license server on premises and the IP address of that server is required for all machines that will run Pro Tools (30+ machines).

Would you know if it's possible to include this IP address somewhere in my policies that could make it's way through? Perhaps as a separate script/policy?

You are welcome.  Glad it all came together for you! I would just use the script that you did use, I mean, if it seems to be working for you, I wouldn't try to change it at this point! lol. 

Curious, did you have to do anything with the helper item on first launch?

Unfortunately, I don't have any thoughts on the iLok.  We are licensing with local iLok USB dongles, so I don't have any experience there.  My gut instinct would make me think it would perhaps be in a .plist file but I'm not sure.  Also perhaps some command you could run during install but I don't know what that would be or what application to start looking at help commands for.

Yes.  We also are using network licenses.

First, use the iLok License Manager / Preferences / My Connections / My Network Connections to add your network license server IP address.  Apply the changes and close the iLok License Manager.

Then, use Composer and grab the preference file from /Library/Preferences/com.paceap.eden.floating.v1.client.prefs

Create a .pkg of that file and upload the package to JAMF.

Create a policy that installs the package above and create a post install script reload the iLok launch agent:

launchctl unload /Library/LaunchDaemons/com.paceap.eden.licensed.plist
sleep 10
launchctl load /Library/LaunchDaemons/com.paceap.eden.licensed.plist

Deploy the .pkg and post install script to your devices.  

Thanks for the reply, I actually had some good Google search luck and managed to find this article here: https://community.jamf.com/t5/jamf-pro/configuring-ilok-license-server-clients/m-p/272582

This seems to explain the same process pretty well, I am going to try it out soon.

If that doesn't work, I'll try your approach :)

Is this script still working for you? I’m trying it with OS 15.5 and Pro Tools 25, but it throws errors.