du -sh /*

rm -rf /tmp/*
rm -rf /var/tmp/*

http://www.if-not-true-then-false.com/2012/delete-remove-old-kernels-on-fedora-centos-red-hat-rhel/

yum install yum-utils
rpm -q kernel
package-cleanup --oldkernels --count=2

Uses aptitude package manager.

Paste this at the CLI then run rmkernel to remove all kernels except your running kernel.

rmkernel () {
        local cur_kernel=$(uname -r|sed 's/-*[a-z]//g'|sed 's/-386//g')
        local kernel_pkg="linux-(image|headers|ubuntu-modules|restricted-modules)"
        local meta_pkg="${kernel_pkg}-(generic|i386|server|common|rt|xen|ec2)"
        sudo aptitude purge $(dpkg -l | egrep $kernel_pkg | egrep -v "${cur_kernel}|${meta_pkg}" | awk '{print $2}')
}

http://www.omegaprojex.com/index.php/2008/11/10/moving-shares-and-users-home-folders-to-a-new-server/

http://alloraconsulting.com/it-solutions/76-windows-server-2008-low-space

http://serverfault.com/questions/8187/whats-the-best-way-to-move-c-users-to-d-users-under-vista-w7

$Windows.~BT and $Windows.~WS are temporary folders and can be safely deleted.

takeown /F C:\$Windows.~BT\* /R /A 
icacls C:\$Windows.~BT\*.* /T /grant administrators:F 
rmdir /S /Q C:\$Windows.~BT\

Now copy-paste the following and hit Enter to delete the contents of $Windows.~WS directory

takeown /F C:\$Windows.~WS\* /R /A 
icacls C:\$Windows.~WS\*.* /T /grant administrators:F 
rmdir /S /Q C:\$Windows.~WS\

cd c:\users
dir
wmic /node:localhost path win32_UserProfile where LocalPath="c:\\users\\user" Delete 2>>c:\windows\temp\wmic.err

Compress the C: drive from the CLI:

compact.exe /s /c /a /i <drive>:\*

For Windows 7 or Server 2008 enter this command:

rd /s c:\$Recycle.Bin

For Windows XP, Vista, or Server 2003 enter this command:

rd /s c:\recycler

Delete hiberfil.sys:

powercfg.exe -h off

By default, the pagefile will be as large as your system RAM. While this is important for Suspend-to-RAM, it may not be very important for most workstations.

System Properties → Advanced → Performance Options → Advanced

• Very useful tool for finding problems

http://www.jam-software.com/treesize_free/

• Cleans temp files
• Good for RDS servers
• Seems to work on 2012 R2
• Run as administrator

http://www.ctrl-alt-del.com.au/files/ICSweep.zip

c:\support\icsweep.exe /size
c:\support\icsweep.exe /all

• Short script
• Probably best used as an emergency 'free space now' tool

@echo off
rem Script to clean up disk space on SBS 2008 servers
rem Downloaded from SBSfaq.com
rem V1.0 - March 28th, 2010
rem Certificate Services Logs
net stop "Active Directory Certificate Services"
del c:\windows\system32\certlog\*.log
del c:\windows\system32\certlog\*.chk
del c:\windows\system32\certlof\*.jrs
net start "Active Directory Certificate Services"
rem IIS Log Files
Del C:\inetpub\logs\LogFiles\*.log /f /s

CleanUp may be useful to clean up Windows Profiles:

https://bitbucket.org/dev247/cleanup/overview

If you are building new systems:

http://support.microsoft.com/kb/949977

https://support.appliedi.net/index.php?/Knowledgebase/Article/View/992/0/how-to-enable-the-disk-cleanup-tool-on-windows-server-2008-r2

On 2008 R2, at an administrative command prompt:

copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe %systemroot%\System32

copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui %systemroot%\System32\en-US

Cleanmgr.exe

2012 R2 - SxS: https://www.saotn.org/windows-server-2012-r2-disk-cleanup-dism/

The Disk Cleanup Tool is available in Windows Server 2012, if you install the Desktop Experience feature.

All existing service packs and updates cannot be uninstalled after this next command is completed.

Clean up all superseded updates:

dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

Clean up after service packs:

dism.exe /online /Cleanup-Image /SPSuperseded

https://www.msoutlook.info/question/463

https://www.howto-outlook.com/howto/movingostpstoutlookcomimap.htm

Perhaps as an administrator:

1. Create a new directory/structure on the destination disk drive to hold the user's local cache
   1. Adjust permissions so that user, and administrators, can access the directory/contents
2. Move the user's .OST file to the new location
3. Create a symbolic link from the old file/location to the new
4. Start Outlook
   1. If any problems, close Outlook and check permissions

As the user whose .OST file we are moving, create the symlink at a command prompt:

mklink "C:\Users\<profile>\AppData\Local\Microsoft\Outlook\<username>@<domain.tld>.ost" "E:\Users\<username>\Mail\<username>@<domain.tld>.ost"