dalewright
asked on
Low disk space - SBS 2003 - windows updates
Morning guys
I am running fairly low on disk space C (Raid 5) with around 1 gig remaining and dropping with updates being downloaded.
I have disabled the updates for the time being and moved some large files and SQL databases to another drive...
My question is, there seems to be large amount of windows update folders in the C: windows drive location.
Is it safe to delete these files? I have read conflicting reports, some saying its ok as long as you dont want to remove the updates from the system, others saying that it could result in the OS becoming unstable.
Any views and suggestions are welcomed...
Cheers.
I am running fairly low on disk space C (Raid 5) with around 1 gig remaining and dropping with updates being downloaded.
I have disabled the updates for the time being and moved some large files and SQL databases to another drive...
My question is, there seems to be large amount of windows update folders in the C: windows drive location.
Is it safe to delete these files? I have read conflicting reports, some saying its ok as long as you dont want to remove the updates from the system, others saying that it could result in the OS becoming unstable.
Any views and suggestions are welcomed...
Cheers.
which size has the partition? You may look with 'treesize'
http://www.jam-software.de/freeware/
if there is any other stuff eating up your space.
And I think leew is right, you can delete those folders.
http://www.jam-software.de/freeware/
if there is any other stuff eating up your space.
And I think leew is right, you can delete those folders.
So long as you've rebooted once since the packages corresponding to the uninstall directories have been installed, it should be safe to delete.
You must keep in mind, though, that those packages contain the uninstall routines for the updates, and removing them may make it difficult to uninstall updates to have cause problems.
Other things you should check are whether you have hibernation enabled. It's generally not needed in servers. But if there is a large Hiberfil.sys hidden/system file in the root of your drive, disable hibernation to make it go away. Also, download and run CleanUp! by Steven Gould. It is my go-to for freeing up space on the system. It will empty all temp directories for every profile on the system as well as recent file lists, cookies, and any files inside any folders named "temp".
Check how much space is being used for your pagefile (virtual memory) and see if shrinking that is an option.
And if you're running an NTFS file system, check that compression is enabled on the C drive. I've had that alone save me a couple gigabytes when applied.
You must keep in mind, though, that those packages contain the uninstall routines for the updates, and removing them may make it difficult to uninstall updates to have cause problems.
Other things you should check are whether you have hibernation enabled. It's generally not needed in servers. But if there is a large Hiberfil.sys hidden/system file in the root of your drive, disable hibernation to make it go away. Also, download and run CleanUp! by Steven Gould. It is my go-to for freeing up space on the system. It will empty all temp directories for every profile on the system as well as recent file lists, cookies, and any files inside any folders named "temp".
Check how much space is being used for your pagefile (virtual memory) and see if shrinking that is an option.
And if you're running an NTFS file system, check that compression is enabled on the C drive. I've had that alone save me a couple gigabytes when applied.
just sort the files in date order and delete the updates that are over 1 month old!!
ASKER
Hey guys
Cheers for the info... The link from leew was good..
I have done the following:
* Changed the spool location
* Cut and Copied files and foldes for WSUS and put them on a different drive
* Cleaned down IIS logs
* Checked the Exchange databases and there is over 3 gig, so going to move these drives to another location
* going to look into hibernation now
I am a bit unsure about the compression of the C: drive. Whats the potential issues with doing so?
Cheers for the info guys.
Cheers for the info... The link from leew was good..
I have done the following:
* Changed the spool location
* Cut and Copied files and foldes for WSUS and put them on a different drive
* Cleaned down IIS logs
* Checked the Exchange databases and there is over 3 gig, so going to move these drives to another location
* going to look into hibernation now
I am a bit unsure about the compression of the C: drive. Whats the potential issues with doing so?
Cheers for the info guys.
I never experienced a downside to the compression on my workstation, and tended to leave it on for it's benefits.
It is only very minimal compression.
If absolute top speed is an absolute priority, then don't run it.
But if you're looking for space, compression will help far more than it hurts.
It is only very minimal compression.
If absolute top speed is an absolute priority, then don't run it.
But if you're looking for space, compression will help far more than it hurts.
ASKER
Cheers Music
Gents, when you say Hibernation, i assume your talking about power options? if not, can some one please clarify.
Cheers
Gents, when you say Hibernation, i assume your talking about power options? if not, can some one please clarify.
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Still low on space. Around 1.6 has been eaten in the last week and i cant find a reason for it.
I read about conflicting posts on C:\WINDOWS\Installer files. There is around 10gig stored here, any views or ideas?
I read about conflicting posts on C:\WINDOWS\Installer files. There is around 10gig stored here, any views or ideas?
http://www.lwcomputing.com/tips/static/bootdrivesize.asp