Deploy latest version at enrollment, but manage updates ourselves after that, how are people doing this?
We deploy an app via a Jamf Policy (pkg) that runs once a computer enrolls. Problem: the app updates constantly, so our uploaded package goes stale fast, and re-uploading a new pkg every release isn't sustainable.
Jamf's auto-patching (App Installers) would keep it current, but it also auto-updates the app across our whole fleet, which we don't want. We want to control update timing ourselves.
What we need:
- At enrollment, always install whatever's currently the latest version, no manually maintained package.
- After that, no self-updating in the background. We push updates ourselves, on our own schedule.
We've tried pointing installs at the vendor's "always current" download URL, disabling the built-in auto-updater via a config profile, and scripting our own update-push (mixed reliability so far, now looking at Installomator for that part).
Is this the standard approach or is there a cleaner way orgs handle this in Jamf?