pembertj Posted April 21, 2015 Report post Posted April 21, 2015 I am running into a seemingly strange problem - maybe I just don't quite understand how supersedence is supposed to work - here is the scenario I am running into: 1. App v1 - Deployed to Device Collections as Required and Deployed to user collection (app catalog) as available 2. App v1 - All deployments now pulled 3. App v2 - App v2 setup to supersede v1 in the properties of the application. All deployments of v1 are now replaced with v2 of the application. Users who fall into the user collection are having v1 automatically uninstalled from their machine and v2 is installing - even though the User Collection deployment is set to Available and not Required. Also the checkbox that is listed when you deploy the application to the User collection "Automatically upgrade any superseded verions of this application" doesn't really make sense to me - isn't this what is done in the properties of the application? Currently this box is uncheck on the deployment. Thanks for your time ~pembertj Quote Share this post Link to post Share on other sites More sharing options...
