Trying to upgrade Zoom app using Supersedence Application management in Configuration Manager lets you upgrade or replace existing applications by using a supersedence relationship
Superseding multiple previous versions I have setup supersedence for an application It is set to supersede 9 previous versions of the application Not all previous versions were deployed via CM so I created dummy apps with the detection method and the uninstall command To the new version I added each of those dummy apps to the supersedence tab and selected for uninstall
How to downgrade or rollback in application model Therefore, i need to uninstall ApplicationA-v2 0 from clients and install ApplicationA-v1 0 automatically As my understanding supersedence is use to upgrade application version or replace an existing application, but not sure is that best practice to use this method to downgrade the application version?
Handling reboot with supercedence I've got it working on a supersedence situation where application v1 and v2 both needed reboot after installation uninstallation Proposed as answer byJoyce LWednesday, April 8, 2015 6:24 AM
Increasing Priority for Supersedence in SCCM There is no way to increase the priority for supersedence and it just follow the order that you add the apps into supersedece May be you can put uservoice for this request?
List of devices with application (NumberOfDevicesWithApp expanded) to be a great help when trying to find where we have not moved devices over to new app version but this is just a int value so we are unable to make use of this to either remove the app from the devices or add them to deployment of new version as we cannot get the names or anything else to identify what devices have the app installed
KB2690729 - Superseded or not? - social. technet. microsoft. com The WSUS console doesn't give you any control over which icon appears for a particular update in the Supersedence column There may be a way to connect to the database to tweak the metadata to correct value it but it's probably safer to hope that a synchronization will set the correct metadata for the update after Microsoft fixes the problem
How to work with dependencies that superseed Supersedence is technically working for dependencies, just not automatically In the article you quoted I believe Stan White and Ronni Pedersen explain why the dependency must be changed It is because a superseding application is a new application The old must be replaced with the new Could Microsoft have automated the process? Most likely, but it does not appear to work that way in
Update problem 80244019 using WSUS - social. technet. microsoft. com I have a problem with windows updates All of the computers in the domain are set up to download the updates form our local server It was working fine, and suddenly stopped Now when you try to update your machine you get 80244019 error, but if you download the updates straight from Microsoft website, it is working fine Any ideas how to trouble shoot that problem?