By default Configuration Manager 2012 client stores deployed packages in %windir%ccmcache folder and default disk space for cache folder is 5120 MB.
All deployed packages and also software updates will be keep in these default folder unless you specify custom location with installation options.
Regarding TechNet article please note that:
One of the main concern about client cache is auto-empty mechanism. There are several scripts around the web that deletes client cache but be aware that client will not be notified so will try to use cached content if installation is not succeed yet.
If you configure the package properties with the option to persist content in the client cache, client does not automatically delete package content from cache.
Likewise you can specify following properties to configure caching options on clients:
Please note that if you use SMSCACHESIZE option and the package would cause the folder to exceed the maximum size, package download fails.
Client Cache size and location is something that can be changed using GPO, so it can give more space for ConfigMgr Administrator to work in.
Hey Anil,
I wrote a guide how to change the cache size, either by Push Installation or via VBS.
This can probably be done via registry too, but I have not tried it (since I found 2 other working solutions).
Take a look: heineborn.com/.../sccm-2012-not-enough-temp-space
Here's how I did it using the new Application method: fearthemonkey.co.uk/how-to-change-the-configuration-manager-2012-cache-size-using-the-application-method
Hi Anil, has anyone ever seen a case where the cache on this asset is standard at 5120 MB however although SOME content is tombstoning, teh cache is now at 8GB and growing with NO OUTSIDE interference?
This is unknown to the Microsoft tech onsite and would require I open a separate case.
Anyone know of this anomoly?
I've tested this in the Setup Windows and ConfigMgr section and this does not seem to work on newly created computers. It's nice to see people creating apps and scripts that make this change AFTER creating a new computer, but these steps wouldn't be necessary if it could be done while creating/generating a new computer using SCCM's task sequences.