SCCM upgrading software packages

[vfong1982]

Hi,

 

This has been boggling me for a while (naturally, because I tend to learn things on the job). I haven't found any clear-cut guides on how to upgrade application packages on SCCM 2012 using the supercedence features. At the moment, software is being deployed via Device Collection, and whenever I want to update it to the latest version, I run an Uninstall deployment to it, wait for it to finish and then create a new software deployment with the latest version.

 

Last time I tried it, it didn't work so well ...

 

An example of a piece of software I tried to upgrade at the time was Schoolcomms when they upgraded to 9.5A. It comes as an MSI installer.

[DavR]

I never got my heard round that either, the Uninstall deployment thing is crap for doing an upgrade.

 

Probably not the official recommended method, but in these sort of cases I write a batch file that uninstalls previous and installs the latest, and deploy that as my package.

[KibosJ]

If you create the new application, you can just set it to supersede the old one with an "uninstall action" or leaving it default will just upgrade (if this is possible), then deploy it to the collection and the upgrade will happen automatically.

 

I think this is what you are meaning, sorry if not.

[Geoff]

I use supercedence here, so for example I have Adobe Flash doing this. I have a custom PSADT script that handles the install / uninstall process for me so I do not need to tick the 'uninstall' option. It will just install over the top of the old version. If you did have something (say an MSI installer) that had to be removed before you could put the new one on, you would tick the box.

 

One gotcha that might trip you up is that clients will immediately jump on the new version once it's been distributed rather than paying any attention to what your deployments say.

[KibosJ]

One gotcha that might trip you up is that clients will immediately jump on the new version once it's been distributed rather than paying any attention to what your deployments say.

 

Yeah, I've been tripped up by this once before!

[free780]

Yeah, I've been tripped up by this once before!

They shouldn't do. They may if you installed the application from a TS which still deployed to the PC.

[Tefters]

They shouldn't do. They may if you installed the application from a TS which still deployed to the PC.

 

Second this... ^^^

[free780]

I actually prefer no to have applications in TS for this reason. But trying to get SCCM to push them out during TS or just after requires patience.

[Geoff]

They shouldn't do. They may if you installed the application from a TS which still deployed to the PC.

 

It entirely depends on if you remember to go back into the application deployment after setting it up and unticking the box that wasn't there before. But you can only do that if you set things up in the right order (create new app, deploy, alter hidden tick boxes, create supersendence rule).

 

https://foxdeploy.com/2016/01/21/sccm-controlling-application-supersedence/

 

Here is the uservoice entry if you want it fixed.

 

https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/11532669-fix-supercedence-behavior

Edited September 30, 2017 by Geoff

[vyperz]

you don't have the 9.5a msi file do you? - i accidentally deleted it .. needed for upgrade to 9.6 !