This feels like a "Two Birds with one stone" scenario. Which will potentially fix issues of auto-retiring apps with deployments that have "Available with forced upgrades". While also leaving a single "known good" version of apps on our server in case there is an issue with the current release and all old apps were cleaned up.
As you may know, you cannot have "available with forced upgrades" enabled in Recast while also auto retiring apps.
Why does recast do this? Well, I believe its because of how SCCM handles supercedence. It is helpful to keep the app in SCCM's repository so it can reference which computers have the old version of the app, and it knows which devices to install the new version of the app on it.
How would this resolve it? Well, by allowing one version of the superceded app on the PC, as long as devices are properly being patched, it would allow SCCM to maintain sight on that single version for long enough to install the new version.
"Long enough?" What if an app releases 2 versions within a few days of each other. It will hose all of the apps that didnt have time to update, and not update those apps. - TRUE, however, that is why I also suggest that we set a "minimum age for superceded app deletion". With a minimum age of lets say 30 days, it will give us enough buffer to ensure that newer versions of apps have been installed.
| Product | Recast Management Server |