Posted on 03-19-2024 02:49 PM
I created a policy to install a package (minecraft education). I put startup and login as the triggers. When I check the logs i see the message below "Installation failed. The package could not be verified"
Any ideas how to fix this error? Thanks
Posted on 03-20-2024 07:26 AM
Usually when I see this error, its network related. Maybe SSL redirection. What happens if you turn off package validation? JSS>>Settings>>Computer Management>>Security>>Package Validation = Never.
Posted on 03-20-2024 08:52 AM
Did you sign the package?
Posted on 03-20-2024 09:01 AM
How would I sign the package? Im a fairly new to jamf, this was my process of creating the package.
Posted on 03-20-2024 09:38 AM
Jamf has a create documentation for it:
Although once you have the cert you can install it on your machine and then tell composer to use that cert in preferences.
Also since you are new, one of the pit falls of composer is that it grabs the permissions for the file you put in there. So if you are grabbing files from user folder, or preferences, make sure to correct the permissions. I usually fix the put level and tell it to "Apply Permissions to private and All Enclosed items"
Good luck!
Posted on 03-20-2024 09:54 AM
Thank you, I will check the documentation.
03-22-2024 01:17 PM - edited 03-22-2024 01:19 PM
I usually fix the put level and tell it to "Apply Permissions to private and All Enclosed items"
The concern with using Apply Permissions to MyAppName.app and all Enclosed Items option, is that everything in the app will become executable. That would run afoul of Apple's Developer guidelines, and might even raise some security audit flags, not to mention the developer most likely didn't intend that to be. :)
Might want to instead first set owner=root & group=wheel, then select the Apply Owner and Group toMyAppName.app and All Enclosed Items option.
Example...