Source
r/SCCM•
Boxofoldcables

Can't get supersedence to work for me

In Config Manager, I set up Supersedence rules between three versions of an app and I checked the "Uninstall" checkbox in both rules. This is necessary because the software is dumb and will not upgrade itself when running the installer for a newer version.

Then I also check the box to [X] "Allow users to see deployments for this application and all applications that it supersedes in Software Center." This is necessary because I want both version 2 and version 3 to be available in Software Center as a possible upgrade from version 1. Not everyone wants version 3 yet. However version 2 is getting dropped from the app list in Software Center, so only version 3 is listed. After careful reading of the documentation page on supersedence I finally noticed the caveat "This option is only for available deployments to user collections."

Unfortunately choosing which PCs to deploy the two app upgrade versions to requires using a device inventory collection. Because that's the only way to locate PCs that have version 1 or 2 installed. User collection can't work in this scenario.

So I want to know why is this supersedence option limited to only user collections? Is there a way to make supersedence work here, or am I stuck dropping the use of supersedence functionality altogether and use scripts instead to handle uninstalling the old version(s)?

​

Addendum: What is the purpose of the "Active" column in the Supersedence tab of an application in Config Manager? Because I don't see a way to make a supersedence rule inactive, short of deleting it entirely. The documentation doesn't even mention it. https://docs.microsoft.com/en-us/mem/configmgr/apps/deploy-use/revise-and-supersede-applications

Posted Feb 13, 2022, 5:42 AM UTC · edited

06
Zenmaster28•

Why do you need to know which PCs have version 1 or 2 installed and only limit installs to those if you are doing an uninstall prior to installing version 3?

3
bdam55Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com)•

>So I want to know why is this supersedence option limited to only user collections

Because user policy is the newer of the two, was implemented a different way, and lent itself to this kind of feature where-as for device policy it would be a much larger lift.

So I'm with u/Zenmaster28: why do you care if the device has v1? Figure out what users need the app and deploy it to them. If v1 exists it will be uninstalled. If it doesn't, it won't.

2
BoxofoldcablesOP•

Because it's an optional upgrade. Users who have the software installed might not want to upgrade it yet. Their project files are tied to the version of the software.

But if they do decide to upgrade, the older/existing version must be uninstalled first which is why I look to the supersedence function. If not for the uninstall ability I would not bother with supersedence in this case.

1
bdam55Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com)•

Well, if you're deploying two versions you must already be deploying them as available. You deploy as available to users, they pick what version they want, and if that means uninstalling v1 then it will do so.

4
pwetter•

Another option, forget about superseding apps all together and put version 3 in a wrapper like PSADT. Then as part of the pre install steps, you can remove version 1 and 2. I’ve never been a fan of superseding apps in CM. Much prefer PSADT to take care of these sorts of cleaning tasks, when needed.

2
paragraph_api•

Just deploy version 2 and 3 as available and have it remove version 1 before installing, you’re making this harder than it has to be, you could have set this up already and moved onto other things because you do have other work besides beating this dead horse right?

1