SBS 2008 Console; watch out

[greif1]

I like the SBS console, I really do, but mine does not run right! Try to add a group; crashes, try to run reports ; crashes (used to work though!).

Anyway, I thought I would warn folks to watch out for some installs like to create huge log files when the Console is running. I left it on over a weekend and found Exchange not receiving mail because the C: drive had only 400mb of space left. Cleaned up the log file and got back 11 gb of space.
Some thing to watch out for.
gr

 

[ShackDaddy]

What\where was the actual log file that you ended up deleting? Was it a single log file or multiple files?

Dave Shackelford MVP
ThirdTier.net
TrainSignal.com

 

[greif1]

The console log seems to be one file, created each day the console is open (or one big one when it is closed if open for a lot of days?)
It is located in
C:\inetpub\logs\logfiles

where there are several more folders in logfiles, some of which are reasonable size, but others are whoppers. In case of bad effects, I just copied the big logs to another partition then deleted those from my C: drive. I did not mess with the current day or previous day logs. I had no ill effects from the move.
gr

 

[happyhacker]

This is interesting. I have a log folder at 2.6Gbyte. In it there are several folders but one is called W3SVC1 (small) but has an "associated" folder W3SVC1nnnnnn at 2.44Gbyte and dated today.

Hm, is there a way to legitimately purge these logs?

Thanks for your time.

 

[ShackDaddy]

Just open the folder and delete every log file except for today's. Actually, I usually leave all of the last 30 days, but you can't go ahead and purge them as if they were unwanted files. As long as you aren't having big issues with web access to Exchange resources, you will probable never need to refer to them, and even if you were...there are always more being generated.

Sometimes on servers with severely limited disk space on C:, I actually turn off IIS logging altogether.

Dave Shackelford MVP
ThirdTier.net
TrainSignal.com