This assumes you installed vCenter 5.5 U2 components on the D or E drive on windows 2012 R2 with the exception of the web client which has to be installed on C: to work.
#1 - C: Out of Space
# 2 - Windows Folders
- Empty out C:$RecycleBin
- C:WindowsWinSxS – Windows Server 2012 R2 – Run this commands as admin.
dism /online /cleanup-image /StartComponentCleanup /ResetBase
- Use one of the following programs to find the largest files/folders.
SpaceMonger 1.4.0 – Portable, from 2000, still works with Server 2012.
# 3 - RDP Profiles
Store RDP user profiles to another partition.
Note – This will be for new RDP users so you will need to remove existing users profile. Yes, this works with Windows 2012 R2
#4 - vCenter logs
#5 - Crash Dumps
CrashDumps ex. vpxd-13.dmp are stored in C:WindowsSystem32configsystemprofileAppDataLocalCrashDumps
In the registry, HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsWindows Error ReportingLocalDumps
set the DumpFolder string from %LOCALAPPDATA%CrashDumps to E:VCenterLogsCrashDumps
NOTE- This will store non-VMware application crash dump files
# 6 - Infrastructure Logs
Even-though all vCenter components installed to the D: drive the Inventory Service and Profile Driven Storage logs are still being written to C:
Changing the following is NOT SUPPORTED!!! I would not do it. Bite the bullet and add disk space.
- C:Program FilesVMwareInfrastructureInventory Serviceconfwrapper.conf
Write the log file to E:VCenterLogsInventory Servicewrapper.log
# Log file to use for wrapper output logging.
wrapper.logfile=E:VCenterLogsInventory Servicewrapper.logChange the following from the default 50 megabytes times 50 to 50 megabytes times 2 for only 100 megabytes of space.
- Ditto for the Profile-Driven Storage wrapper.log plus the following
Changing the following to E: is also risky.
- Ditto for C:Program FilesVMwareInfrastructuretomcatconfwrapper.conf plus the following