Forgive me if this question has been asked already. I have Googled (Binged) far and wide and have not found any real posts that say what is the best option for this type of application scenario.
So, her goes...
Is there any scenario where you would revision an application instead of Superseding it?
An example I would like input on would be something like Adobe Reader. My obvious thought would be to if you are moving from a deploy of Reader 10 to Reader 11 that you supersede reader 10 with reader 11. I think this would be the best course.
Now, let's assume that we don't have a SCUP package for Adobe Reader updates and we cannot use SCUP as an answer.
So, our deployment of 11.0.4 has completed to all systems (As a script deployment) and 10 is no longer out there. Now, Adobe Reader 11.0.7 has been released as an MSP patch update to 11.0.4. In this scenario, I am not sure if I should revision the install script to patch to 11.0.7 and update the detection method to 11.0.7 or supersede the install with a scripted install that installs 11.0.7.
Assume that my Script install can detect that 11.0.4 is already installed before patching to 11.0.7 and that my script install can also remove older version of Reader 9 & 10 as well.
What would be the thoughts from everyone? What works best for you?