Files safe to delete?

Sponsored Links

Hey all, i have some old servers, and I am trying to delete files to free up
space. Does anyone know if these are safe to delete/move??

C:\WINDOWS\Installer\$PatchCache$\
C:\WINDOWS\SoftwareDistribution\Download
C:\Windows\Ie7updates


********
To others who stumble across this forum, i have found the following NOTsave
to delete;
DO NOT DELETE THESE FILES!
********
X $hf_mig$ can NOT be removed, although it can be compressed. this
directory tells future updates what has already been done
X C:\windows\installer can NOT be removed, although duplicate files can
be removed. this is used for uninstalls and installs of new apps
X C:\windows\assembly can NOT be removed, this is a .NET folder, do not
play with or compress

*******
I have found that it is save to delete or move these files;
*******
O $Ntxxxxxxx$ files can be removed from the c:\windows directory
O Attempt to move the page file
O Run the disk clean up utility, and compress old files, and empty the
recycle bins
O The temp directories in the user profiles can be cleaned out, also
check the desktops for downloaded apps for their setup file
O C:\WINDOWS\Downloaded Installations\ These should be safe to remove,
but probably a good idea to leave them alone as the updates may need them, be
careful here.
O Ok to delete log files for Symantec
C:\Documents and Settings\All Users\Application Data\Symantec\Symantec
AntiVirus Corporate Edition\7.5\Logs
C:\Program Files\Common Files\Symantec Shared\Reporting
Agents\Win32\ReporterSvc.log
O Quarantine files can be removed from Symantec, usually here;
C:\Documents and Settings\All Users\Application Data\Symantec\Symantec
AntiVirus Corporate Edition\7.5\Quarantine
O Ok to delete zip files from Symantec, and actually all files in here
C:\Documents and Settings\All Users\Application
Data\Symantec\LiveUpdate\Downloads
O IIS web logs ok to remove C:\WINDOWS\system32\LogFiles\W3SVC1
There is no option to do this automatically, this must be scripted
O Log ok to remove C:\WINDOWS\system32\wbem\Logs\FrameWork.log
There is no option to do this automatically, this must be scripted