Some information about SCCM 2012 Client Cache

SCCM client cache is location where it stores the packages on the client before any application runs from it.

The default location for the Configuration Manager client cache is %windir%\ccmcache and the default disk space is 5120 MB.

The Configuration Manager client downloads the content for required software soon after it receives the deployment but waits to run it until the deployment scheduled time. At the scheduled time, the Configuration Manager client checks to see whether the content is available in the cache. If content is in the cache and it is the correct version, the client always uses this cached content. However, when the required version of the content has changed or if the content was deleted to make room for another package, the content is downloaded to the cache again.

If the client attempts to download content for a program or application that is greater than the size of the cache, the deployment fails because of insufficient cache size and Configuration Manager generates status message ID 10050. If the cache size is increased later, the download retry behavior is different for a required program and a required application:

  • For a required program: The client does not automatically retry to download the content. You must redeploy the package and program to the client.
  • For a required application: Because an application deployment is state-based, the client automatically retries to download the content when it next downloads its client policy.

If the client attempts to download a package that is less than the size of the cache but the cache is currently full, all required deployments keep retrying until the cache space is available, until the download times out, or until the retry limit is reached for the cache space failure. If the cache size is increased later, the Configuration Manager client attempts to download the package again during the next retry interval. The client tries to download the content every four hours until it has tried 18 times.

Cached content is not automatically deleted but remains in the cache for at least one day after the client used that content. If you configure the package properties with the option to persist content in the client cache, the client does not automatically delete the package content from the cache. If the client cache space is used by packages that have been downloaded within the last 24 hours and the client must download new packages, you can either increase the client cache size or choose the delete option to delete persisted cache content.

More Via

2 Responses to "Some information about SCCM 2012 Client Cache"

  1. Hi Eswar,

    I have SCCM-2012 infrastructure.
    On some systems i found software updates are downloaded at directory "c:\windows\ccmcache" (asusual) as well as at directory "C:\Windows\SoftwareDistribution\Download" .
    i tried to to check whether system is still getting updates from internet but i found my SCCM MP as WSUS server for those systems in WindowsUpdate.log,WUAHandler.log; but did not get any clue this strange behaviour of SCCM client.

    So please help me out to understand the root cause.
    Sourabh Rathore

    1. Why did you configure for clients to download the content from Internet if you are sccm? I would try to enable gpo to disable software updates from Internet and let sccm configure the policy on client by making use of wsus. If the clients are downloading the content, you should really look at couple of logs... Wuahandler. Log, Windows update store. Log, deployment log etc whether the client scan successful or not..


Leave a Reply