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
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
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.
Did you sign the package?
Did you sign the package?
How would I sign the package? Im a fairly new to jamf, this was my process of creating the package.
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!
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!
Thank you, I will check the documentation.
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!
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...
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.