We have a Windows 2008 server (not R2). There was 2.72GB of free space available on the system drive. I ran the compcln.exe utility from the Run command. It asked for confirmation, and after pressing Y the window immediately closed. I had read that in order to reclaim the space I need to add a feature then remove it to initiate a 'cleanup of the binaries'.
Anyone know of a manual removal procedure, please? The server was purchased before the last service pack was released so compcln.exe should have worked unless I'm missing something really basic here. The server is in a worse condition than when I started.
compcln exe server 2008
Uninstalling bits and pieces will never solve the larger problem. Looks like the only solution is to stand up a new DC on a larger disk, patch it fully, followed by system update readiness tool to make sure that servicing store is intact (2008 vista kernel is notorious for servicing corruption), join existing domain, dcpromo it, migrate the roles over.
I've removed those files and have also used cleanmgr to clean up the system partition. There is now 2.4GB free. The server also hosts the central installation of our security software so I'm looking at migrating that to a different server which will free up quite a lot of space (mostly used by SQL files).
The operating system on all servers is Windows server 2008 R2, no SP1 is installed and therefor the tools are non-existent (compcln.exe and vsp1clean.exe), in addition to that i'm not allowed to install SP1 on the servers.
Where ever it was possible i deleted many $NT... folders from the Windows directory and in some servers it did solve the free space issue, but on the rest of the servers I couldn't find any $NT... folders to delete.
And Windows 2008 R2 on a 30 GB volume? Forget about it; they just need more space. And if your disks are full, sounds like new server hardware's going to be damn near required as well. You can bit the bullet now or later. Now is cheaper.
Personally, I tend to favor a mirror RAID for the OS disk, and where needed, a 4-disk RAID 10 for the data partition (since practically every server made in the last 10 years supports at least 6 physical disks), but either way, this type of situation is why it's best to keep your data and OS volumes on different disks.
I agree with the guys who are saying 30 GB is not enough for Windows 2008 R2, but I had the same issue you are facing in the past and I couldn't do anything other than deleting some files. A utility called WinDirStat helped me a lot in identifying which folder is taking too much space. In my case, it was IIS Log files and was hidden from System Tools like clean up. So, I deleted them manually and it was a good temporary solution.
The Windows Component Clean Tool (COMPCLN.exe) can be used to remove the files that are archived after Windows Vista SP2 or Windows Server 2008 SP2 is applied. It also removes the files that were archived after Windows Vista SP1 was applied, if they are found on the system. Running this tool is optional.Installing Windows Vista service packs increases the amount of disk space that is used by the operating system. This space is used to archive files so that the service pack can be uninstalled. Typically, you should run COMPCLN.exe if you want to reclaim this disk space after applying SP2 and if you will not need to uninstall SP2. You cannot uninstall Windows Vista SP2 or Windows Server 2008 SP2 after you run this tool on an image.
Scavenging may also be performed proactively on Windows Server 2008 installations by forcing a removal event on the system. Scavenging will try to remove any unwanted system binaries from the installation and enable Windows to reclaim the disk space. To issue an uninstall event on a Windows installation, add and remove any unwanted system component that is not already installed, and then restart the Windows installation. Scavenging will be performed during the following restart of the operating system.
With the release of Windows Vista, Windows Server 2008, and now Windows 7, Microsoft significantly expanded the role of the WinSxS folder. Unfortunately, Microsoft seems to provide two different descriptions of the WinSxS folder.
This should be included script in the Citrix Optimization tool and BASE Image Script Framework for non-persistent virtual desktops. Reduced free space from 3.42GB to 6.47GB saving limited server SSD intellicache for our six servers. Great work, Thank you.
Once you've installed both Service Packs and everything is running well, AND you are absolutely 100% sure you do not want to uninstall it, AND you have backed up your system... You can run this command compcln.exe .
This will allow you to reclaim significant disk space. To do this press the Windows + R keys and type compcln.exe in the run box, or, if you prefer using the command line: press the Windows + R keys and type cmd then type compcln.exe .
When it comes to improving Windows server performance, most sysadmins focus on hardware such as adding CPUs or RAM. However, low disk space can also impact performance sometimes even causing critical processes such as backups to fail. Fortunately there are quite a few places to check on a Windows server to free up additional disk space. Some paces to check are obvious such as cleaning up log files while other paces are not as obvious such as finding system temp files.
Click on the View tab and select Show hidden files, folders, and drives. Uncheck Hide protected operating system files and Hide extensions for known file types. Making these changes will allow you to see all the files on the server including system files and folders which could be taking up unnecessary space. Click OK to close the window.
The next thing I do when I need to free up disk space is to compress the IIS site log files. The default path to these files is %SystemDrive%\inetpub\logs\LogFiles. However, I prefer to redirect that path to something easier to find at the root of the disk drive such as C:\wwwlogs. If the server has multiple drives I will store them on the largest drive. Unless you disable your site logs they will automatically grow until the disk drive has filled up or they are removed or they are deleted. Enabling Windows file compression on the IIS logs directory tree will save a considerable amount of disk space.
After applying compression to this folder I was able to save approximately 60% of the disk space used by the backups. By zipping the files as well can you save can even more space. Depending on your particular business needs, you can also save additional disk space by limiting number of backups SQL Server stores on the server. This can be configured with a SQL Server Maintenance Plan.
Windows Performance Monitor is an invaluable tool to analyze performance on a Widows server. Within minutes, one can easily configure a Data Collector to get deep insights on CPU, RAM, Network IO, and Disk IO. However, this convenience can also lead to disk space being needlessly consumed when you have forgotten about the reports days or weeks after the analysis has completed. This will be even more apparent if someone forgets to set a Stop Condition on the Data Collector and leaves it running for days.
Windows Error Reporting is an exceptional tool for identifying issues on your server. Unless you delete the logs or disable the feature they will accumulate over time. The default path to WER reports is C:\ProgramData\Microsoft\Windows\WER and there are two sub-directories below it. You can delete the files in the folders but you should leave the 2 folders in place. This is another great place to apply Windows file compression to save more space.
After the server has been installed you can access the Disk Cleanup tool from the Control Panel. You will have a convenient way to clean up different types of temporary files including Windows Update files and Windows Error Reporting files.
This tool is very helpful with cleaning up disk space. However, you should be aware that there will be some additional programs installed along with the Disk Cleanup tool which you may not want on your server such as Media Player. Here is a complete list of the programs that are installed with the Desktop Experience.
All of the options listed above will also work on Windows Server 2008 systems however specifically on Windows Server 2008 SP2 servers you can make the service pack permanent and free up space by running the following command which should free up nearly 1GB of disk space on the server:
Having your Windows server run out of space can cause serious performance issues as well as prevent important backup processes from running. I covered several great places to check on a Windows server when you need to free up space. Always confirm that files are safe to delete before you delete them. Thanks for reading!
Small Business Server 2008 installs default install puts everything on the C:\ Drive. there are tools available in the Small Business Server Console to move some of the data to other locations, but several folders that remain in the C:\ volume will grow if left unchecked, this will potentially eat all the available disk space on the C:\ drive. Once the C:\ drive begins to reach capacity some services will stop functioning properly on the server, while others will change their behavior to prevent data loss. The biggest impact of the low disk space issue is e-mail flow. The most common error is 452 4.3.1 Insufficient system resources. 2ff7e9595c
Comentarios