Automatically upgrade any superseded versions of this application is grayed out
for device collection deployments. If you make an application deployment
available to a device collection and blow through the wizard you may not notice
this :) (I've made this mistake). The only work around I know of is to create
the deployment first and then configure the application to supersede. Another
probable work-around is to use the SDK
http://msdn.microsoft.com/en-us/library/hh949124.aspx. Not sure what flags
would have to be set.. http://msdn.microsoft.com/en-us/library/hh948575.aspx
To me this is a bug and has been filed on Microsoft Connect, they marked it as
resolved-postponed. I assume that it will be fixed in the *near* future More
info:
https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/796927/automatically-upgrade-any-superseded-versions-of-this-application-grayed-out-for-device-collection-deployments
From: [email protected]
To: [email protected]
Subject: [mssms] When creating an install and uninstall package it runs
automatically?
Date: Tue, 3 Sep 2013 14:33:51 +0000
I have done this a few times and the results are always the same.
I have created a 7-zip install Application and I created a winzip uninstall
Application. Both are set as available and both work perfectly OK when they are
separate.
But then I wanted to get fancy and have it so that it uninstalls winzip first
then installs 7-zip.
In 7-zip I have the Winzip uninstall as supersedence, where I think the issue
happens, because when I add this to a collection it instantly starts the
uninstall (almost like it becomes required), when I am hoping that a user can
choose
to kick start the uninstall/install themselves.
I assume that most CM admins do this so it takes the work away from the end
user having to have 2 tasks to complete?
Thanks,
Kevin Johnston
