Hi team, based on the patch dynamics for 3rd party applications, what do you consider is the best procedure to handle supersedence. My first thought is to expire old packages in SCCM. The way I would do it is to remove the package from PM in the update services view (effectively from the upstream SUP), and then it will show as expired in SCCM console.
Any software update groups will gather the change and will work accordingly.
Any new machines will get the newest patches only.