Re: How to safely decline the already approved updates in WSUS 3.0
> Thanks for your post.I should I have been more elaborative on this. Yes I do
> know about how to decline the patches but my problem is I am having number of
> patches with database of upstream server touching >100 GB.
I assume you mean the content store rather than the actual database?
> I have declined
> superseded and expired updates but there are thousands of other updates that
> are unusable to my environment like SQL, Windows server 2008 64 bit etc. I
> used to approve all the patches that comes under my selected classification
> but now I wanted to decline them and finally purge them from database.
For the record, I don't usually recommend declining updates, although I believe
I'm in the minority here. The reason is that if an update is declined, you
won't get any warning if it turns out it was actually still needed after all.
(This may not apply if you're using a separate tool to check compliance.) One
option in your situation would be to decline the unwanted updates, then set them
all back to "unapproved" once you've purged the content.
To answer your question:
Probably the best approach would be to decline the updates by hand. I think
you'll find that if you set "Group By" to Classification (from the Action menu)
and then sort by title that most of the updates you'll want to decline are
clustered together, and it won't take nearly as long as you might think.
Theoretically you could write code to sort it for you, but it would almost
certainly be faster to do it yourself.