Automatically Cleaning SCCM Client Cache

Hi, @Donald-0332

Thank you for posting in Microsoft Q&A forum.

The SCCM client cache does not have an automatic process for cleaning up itself. However, the cache is managed by the Configuration Manager client, which does not automatically delete cached content unless new content requires its disk space. Cached content remains in the cache for a configured number of minutes after it is used. If the cache is full and new content needs to be downloaded, the client will attempt to download it again during the next retry interval, which occurs every four hours until it tries 18 times.

To manage and clear the cache periodically, you can configure the cache settings during client installation or adjust them afterward in the Configuration Manager console. It is important to use the supported methods for deleting files in the cache, such as the "Delete Files" option in the Configuration Manager control panel, rather than manually deleting files from the cache folder.

For more effective management, you can also adjust the size of the client cache without reinstalling the client by using the cache size settings available in Client Settings in the Configuration Manager console.

For your references:

Configure the content cache for Configuration Manager clients

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

Despite all your best efforts, you may find clients still exceeding the set size allow for the client cache. When this happens, you need to sometimes manually intervene. What I have done in the past is use the SCCM "Scripts" functionality instead of creating a "package".

SCCM Scripts

Just make sure to use the correct PS commands to clear the ccmcache, don't just "delete" it.
I believe another way to manage this is with compliance baselines. You can have a PowerShell script check the size of the ccmcache and a remediation task to clean it up. Another way is simply remote PowerShell commands to clear it looping through a CSV file.