Challenge: Prevent certain app from updating / freeze stable version of app

durian
New Contributor

Context
A healthcare institution with 1'000+ managed iOS devices. In the past we experienced problems with buggy new releases of a business critical app. Stable versions are available though.

We currently don't use any Software Update Server (like NetSUS) or Caching Server in our environment.

Goal
We want to be able to freeze a known stable release of this app on our devices and prevent them from updating to the latest version available in the app store.

Before the new app versions gets released into production (which currently is always the case, whenever a new version of the app becomes available - chaos and panic ensured) we Admins want to be able to test new releases of the app in our lab and block updates if necessary/if latest version is too buggy.

Seems like a simple task but currently we don't know how to achieve this.

How to achieve this kind of app (update) management?
As Windows admin I'm used to have full control over what kind and versions of software gets installed on our clients. In the iOS/App world this seems kind of challenging. How did you solve this problem in your environment?

Would it be possible to set up a local caching server in our environment and only cache a stable release of the app? There should be ways to prevent the caching server from getting the latest version of the app from the app store. Thus it would only distribute releases of the app to our iOS devices that we Admins approved.

There might be easier ways to achieve this though. Any ideas?

2 REPLIES 2

easyedc
Valued Contributor II

So I'm shooting in the dark, but won't VPP solve this? We don't manage iOS, just Macs, and VPP on Macs does allow me to use the MAS and then lock it at a release (technically I can allow updates, so the same thing but opposite of what I said). Have you checked there?1bd7199b3723430284ade51e950e4289

cddwyer
Contributor

@easyedc I wholeheartedly agree. That's exactly how I'd have done it. However, you'd need to set this at the time the the stable version was the 'current' one.