Cleanup Settings Cloud
C:\Program Files (x86)\ManageEngine\UEMS_Agent\patches. To reclaim space, you may delete older files from that patches folder only; do not delete other files or folders under the UEMS_Agent directory. C:\Windows\System32\DriverStore\FileRepository is managed by Windows; Vulnerability Manager Plus does not store patch binaries there and cannot clean it from the console. See Windows DriverStore FileRepository disk space.To configure cleanup settings, go to Threats & Patches → Settings → Cleanup Settings.
Configure the following options under Cleanup Settings:
Location of the Distribution Server
After changing a Distribution Server’s patch-store location, verify that existing files have been copied and the new store is in use before removing files from the old path. Follow the Distribution Server steps in Configure patch store location. Patch-store migration and software-deployment repository migration are separate procedures.
Under Patch download location, check the DS directory where patches are downloaded. Make sure its drive has enough free space for the downloaded patches. For replication failures that report low disk space, follow Distribution Server disk-space checks.
The default Distribution Server patch store is C:\Program Files (x86)\ManageEngine\UEMS_DistributionServer\replication\store. Identify the Distribution Server computer from Agent → Remote Office.
Patch Download Settings
Downloading or pre-staging a patch does not install it. Installation still requires an eligible task and its policy. Pre-staging uses bandwidth and Distribution Server storage. Review the offices assigned to that Distribution Server and the deployment policy before changing this setting.
Enable Download the missing patches in the network to download patches that meet the selected criteria to the Distribution Server. These downloads include qualifying patches outside APD tasks or test groups.
After enabling the checkbox, under Patch download criteria, you can choose to download All missing patches or All approved missing patches. All approved missing patches downloads only patches that you have approved. Approve a patch with Mark As in a patch view. See Test and Approve.
Patch Cleanup Settings
Use these settings to remove eligible patch files from the Distribution Server and free disk space. Cleanup runs according to its schedule and eligibility rules. The patch-store usage notification is separate from the free-space check that can block replication.
Remove Superseded Patches: Enable this option to remove superseded patches from the Distribution Server.
Remove the patches that are older than: Enable this option and select a retention period. Eligible patches older than that period are removed when they are not missing on any managed computer.
Patch retention after cleanup
Patch Cleanup Settings do not remove every downloaded file as soon as you save the configuration. Patches remain in the store when any of the following is true:
- The patch is still detected as missing on any managed computer.
- A related patching task is failed, retrying, or in progress.
- The patch Superseded value is N/A. The vendor has not superseded that version, so Remove Superseded Patches does not remove it.
There is no force-cleanup option besides these settings. To request additional automatic cleanup, submit a feature request.
For an immediate cleanup, delete the downloaded patches from the console in the Distribution Server-wise view; they are then removed from the Distribution Server.
Delete files from the Distribution Server store only when no active, in-progress, or retry task needs them; otherwise they are redownloaded. If a deleted patch is still missing on a managed computer, it is redownloaded.
Decline Patch removes the patch from the Distribution Server during the next daily sync, even if the patch is included in an Automated Patch Deployment task.
To stop older patches being retained for decommissioned computers, remove those computers from Agent → Computers, then delete the corresponding older patches from the patch repository. Alternatively, decline the patches that remain missing only on those machines and delete them from the repository; declined patches are not downloaded automatically unless they are manually deployed.
Extra Office language files remain until the configured cleanup age is reached or they are deleted manually. Keep only the languages you manage in Threats & Patches → Settings → Office Click-to-Run Settings. See Microsoft 365 (Office 365) Patch Deployment.
Notification Settings
To receive notifications about this activity, configure the Notification Settings.
Notify when the space occupied by the patch exceeds: Enable this option and set a size limit. You receive a notification when downloaded patches occupy that space or more on the Distribution Server.
Enter the email address that must receive the notifications. If the Mobile App is installed, you can also configure notifications in it.
Click Save to apply the settings.