Jamf App Catalog vs Software License

​@Lion55 Licenses aren’t needed for apps from the Jamf App Catalog. 

If the app has a license (e.g.: Adobe device license), then you’ll want to install the license package as a separate policy.  If the app has a license that is a code input after installation, then have a smart group filled with the device in it post install and have a script run to apply the code or whatnot.

​@Chubs Our Adobe EDU licenses must be different. I don’t have to install a separate license package.

You can download just the license file in a pkg for device based licenses.  The package creator online has the ability to do that - just have to finagle it a bit.  That’s how I did it when I worked for EDU.

​@ktrojano / ​@Chubs : you can create the file path in Jamf composer for licenses as an PKG, but it doesn’t work when upgrading the app? any thought on my error message attached? 

IMO: Don’t use composer. Packaging apps/files is an old technology. 

Should be able to do a one liner script in files and processes under a Policy to add the license file. Something like this:

mkdir -p /Users/Shared/TechSmith/Snagit && echo "12345678910" > /Users/Shared/TechSmith/Snagit/LicenseKey

**Do not add a file extension to the file. Snagit doesn’t like that. 

​@Lion55 I’m glad you figured it out and got it working!

Yep - permissions will get you every time.  I also don’t use composer because of things like that.  I’d recommend using a script to set this as it’s much more dynamic.

​@Chubs : I do normally script for some these actions, but on this process it was quite straight forward without having to debug, thanks for you and Kim support!

I believe in things being dynamic and scalable - meaning little-to-no maintenance required.  

If you’d like to brainstorm what I’m thinking about, shoot me a PM. :) 

Will do, Cheers ​@Chubs 🙂