SCCM-Removing a Superseded Package Locally From a Machine?
Posted on 2014-01-22
We are currently running SCCM 2012 in our environment and are running into an issue where certain machines continue to try to install superseded packages. Typically it goes something like this....
Application V1 (required app) is deployed and fails to install on the machine. Customer never reports the issue so it keeps retrying every so often but they otherwise ignore it.
Application V2 comes along and Application V2 is marked as superseded but not deleted. It's required so any machine with V1 will get upgraded to V2. V2 installs successfully on this same machine where V1 failed to install previously.
One problem however, even though V1 is superseded it will keep trying to install and failing until the end of time or until the package is removed from the server.
Currently the only fix I have for this would be to uninstall V2, fix the problem that is preventing V1 from installing. Allow V1 to have a successful install, then reinstall V2.
I spoke to one of my system architecture contacts today and was told that they suspect it's a bug and don't really have any answers right now besides what I'm currently doing or to reinstall the SCCM endpoint. They seem to think this and several other problems will be resolved by SP1, however it has not been approved in our environment yet.
It seems like there should be some way to "remove" the superseded package at the workstation end, but neither I or they have any idea how this could be accomplished. Any ideas on a less messy work around in the mean time?