Fix Supercedence Uninstall bug
There is definitely a bug with using the Supercedence Uninstall feature that causes the old application to be removed but the new application does not install.
Scenario (confirmed this happens with a variety of applications):
- Office 2013 is a required deployment
- Office 2016 is ready to deploy, so we create a supercedence with Uninstall
- Maintenance Window is Mon-Fri 5PM-5AM, all day Sat/Sun
- Deploy Office 2016 as Required starting Friday 5PM, with a Deadline of the NEXT Friday at 5PM
- The Monday after deployment start (deadline not reached yet) Office 2013 will have uninstalled as expected, but Office 2016 will not have installed despite having 60 hours of Maintenance Window
Changing the Deadline to immediate and allowing installation outside Maintenance Window will trigger 2016 to install. HOWEVER, we have created deployments that start out set that way and still witness the same behavior.
The App logs even indicate that SCCM is aware it's supposed to install the new application, however it does not and app enforcement just stops.
This severely limits the usefulness of Supercedence because it can't be trusted to not leave users out in the cold.
This is either related or a dupe of https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/11532669-fix-supercedence-behavior