We're using SCUP to publish updates for 3rd party apps. In our environment, users can manually update the apps themselves (such as Adobe Reader and Firefox).
However, if a person, for example, manually updates Firefox from 20 to 21, and then we deploy (thru SCCM) the update of 20.0.1, the install then gets stuck in a loop on the client side because the client is now running version 21 and SCCM is trying to install 20.0.1.
This happens with other apps as well.
Not allowing manual updates by the user is not an option.
Is there a way to prevent this situation from happening?
