Create an application and add a dependency to it like .net framework 1.1 (Call it App A version 1.0) Deploy it available to all users Get the new version of the App. (Call it App A Version 2) Deploy the new version to all users optional and select to upgrade previous versions Delete the deployment for version 1.0 create a simulated deployment to all systems for App A version 1.0
*App A Version 2.0 installs on all machines in the environment* Delete all the deployments Remove the dependency on App A version 1.0 to .net 1.1 Deploy App A 2.0 to all users optional and select to upgrade previous versions create a simulated deployment to all systems for App A version 1.0 *SCCM discovers all old versions and upgrades them exactly as it should* Since the supersedance rule ONLY affects the app itself and not the dependent apps there is no reason to have a dependency on the superseded app. If you are going to supersede and app be 100% sure you remove the dependencies on it first. The client cannot tell the difference between the app being installed and the dependency being installed /Todd
