none
Is this correct re: cleanup?

    Question

  • In another thread it was stated regarding cleaning-out unneeded updates:

    [QUOTE]First they have to be declined. Second, if they were never approved, those aren't the updates causing your headache, because never-approved updates have no content files. Rather you need to focus on the updates that are NOT declined that should be declined.

    1. Go to the All Updates view.
    2. Filter on Any Except Declined.
    3. Enable the Supersedence column.
    4. Sort by the Installed/NotApplicable column.
    5. For any update that is reported as Installed/NotApplicable=100% and is superseded -- DECLINE it!

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com[/QUOTE]

    I'd like to implement this not only to free space on my WSUS server but also to simplify things. To make sure I understand:

    1. In the Supersedence column the ones I leave alone are the "supercedes other updates" and the "blanks", and the ones to Decline are the remaining two categories, "is superceded" and "is superceded and supercedes others". Correct?

    2. When I Decline these, any downloaded files will be removed from the server at the next Cleanup?

    I want to confirm that this is a very safe procedure, i.e. they're already dealt with (100% Installed/Not Applicable) and any Computers I might add in the future would use the superceding updates still on the server.

    Saturday, August 24, 2013 2:27 PM

Answers

  • Hi Maxblack,

    Lawrence has an article with a bit more details about this process here: http://thwack.solarwinds.com/community/application-and-server_tht/patchzone/blog/2013/01/21/wsus-timeout-errors--removing-unneeded-update-approvals

    Regarding the cleanup, I'd assume so but I haven't really paid close attention to the server cleanup wizard for a while so I can't be 100% sure. Hopefully someone (Lawrence) could confirm that ;)

    I hope this helps,
    Mark.

    Saturday, August 24, 2013 6:00 PM
  • I have not tried your script (yet), preferring to reduce my variables (I have never attempted this before!) and after following the process above: the Server Cleanup ran overnight, but it changed the WSUS folder not one iota. It turns-out that I need to manually run the WSUS Cleanup Wizard for this, and despite some surfing that suggested this could take hours, it completed in only a few seconds. On my setup I observed the following:

    1. The "Decline Superseded Updates" process above yielded 1012 useless updates to Decline

    2. Before running the WSUS Cleanup Wizard my WSUS folder contained 1.671 Files consuming over 9GB of disk space

    3. Following the WSUS Cleanup my WSUS folder contains 798 Files consuming about 5GB of disk space

    I did make an image backup of my installation before attempting the above, but it appears that all has gone very smoothly indeed (knocking on wood). Thanks for your input Mark and I hope this thread helps someone else some time.



    Sunday, August 25, 2013 3:39 PM

All replies

  • Hi Maxblack,

    Lawrence has an article with a bit more details about this process here: http://thwack.solarwinds.com/community/application-and-server_tht/patchzone/blog/2013/01/21/wsus-timeout-errors--removing-unneeded-update-approvals

    Regarding the cleanup, I'd assume so but I haven't really paid close attention to the server cleanup wizard for a while so I can't be 100% sure. Hopefully someone (Lawrence) could confirm that ;)

    I hope this helps,
    Mark.

    Saturday, August 24, 2013 6:00 PM
  • It does help Mark, thanks for the link--I'd thought I read all of Lawrence's blog entries but did miss that one. Clearly I'm a candidate as I have several thousand approved updates ("a well-maintained WSUS server will rarely have more than a few hundred approved updates") so I'm on it.

    I needed too to understand the supercedence icons but I found that by searching.

    I'm gonna go for it...I think Sat. nite is even the night for auto-cleanup, so should see whether the declined files get wiped-away.

    Saturday, August 24, 2013 7:04 PM
  • That "well-maintained" sentence threw me a bit as well but I guess it must be relative to how many OSes and Microsoft products you have in your environment.

    It's more of a proof of concept but I wrote this script after going through that article and got bored trying to decline updates supersceded by service packs that may help you: http://gallery.technet.microsoft.com/Decline-all-updates-f9de0c7d

    Mark.

    Saturday, August 24, 2013 7:37 PM
  • I have not tried your script (yet), preferring to reduce my variables (I have never attempted this before!) and after following the process above: the Server Cleanup ran overnight, but it changed the WSUS folder not one iota. It turns-out that I need to manually run the WSUS Cleanup Wizard for this, and despite some surfing that suggested this could take hours, it completed in only a few seconds. On my setup I observed the following:

    1. The "Decline Superseded Updates" process above yielded 1012 useless updates to Decline

    2. Before running the WSUS Cleanup Wizard my WSUS folder contained 1.671 Files consuming over 9GB of disk space

    3. Following the WSUS Cleanup my WSUS folder contains 798 Files consuming about 5GB of disk space

    I did make an image backup of my installation before attempting the above, but it appears that all has gone very smoothly indeed (knocking on wood). Thanks for your input Mark and I hope this thread helps someone else some time.



    Sunday, August 25, 2013 3:39 PM