WSUS is 130GB

I have recently started to manage the IT for a company which has a SBS 2008, they use WSUS, the WSUS is 130GB, as i have not set this server up, my guess is that it has been setup to collect all updates for most products and languages, the director said that the previous IT guy had removed languages recently before leaving. i have ran the cleanup wizard and it removes 100mb of updates, is 130GB really needed;

1x SBS 2008
11x windows 7 pro
1x windows ultimate  

Any advice is welcomed
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

*** Hopeleonie ***IT ManagerCommented:
And no Office updates?

For me I think 130 GB is fine as WSUS will grow :-)
David AtkinTechnical DirectorCommented:
Did you run all of the options on the WSUS Cleanup?  I would expect it to remove far more than 100MB.

Re-run the cleanup one option at a time.  I tend to run the cleanups from the bottom to the top as the top option seems to take forever to complete.
Seth SimmonsSr. Systems AdministratorCommented:
130gb is definitely excessive if you don't have a lot of products and classifications; your OS selection should only be windows 7 and 2008
i would select those updates in the other languages and decline; may not go through cleanup wizard until that step is done first

and go through other updates and decline any that are superseded
i recently wrote an article about building a wsus environment and there is a section on managing updates that will help determine superseded updates that you can sort and decline which should allow the cleanup wizard to delete more

Installing, Configuring, and Managing WSUS
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

DonNetwork AdministratorCommented:
For me it is by far much easier to start from clean content folder especially when you are taking over from another. Follow the advice here on how to use wsusutil.exe

I would also make sure that only updates that are "Needed" are Approved

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jungle_JonAuthor Commented:
Update, I'm back at work (UK time zone), went throught and double checked what product i had selected, changed it to office 2010, win 7 and SBS 2008. Now currently going through and running the cleaner with one option at time. If that fails then i will do what dstewartjr says and clean out the WSUS folder.

Thank you for the advice / help so far.

EDIT: Now 120 GB, going to do what dstewartjr said. The Internet here is two cans and a bit of string will leaving it runnnig over the weekend when i leave tonight.
Mike TLeading EngineerCommented:
Hi JJon,

For just W7 x 2 with SBS 130GB is definitely over the top. I setup WSUS last year for W7 only and it was 60GB. Factoring in another 12 months is maybe 30GB more.
I agree with the advice given - it's often easier to scrap it and start again than spend time trying to fix it. You won't get any nasty surprises either.

However, I would budget for 250GB of space on the grounds that patches only ever grow. I'd rather get enough space for a few years now than try and skimp and then mess about trying to move the content to another disk.
Recently I've seen servers built with 32GB disks and "surprise" they ran out of space.

Just a thought.

Jungle_JonAuthor Commented:
Ran the reset over the weekend and the WSUS is 62GB, seems normal, will monitor over the week. Solution given to dstewartjr, thanks everyone for helping.
Jungle_JonAuthor Commented:
Thank You, over halved the size of the WSUS content folder.
Jungle_JonAuthor Commented:
UPDATE: The WSUS has now ballooned to over 160GB, im going to remove the role and re-add it.
DonNetwork AdministratorCommented:
"The WSUS has now ballooned to over 160GB"

Then you most likely have too many products and classifications selected and/or languages. Do you have express installation files enabled ?

"You can use express installation files to limit the bandwidth that is consumed on the local network. However, this is at the costs of additional bandwidth on the Internet connection and additional local disk space. By default, WSUS does not use express installation files."
DonNetwork AdministratorCommented:
From your original question "setup to collect all updates for most products and languages"

why more than 1 language ?
DonNetwork AdministratorCommented:
I would go back and delete the content again then only select the products/classifications/languages you need and do a reset again.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.