Search the Community

Is it possible to set a deployment to superseded another deployment and it automatically installs for all those users which have it installed, but remains "available" for those that haven't. Take for instance a Java install. I create a Java application with v8.35. I set it as Available and deploy to the Staff collection. Users who require Java can install it and the rest do not. A new version is released. I create a new application Java v8.45. I set it to superseded v8.35 and deploy as 'Available' again to the Staff collection. I retire v8.35 at the same time. How can I make the deployment update all those users who manually chose to install v8.35, but not force a collection wide "required" rollout of java. Thanks in advance. I think I know the answer in that SCCM doesn't handle third party software updates like this, but it seems like a pretty straightforward and basic feature that would benefit many.

Hi folks, Here's another one that got us today that's worth keeping in mind. If you have an Application which has, let's say, two Deployment Types, the first (priority 1) is configured to auto-install the second (as specified in the Dependancies tab). If you then make this application Available (i.e. not even Required) to a device, as expected it will appear as Available within Software Centre and do nothing until you hit Install... UNLESS the machine happens to meet the requirements of the Detection Method of the first Deployment Type in which case it will AUTOMATICALLY INSTALL THE SECOND DEPLOYMENT TYPE WITHOUT WARNING :angry: This will happend regardless of whether the application is deployed via Task Sequence or on its own. If you're in the habit of using Available deployments as we are, best make sure your Detection Methods in all Deployment Types are unique. I'd say this is similar to the issue that bit us earlier around supercedence causing Available applications to auto-uninstall superceded packages without warning ( http://www.windows-noob.com/forums/index.php?/topic/8952-possible-bug-in-sp1-cu1-client-applications-that-supersede-others-may-rollout-unexpectedly/?p=33797 ), both of which I'd call a bug rather than a feature.