Shavlik Patch 2.1 for SCCM 2012 2.1 has added some features around handling patch revisions and supersedence. Specifically, patch revisions for patches you have already published to make it easier to accept these revisions. On 11/12/2014 we will begin including supersedence information with our Shavlik Patch for SCCM 2012 patch content. By including supersedence content customer will more easily see which patches they need to apply to be up to date. Customers will not need to keep track of supersedence themselves and have a separate process for expiring old patches.
Shavlik Patch 2.1 includes new a filter in that can be used to filter out patches that have been superseded so customers can easily identify the latest patches. We have also added information about the details of supersedence in new columns and the new details view so customers have visibility into the supersedence content.
There are some important things to understand regarding supersedence and SCCM 2012. When a patch is published that supersedes an older patch the publishing process triggers an expiration process of the older superseded patch. How that older patch is expired is controlled by settings in the Software Update Point (SUP). Below is a screenshot of the supersedence tab in the SUP that shows your options.
You have the option of triggering the expiration immediately or dealing it by a specified number of months. When an update is expired it will not be evaluated and installed on client machines.
Shavlik Patch 2.1 for Microsoft System Center (SCUPdates)