Client Cache requires ridiculous amount of disk space

Question

I'm testing SCCM 2012 R2 with a Windows 7 client. I'm on my second application install and both apps gave me error that the cache was not large enough. The first time I increased it to 9GB and for the second app I increased it to 15GB. Both times I did it
manually from the client machine.
If these apps are only 5MB in size why is the cache having to take up so much room? Also, is there a way to have the install automatically delete the cache if the install will be too big?

Answer 1

I've never had this type of issue, in all the years we've used ConfigMgr.
Assuming your installation of ConfigMgr is healthy, the first thing I'd look into, is if you may have inadvertently created the package for your 5Mb application by specifying the wrong source folder.
What I mean by that, is that sometimes, it's easy to inadvertently point the package source location at the wrong folder for source, if you point the source folder at, say, the root of a large software library (instead of the specific application folder), your
end up creating a package that is massive in size because it has all source for all applications in a single package.
(I've seen it done. It's not funny at the time, but afterwards, it gets a grin and office-myth status ;)
So, on a client, examine the ccmcache folders and content. if there's only supposed to be a single application install source in there, verify that.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)