A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Instead of just creating a new app and deleting the old one, please add support for using intune app supersedence in addition to the options to remove previous apps.
Supersedence relationships can be created when adding or modifying a Win32 app within Intune. The Supersedence steps allow you to specify any supersedence relationships related to the Win32 app.
Marking this as will not implement. As far as we know right now, there are no real world scenarios that would get resolved that aren't already solved with update-only apps. Happy to revisit this when that changes.
We often deploy a base install of an app, along with the update applications. Some applications (example, Adobe Reader) are deployed to all of our deviecs. We also roll out the updates over a period of about a month.
Due to this, we leave two PMPC update applications assigned to all devices (in waves, over various dates).
Depending on the update release cadense, it's possible for a device to be in scope of both PMPC update applications. Common examples are new devices, or devices that have been offline for an extended period of time.
Because there isn't a supersedence relationship, the order of the two PMPC update applications is random - sometimes it installs the latest update first (and then detects the previous update as already installed), but sometimes it installs the previous update, and then the latest update.
This second scenario is not desireable as it can cause delays with device provisioning, or block other apps from installing.
Part of the appeal for making apps as AVAILABLE is that it gives user choice between installing the app or not, or uninstalling the app when they dont need it anymore - all via Company Portal. With the way PMPC handles updates it makes an Update as required and therefore a user can not the uninstall an updated app. This is a big issue. Would using Supersedence resolve this?
Sad to hear that, Yes we did change our update strategy because you did not support this, but it will be a part of our talks if Bestseller should renew our license
Marking this as will not implement. As far as we know right now, there are no real world scenarios that would get resolved that aren't already solved with update-only apps. Happy to revisit this when that changes.
On the contrary for us, each time that we added pre-requisites in separate superseding intune packages, we had unreliable results. In the meantime, we avoided supersede mechanics and installed pre-requisites with pre-install section of PSADT.
Maybe new tests are needed from everyone and a couple use cases could be planned?
We use it for our apps that is not from pmpc and it works great
When we first looked at this it lacked the ability to automatically update apps deployed as available. That made it feel like a non-starter for us. That functionality was added to Intune in 2024 but our initial experiences with it were poor.
So I ask those here, is auto-update superdense in Intune ready for prime-time use? Is it as reliable as our Update Only deployments?
+3 for this!
+3 for this!
Though I think that it needs to be considered how PMPC implements the supersedence for each scenario. Perhaps give the user via PMPC cloud/desktop to pick alternatives to the default behaviour.
Such scenarios I can think of include:
Pick for each update/app whether it's an update/replace.
PMPC UPDATES supersede PMPC APPS when the UPDATE is determined to be required.
The next UPDATE that gets published should supersede the old UPDATE. With the chosen supersede type.
+1 in conjunction with the new auto-update available app supersedence option:
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4076
Hey is it possible to have a look at this - supersedence is supported natively within intune
Would really appreciate Intune App Supercedence. We have tested and validated that Autopilot will only install the latest version of the Application that has supercedence applied and both applications are targeted at the same AAD Group
Fantastic Idea!
This is a excellent idea and a nice feature.