×
×
×
×

Which files can I delete from the folders in the Central Server to increase space?

Managing Disk Space on the Endpoint Central Server

The Endpoint Central server accumulates files over time — old patch builds, upgrade artifacts, log archives, crash dumps, and configuration backups. Left unmanaged, these can consume significant disk space and eventually block log creation, patch downloads, and server upgrades. This page helps you identify what is consuming space, understand what is safe to remove, and automate cleanup going forward.

Important
Stop the Central Server before manually deleting any files. Deleting files while the server is running can cause data corruption or incomplete cleanup.
Note
Minimum disk space: The Central Server requires at least 5 GB of free disk space at all times on the drive where it is installed. For upgrades, additional space equal to the size of your current server data is required. Refer to the Pre-Requisites section of the Installing Service Pack page for upgrade-specific space requirements.

Step 1 — Identify what is consuming space

Before deleting anything, identify which folder is consuming the most space. If third-party tools such as TreeSize are unavailable due to licensing restrictions, use the following native PowerShell command on the machine where the Central Server is installed:

Open PowerShell as Administrator and run:

Get-ChildItem "C:\Program Files\UEMS_CentralServer" -Directory |
ForEach-Object {
    $size = (Get-ChildItem $_.FullName -Recurse -File -ErrorAction SilentlyContinue |
             Measure-Object -Property Length -Sum).Sum
    [PSCustomObject]@{ Folder = $_.Name; "Size (GB)" = [math]::Round($size / 1GB, 2) }
} | Sort-Object "Size (GB)" -Descending | Format-Table -AutoSize
Note
Replace the path above with your actual installation directory if it differs. To find the installation path, open services.msc, locate ManageEngine UEMS - Server, right-click, and go to Properties > General.

This command lists every top-level folder under the Central Server installation directory sorted by size, so you can immediately see which folder is the largest contributor and act on it first.

Step 2 — Safe deletion reference

Once you have identified the folders consuming space, use the table below to determine what can be safely removed. Every folder and file type is explicitly marked with a deletion status and the reason behind it.

Important
Stop the Central Server before deleting any files from the folders listed below. Always retain at least one previous build folder in PatchBackup\ and Patch\ as a rollback point.
Folder pathFile or folder typeSafe to delete?Condition / Notes
<Install_Dir>\bin\Zipped log files (e.g. UEMS_CentralServer_Logs.zip)YesThese are compressed log archives. Deleting them does not affect server operation.
<Install_Dir>\bin\Heap profiler files (.hprof)YesCreated automatically during Java crashes. Safe to delete once the crash has been investigated or reported to support.
<Install_Dir>\bin\MiniDump files (.mdmp)YesCreated after native crashes. Safe to delete once the incident has been reported or resolved.
<Install_Dir>\bin\Empty (null) foldersYesLeftover empty directories with no content. Safe to remove.
<Install_Dir>\PatchBackup\Build backup folders (e.g. 70137-Feb-22-2011-15-10)Yes — with conditionRetain the folder corresponding to the immediately previous build as a rollback point. All older folders can be safely deleted.
<Install_Dir>\Patch\Build folders (e.g. ManageEngine_CentralServer-10.0.0-SP-252)Yes — with conditionRetain the folder for the previous build only. All other older build folders can be safely removed.
<Install_Dir>\Patch\PPM files (.ppm)YesPPM files are service pack installers used during upgrade. Once the upgrade is successfully completed and verified, these files are no longer needed and can be deleted.
Any drive (D:\, E:\, etc.)Old PPM installer files downloaded outside the install directoryYesPPM files downloaded to a non-default location for upgrade purposes can be safely deleted once the upgrade is complete and the server is running on the new build.

Step 3 — Automate cleanup going forward

Rather than manually managing disk space on a recurring basis, configure the following settings in the Endpoint Central console to handle cleanup automatically:

Patch Cleanup Settings

Navigate to Threats & Patches > Settings > Cleanup Settings to configure:

  • Remove superseded patches — Automatically removes older patch versions when a newer version is available. Recommended to keep enabled at all times.
  • Remove patches older than [N] days — Removes patches that are no longer missing on any managed computer after the specified period. Set a retention period based on your audit requirements — 30 to 90 days is a common range.
  • Space threshold notification — Sends an email alert when the patch repository exceeds a defined size. Configure this as an early warning before space becomes critical.

When a patch is removed from the Central Server, it is automatically removed from all Distribution Servers during the next replication cycle. No manual cleanup is required on Distribution Servers separately.

Configuration Cleanup Settings

Navigate to Admin > Configuration Cleanup Settings to automatically remove configurations that have remained unchanged beyond a specified number of days.

Step 4 — Move storage to another drive

If the drive where the Central Server is installed is consistently running low on space, consider relocating high-volume storage paths to a drive with more capacity. The following paths can be moved independently without reinstalling the product:

  • Patch store location — The directory where downloaded patches are stored. To change it, navigate to Threats & Patches > Settings > Cleanup Settings > Patch Download Location and update the path. Copy all existing patch files from the old location to the new one before restarting the server. Refer to Changing the Patch Store Location for detailed steps.
  • Software repository location — The HTTP repository used for software deployment. To change it, navigate to Software Deployment > Settings > Software Repository > HTTP Repository and update the path. Refer to Changing the Software Repository Location for detailed steps.
  • Database backup directory — The folder where scheduled database backups are stored. To change it, navigate to Admin > Database Settings > Database Backup and update the Backup Directory field. This can be set to a local directory or a network share path.
  • Remote control session recordings — Session recordings can accumulate significant space over time. To change the storage location, navigate to Tools > Remote Control > Settings and update the recording storage path to a drive with sufficient space.

Recovering from a "disk full" state

If the server drive is already full and the server is unable to start or log creation has stopped, follow these steps in order of priority:

  1. Stop the Central Server immediately if it is still running.
  2. Delete .hprof, .mdmp, and zipped log files from the \bin\ folder — these are typically the fastest to clear and carry no operational risk.
  3. Delete old build folders from \PatchBackup\, retaining only the previous build folder.
  4. Delete old build folders and .ppm files from \Patch\, retaining only the previous build folder.
  5. Verify that at least 5 GB of free space is available before restarting the server.
  6. Once the server is back online, configure Patch Cleanup Settings to prevent recurrence.