It's kind of expensive, but I solved my disk space problem by using acronis
disk director:

http://freecomputerconsultant.com/bl...irector-fixes/

it did work slick, just as written about. I had plenty of space on D: but
thought (some years ago) that 12GB was big enough for C:

"Gary Drost" <GaryDrost> wrote in message
news:0ef9
[..]

Thanks for the info, seems pretty complicated and time consuming
unfortunately.

Why on earth, then, did WSUS recommend WSUS 3.0 SP1 for my R2 server with
WSUS 2?

thanks.

"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer> wrote in
message news:4180
[..]

The instructions for upgrading 2 to 3 include backing up the database. Do I
have to? Why do I care, won't it just find the clients (all 5 of them),
reanalzye them and download what's needed?

thanks.

"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer> wrote in
message news:4180
[..]

I never have..
I just toast it and install it.
Unless you pay for Download Data
(Which We don't in the USA)
I can't see any use keeping it myself?

Russ

Good question...
I guess MS Assumes everyone should upgrade to WSUS SP1
(Which if you have WSUS 3.0 You may see errors in logs and SP1 is needed
anyway.)

I know others here Love R2 version but I prefer WSUS 3.0 SP1
It gives better control IMO

Russ :)

Got to point out that there are other ways to re allocate disk space but
until Server 2008 none are officially supported by MS.

Further, a 12 GB partition can be managed. And a 25/30/50 GB partition
still has to be managed, it will just longer before you have to do it, but
there will be more to do.

If you allow WSUS and Exchange and User Folders, etc all to live on the
system partition you will still have issues. If you allow WSUS to live on
the system partition, just repartitioning your drives may only solve the
space problem for a few months or a year or so, and then you will be re
visiting this.

Put all the stuff that grows on the data partition. Add drives if you fill
it up and move stuff again. But to allow the system partition to run with
less than 20% free space will drag down performance, and the more free space
the better.

Then depending on your version of SBS and related programs, keep the
mailboxes cleaned out, run the cleanups for WSUS, watch the space consumed
by windows update uninstall folders, delete (or compress if you must) old
log files (Windows\System32\Log Files), make sure you get "exchange aware"
backups, institute disk quotas, run FSRM and prohibit music, photo and
movies, check that your AV deletes its downloaded updates and patterns after
a few days, and watch the temp files and temporary internet files for
abnormal use.

There is more... you can search for a list from me for clearing space on the
system partition, or, if requested I will post it again.

-Larry


"R" <none> wrote in message
news:5920
[..]

I pretty much have everything cleaned out that grows - EXCEPT!- Windows
updates (and after a few months I delete the compressed backup directory,
but I wait a couple months!) - that's what broke the camel's back recently
for me. And WSUS 3.0 SP1 wouldn't even install originally (I should have
just skipped it) because of inadequate C: space. This is even though I had
previously installed WSUS on a different drive. Go figure.

That's another confusing point about Microsoft installations; they make it
less than obvious how to put things that grow elsewhere.
Such as:
InetPub
SQLData
even Exchange; in Exchange 2007, you HAVE to install to C: and then move
later (unless I'm missing something).

What's wrong with these guys? Is it that hard to segregate on the install
with an option to change directories?

thanks,
Roger.

"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer> wrote in
message news:3492
[..]

You should have everything you need to shrink/move the WSUS program/data
file now. If all else fails you can remove the entire R2 set and put it
back, specifying the drive with the most space.

-Larry

"R" <none> wrote in message
news:1164
[..]

Larry:

I was never able to get the "mowing the grass" part to finish. I ran it
several times, the first time it ran for several hours before erroring out,
subsequent runs much shorter, maybe to the tune of a couple minutes.

When I ran the WSUSDebugTool (it was a bugger to find) it cleared out nearly
12GB of space.

Now I will need to consider installing WSUS 3.0 SP1 or figuring out how to
just move the files associated with WSUS 2 from C: to D:

Gary

"Gary Drost" wrote:
[..]

yes, mowing was probably failing due to the lack of space and low
performance this causes.

Can you now get into the WSUS console?

"Gary Drost" <GaryDrost> wrote in message
news:699f
[..]