Wsus - WsusContent size

[aarono]

Hi,

 

I have just had to increase the hard disk size of our wsus server to 90GB as it was full due to the WsusContent folder. (Shrinking the built in sql database will have hardly any effect)

 

We download only English language, we download only when approved, we do not download express installation files.

 

We download windows 7, windows 8, windows server 2008 r2 and windows server 2012 r2.

 

How much space do others use for their wsus as I am not sure if the WsusContent should be quite as lager as 80+GB?

 

Thanks

[LeMarchand]

Ours is currently 101GB - and I ran the cleanup wizard a month or two ago which removed a fair few GB of updates that were no longer needed.

[sted]

the only way ive ever found to reduce the size significantly is to uninstall wsus and hope it will reinstall on the same server again (it wont always) as server cleanup wizzard dosent seem that good

[LeMarchand]

as server cleanup wizzard dosent seem that good

 

Too busy wishing it could be Christmas every day.

 

[3s-gtech]

We have Server 2008 in the mix too, currently 148GB. Little bit of expansion left on the host, but not much. Retiring 2008 will help, but I'm in no real rush as it has years left in it and makes a rather good print server.

[minimoo]

we download products we run + win7, 8.1, 2008R", 2012R2, and download all classifications apart from drivers + hotfix currently and the wsus content folder is sitting at 50GB currently.

 

However, I think the point here is thinking about what wsus cleans up - i've recently gone for the approach or running a cleanup for everything but *not* removing computers not contacting the server, and then looking at the PC's that never "check in" and fixing windows updates on them / getting them out the cupboard and turning them on etc for the oldest ones on a 'rolling program'

 

wsus will delete the content files that take space for updates that are expired, or aren't needed by computers for 30 days or more and if they are superseded.

 

My rational for not clearing the computers contacting the server automatically - is if a pc isn't used for 50 days, it'll get cleaned up out of wsus, but when it comes back in, the updates that got cleaned up will suddenly become needed. Therefore, i've gone for running a script that does a SQL query if a PC isn't seen for 90 days - and then I go and find PC and turn it on, or if it's something i've just forgotton to delete from the AD/WSUS, clear the record out manually. If you are not changing computer names on re-install, manually deleting the 30 pc's that get scrapped each year isn't too much work, and dealing with the PC's that aren't getting used doesn't take long as most pc's are used, and is one method of identifying if there's stock within the school that can be better utilized.