Are most people using the standard cache size of 2 GB for the client install?

I'm assuming the MSI gracefully exits if it doesn't have enough disk.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Currently 'Yes', but I'm still working with the traditional streaming environment & only streaming what's needed / on-demand. Most of my customer's apps are small client installs anyway, but as I move forward with more apps I can use SMS to send out the appropriate Registry key to increase them later.
Answered 05/08/2008 by: BadShadd
Orange Senior Belt

Please log in to comment
0
You can always increase the cache size after the fact (not shrink it) but 2GB might not be enough for laptop users because you usually pre-cache the entire sequence unless you are going to try streaming through the DMZ to laptops (internet accessible) or VPN. On a terminal server farm with 200 apps I see around 25-30GB utilization with everything cached but that isn't what it might bloat to after it's been operational for a while.

The MSI should generate an error if there isn't enough space for cache but I don't remember exactly what it would throw. I think it is a generic installation failed code.
Answered 05/08/2008 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Alright, thanks guys.

Just using it on clients.. mostly desktops. No TS servers. I'm thinking about doing 4GB to start. They don't have a tonne of apps but the ones they do have are large.

Everything's big these days I guess. Can you believe that Adobe Reader is 200 MB sequenced? What a boated pig of a program that thing is.
Answered 05/08/2008 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity