We were shown how to use Composer to package applications from DMGs when we purchased Jamf Pro. You install the app to Applications via the DMG. Then you copy the app to Composer and supposed to change the perms to 'root' & 'wheel' and 'Apply Owner and Group to Frameworks and All Enclosed Items' to the uppermost folder (Applications).
My question is, some apps come as a Package (.pkg). Can I just import the package to Jamf to push the app to users? Do the permissions really matter? The 'root' and 'admin' permissions are always there in Composer, all of our associates are admins on their Macbooks.
Thanks in advance for any insights into this.
If the vendor provides the .pkg, there's no need to re-invent the wheel. Yes, you can import to Jamf and push.
Having said that I would use Suspicious Package (or something equivalent) to inspect and validate the package before pushing. Of course, test, test, test.
@gurduv with Packages, doesn’t one have to check the disk to see where things were installed? For instance, if an Adobe CC app is added, there’s the app in /Applications, but there might be things installed in /Library or ~/Library. Composer would look for all those things, but with Packages, wouldn’t it need to be looked for manually to add to the package being created?
I get the following "this application was downloaded from the internet", select ok to proceed... Try to go to the vendor example FireFox, Chrome, etc... for the PKG.. furthermore. I don't like using composer.. it takes a real long time to package stuff.. I recommend "Packages"... http://s.sudre.free.fr/Software/Packages/about.html