Install app update for non admins

[Eskobar]

Hi all,

Non-admin users cannot run this update. Is there a way to cancel/skip/run the update from jamf ?

Re-packaging the app will cause user’s enrolment loss.

Thanks,

[geoff_widdowson]

Not sure why repacking would be any issue, but you know the application I don't. Can't you re-package and make the update available in Self Service? Deploying new version tend not to affect user data/settings. You should at least re-package for future use nayway, and once done test it out to see if it really does cause the problems you say.

[sdagley]

@Eskobar Why do you need to re-package the PingID app? There appears to be a .pkg installer available from https://www.pingidentity.com/en/resources/downloads/pingid.html, and that should be something you can reply via Jamf Pro without any re-packaging needed.

As @geoff_widdowson mentioned in their reply deploying the new version should not impact the configuration of an existing install.

[AJPinto]

Honestly, this is a question for the PingID vendor. It would really be down to how the app works, and where it stores its "Enrollment".

• If the package does not override the files that identify enrollment like certificates or plists, you should be able to just push the package and be done with it. Most vendor packages have logic in the post install scripts to preserve the existing environment on the device.
• If the package does override the files that identify enrollment, you need to open a ticket with the vendor. Trying to rebuild their application from source to change its behavior would void any support for your environment, as well as voiding the developer certificate, in addition to being beyond your pay grade. 

Reading their documentation and it suggests your enrollment is preserved. However, I cannot stress enough; reach out to the vendor to ask questions. I would be floored if they did not have an upgrade process that did not require users to have admin access.

PingFederate Server (pingidentity.com)