Posted on 02-09-2023 12:23 AM
I’ve pushed the policy to Monterey and Ventura machines but application won’t launch in Ventura due to it being an unidentified developer.
Even when I upgraded the Monterey machine to Ventura, it runs into the same issue.
How can make it so that it’s able to launch in Ventura? Is there a config file that needs to be setup and pushed out to machines prior?
Posted on 02-09-2023 12:46 AM
Hi,
open a terminal and issue the following command.
/usr/sbin/softwareupdate --install-rosetta --agree-to-license
try opening the app now.
Posted on 02-09-2023 04:06 AM
Well you are telling us explicitly that the app is from an unidentified developer, so that's the issue, it's missing a valid developer signature. When I last ran into this issue, I created a specific Jamf Pro policy and pushed it to the users who needed the app. The policy uses Files and Processes to execute the application manually from the terminal.