Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

How to safely decline the already approved updates in WSUS 3.0

microsoft.public.windowsupdate






Speedup My PC
Reply
  #1 (permalink)  
Old 09-10-2008
ikafridi
 

Posts: n/a
How to safely decline the already approved updates in WSUS 3.0
Hello Everyone,
I have couple of updates that I have already approved manually initially for
couple of different classifications like SQL etc. Now the database size has
grown enormous and I wanted to devise a mechanism for declining those
approved but unused updates . Although superseded and expired updates are
taken care of but the updates not within these two categories are still lying
there. Also I need to make sure that these updates do not turn around again
once I decline and purge them.

Any pointers would be much appreciated.
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 09-10-2008
TaurArian
 

Posts: n/a
Re: How to safely decline the already approved updates in WSUS 3.0
"ikafridi" <ikafridi@discussions.microsoft.com> wrote in message
news:B5EED5FB-570A-4F9B-B44E-EC8A0A5A313A@microsoft.com...
> Hello Everyone,
> I have couple of updates that I have already approved manually initially
> for
> couple of different classifications like SQL etc. Now the database size
> has
> grown enormous and I wanted to devise a mechanism for declining those
> approved but unused updates . Although superseded and expired updates are
> taken care of but the updates not within these two categories are still
> lying
> there. Also I need to make sure that these updates do not turn around
> again
> once I decline and purge them.
>
> Any pointers would be much appreciated.


Perhaps try the WSUS Newsgroup (xposted for convenience)

On the web:
http://www.microsoft.com/communities... date_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services


Reply With Quote
  #3 (permalink)  
Old 09-10-2008
Harry Johnston [MVP]
 

Posts: n/a
Re: How to safely decline the already approved updates in WSUS 3.0
[TaurArian cross-posted to .update_services]

> "ikafridi" <ikafridi@discussions.microsoft.com> wrote:


>> Hello Everyone,
>> I have couple of updates that I have already approved manually initially
>> for
>> couple of different classifications like SQL etc. Now the database size
>> has
>> grown enormous and I wanted to devise a mechanism for declining those
>> approved but unused updates.


I'm not sure I understand the problem. You know how to decline an update?
Select one or more updates, right-click and choose Decline.

>> Also I need to make sure that these updates do not turn around
>> again once I decline and purge them.


I'm not aware of any circumstances in which a declined update will spontaneously
re-approve itself.

Be cautious about what you decline, as declined updates will not be detected as
needed even if they are.

Harry.
Reply With Quote
  #4 (permalink)  
Old 09-11-2008
ikafridi
 

Posts: n/a
Re: How to safely decline the already approved updates in WSUS 3.0
Hi Harry,

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 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.

Thanks,
Imran

"Harry Johnston [MVP]" wrote:

> [TaurArian cross-posted to .update_services]
>
> > "ikafridi" <ikafridi@discussions.microsoft.com> wrote:

>
> >> Hello Everyone,
> >> I have couple of updates that I have already approved manually initially
> >> for
> >> couple of different classifications like SQL etc. Now the database size
> >> has
> >> grown enormous and I wanted to devise a mechanism for declining those
> >> approved but unused updates.

>
> I'm not sure I understand the problem. You know how to decline an update?
> Select one or more updates, right-click and choose Decline.
>
> >> Also I need to make sure that these updates do not turn around
> >> again once I decline and purge them.

>
> I'm not aware of any circumstances in which a declined update will spontaneously
> re-approve itself.
>
> Be cautious about what you decline, as declined updates will not be detected as
> needed even if they are.
>
> Harry.
>

Reply With Quote
  #5 (permalink)  
Old 09-12-2008
Harry Johnston [MVP]
 

Posts: n/a
Re: How to safely decline the already approved updates in WSUS 3.0
ikafridi wrote:

> 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.

Harry.
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
WSUS updates Doubled D microsoft.public.windowsupdate 2 07-29-2008 04:56
Scheduling Updates with WSUS... KM microsoft.public.windowsupdate 2 07-26-2008 13:46
WSUS doesn't sync all updates Carsten microsoft.public.windowsupdate 5 05-05-2008 07:40
WSUS Client Failed to detect Approved Updates SAFairfax microsoft.public.windowsupdate 17 12-20-2007 01:59
Error Code: 0x80244019 on approved updates Jerry microsoft.public.windowsupdate 1 12-12-2007 20:15




All times are GMT +1. The time now is 00:10.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120