Re: Running out of disk space on C:
- From: Dave Solly <DaveS@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 Apr 2010 02:03:01 -0700
Thanks Larry - what a wealth of useful stuff ! I think this could go a long
way to resolving my problem (though I'd be glad to find even more !). As far
as this system goes:
Users Shared Folders, Company data, Exchange & Client Apps are already on E:.
Not currently using Sharepoint Fax or WSUS, and no local print spooling.
Page file is a good idea - thanks for the reassurance I can move it.
Clearing all D&S\username\Local Settings\TEMP will also yield 560MB. And if
I move all the C:\Windows\$uninstall folders to E that would save 730MB.
Would that muck up Add/Remove Programs or use of MSICUU ?
SBSMONITORING database (path C:\MSDE\MSSQL$SBSMONITORING as set by install,
not Program Files) is 400MB so worth moving. When I do this do I ONLY move
the 2 files listed in the article ? What about tempmdb.mdf, templog.ldf, and
the master, model and msdbdata files ?
ISA Firewall database (MSSQL$MSFW) is 43MB so probably not worth moving.
However although I've got ISA logging (Firewall & Proxy) to E:, there's still
607MB of ERRORLOG.nn files in C:\PFiles\Microsoft SQL Server\MSSQL$MSFW\LOG.
Can I delete those ?
Not sure which system32 logfiles you meant. I have 1MB in system32, 30MB in
system32\logfiles, 28MB in Windows, and 8MB in Windows\Debug ?
I've also got a 200MB logfile C:\PFiles\MS Windows SBS\Support\MSSBSSSR.log.
"Larry Struckmeyer[SBS-MVP]" wrote:
Here are some official documents on the subject, as well as some recomendations
gleaned from this news group and other sources. A 20 GB system partition
will require some attention as service packs and updates take up room.
As pointed out by others, you can find the space hogs with treesize pro or
Moving Data Folders for Windows Small Business Server 2003
How to move Exchange databases and logs in Exchange Server 2003
How to Move Small Business Server 2000 Company and Users Shared Folders
How to Move the Client Programs Folder to Another Location in Windows Small
Business Server 2003
How to Move the Windows Default Paging File and Print Spooler to a Different
Look at where the ISA logs are kept
You can move the C:\windows\uninstall$ folders off your systemroot, but you
may want to keep them in case you have to move them back.
Remove any folders or files under the c:\documents and settings\user name\local
If Monitoring is enabled it can create a file that could be large. Run through
the wizard again to flush out the gooey stuff..
Delete logs older than "date of your choice" from the system32 folder. Likewise
the logs and reports from the ISA folder.
Search for and delete old dmp files.
You can move the page file to another partition. The only downside is that
if you get a "blue screen" you will not get a full memory dump, and since
only MS can read them anyway, I don't see that it matters much.
You may gain some usable space and increase system performance in Windows
Server 2003 by moving the printer spool files to a different drive than the
one that holds the operating system. Note that this should be a different
spindle, but a different partition will help the OS a bit also.
By default, Windows Server 2003 places the printer spool folder at %systemroot%\System32\Spool\Printers.
However, you can potentially increase system performance by moving the printer
spool files to a different drive than the one that holds the operating system.
Computers frequently access system files, so moving the printer files to
a different location allows faster access to those files. The drive won't
have to try to service requests simultaneously.
To change the location for the printer spooler files, follow these steps:
1. Go to Start | Printers And Faxes.
2. From the File menu, select Server Properties.
3. On the Advanced tab, enter the location where you would like to spool
print jobs. If the location doesn't exist, this process will create it for
you. Make sure the new location has sufficient disk space to handle large
4. Stop and restart the printer spooler service, or reboot the server.
Please post the resolution to your
issue so others may benefit
Get Your SBS Health Check at
Our SBS2003 has a RAID-5 HDD partitioned 20GB C: for the system and
for user data. This was ok originally, but C: is gradually filling up
now 17.5GB used (D&S 1.7GB, MSDE 0.5GB, PFiles 5GB, Windows 6.5GB,
3GB) which caused my latest software update to run out of disk space.
reluctant to try to resize partitions (don't trust Partition Magic 7
server RAID array), and have done what I can to reduce the size of C:,
* located user SQL DBs and SBS Client Apps on E: not C:
* with Disk Cleanup, removed everything offered
* also deleted older larger files from D&S\<username>\L~S\TEMP and
Is there anything else I can safely delete ? For example there's
log files under PFiles\..\MSSQL$MSFW, 150MB in PFiles\MS SQL Server
400MB in D&S\....\NTbackup\catalogs, another 500MB in D&S\...Local
Settings\TEMP, 800MB in Windows\system32\Debug\isalog.bin and .bak
Any advice much appreciated !
- Prev by Date: Re: Delete old WSUS 2 Database files
- Next by Date: Re: iPhone and Exchange
- Previous by thread: Re: Running out of disk space on C:
- Next by thread: Re: Running out of disk space on C: