Search the Community
Showing results for tags 'supersede'.
OK Guys. I was preparing for a Java update in our environment and made one application supersede all other Java applications. I did not have any active Java deployments but yet when I came in this morning, low and behold, Java had started updating across the organization! Turns out, the same Java application was in a Task Sequence which was deployed as available to a large number of machines so SCCM started updating Java on them. I read that this was sent in as a design change but did not make it into 2012 R2. My question is how do you deploy available task sequences and what is best practice? We are not currently utilizing unattended PC builds so I don't deploy any Required Task Sequences. I have thought about deleting all my deployments and then just deploying to specific collections and have the technician add whichever PC they wanted to image to said collection beforehand. This just seems counter intuitive. Any thoughts? Anyone been burned by this before? SCCM 2012 R2
Folks, You'll like this. We were wondering why two packages recently uninstalled themselves from all our PCs without any warning. Eeak! It took a bit of digging but we discovered that currently (SP1 CU1), when you “supersede” an application with another, if the superseding (i.e. newer) application is then added to a Task Sequence and this Task Sequence is then made “Available” to a PC that has the superseded application installed, the client will automatically try and perform the upgrade shortly afterwards! Because our application happened to require a reboot before the newer version would installed, the first sign we got that something was wrong was when our users started reporting that the application had disapeard. Oh what fun! Here’s what we did to replicate the problem: a) Created application A and installed this on a PC. Created application B and specified that this supersede application A (ticking the Uninstall option in the Supersede tab). c) Created a new Task Sequence that includes only application B and made this Available to the PC. d) The client will uninstall application A and install package B shortly afterwards. The CCM client log AppIntentEval.log finally gave us the tip-off as it not only goes to the trouble of listing all applications within an available Task Sequence with each policy refresh, but it also reports the supersede uninstall/install. I can’t find any documentation that warns that making an application Available via a Task Sequence (or even via a direct deployment but I haven’t tested that far) might trigger the automatic upgrade of any superseded applications, but I can't see how this should be default behaviour. I've raised an incident with MS so let's see what they say... Dave