We have experienced this as well, just in the last couple of weeks, too.
I'll vote up your feedback. From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Leuthold Sent: Monday, August 12, 2013 9:08 AM To: [email protected] Subject: [mssms] Automatically upgrade any superseded versions of this application grayed out for device collection deployments May be old news for some but I didn't see any DCR/bugs filed on Microsoft Connect for this issue since beta so I wanted to bring this up and post feedback on Connect... https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/796 927/automatically-upgrade-any-superseded-versions-of-this-application-grayed -out-for-device-collection-deployments We use ConfigMgr to manage our server environment. We ran into an issue where we were trying to supercede an application and test the deployment however we cannot remove the "Automatically upgrade any superseded versions of this application" option during deployment. We are targeting servers (devices) and not users. We want to test and manage the app upgrade without it being forced and still be able to take full advantage of the app model. The only work-around I found thus far was to create the deployment prior to adding superseded applicaiton(s) to the deployed application. I'm assuming we should be able to create a deployment using PS/SDK without forcing superseded applications to be upgraded as another workaround but haven't tried it yet. -Stephen
smime.p7s
Description: S/MIME cryptographic signature
