Once the updates are published to the WSUS server, they can be treated just as any Microsoft update would be. To expire them, you would simply browse down to the updates in question under Update Services -> [WSUS Server Name] -> All Updates (or Third Party Updates if you have that view defined). Next you would select the update(s) in question, right-click, and select Expire.
Hmm, i did that and is not showing up as expired when i go to configmgr console to look at software updates. Expire=NO.
I noticed the task to expire patch failed in Eminentware.
Expire Update Package
Object: Java Runtime Environment 6u26 (x86 for x64) (Upgrade)
Details: Expire update package Java Runtime Environment 6u26 (x86 for x64) (Upgrade) failed. Value cannot be null.
Parameter name: path2
Ah, we did not realize you were discussing a Configuration Manager environment as you only initially mentioned WSUS.
In a ConfigMgr environment, you don't want to modify update content from the "WSUS Console" in that way.
If 6u27, 6u29, or 6u30 lists 6u26 as a superseded update, the update will be automatically expired by Configuration Manager when the superseding update (6u27, 6u29, 6u30) is published to the SUP.
For Sun patches that i published with Meta data only but want to get rid of it now so there is no way but to wait till it gets superseded? I notice that if you published Meta data only patches SCCM keep scanning patch as not required. Only patches with published in FULL will get scan properly. Is that true? thanks.