locked
SCCM and App-V Integration - best practice for setting cache szies RRS feed

  • Question

  • Hi,

    Has anyone got any theories or feedback on the best settings for sccm cache and app-v cache sizes? We current have our SCCM cache at 5GB and softgrid at 4GB but now moving to App-V clients. I'm thinking moving to allowing the app-v cache to be based on free space remaining but am unsure.

    Any thoughts?

    Thanks!

    Thursday, April 23, 2009 2:58 PM

Answers

  • As Troy said, the size of the SCCM cache depends on the deloyment method. 4 GB for the App-V cahce might be enough, but as soon as you deploy larger applcation, you may run out of App-V space.
    If you intent to move from "installation" to "virtualization", you could try to find a Client with a lot of applications installed, add the "Program Files" and "Program Data" information, double it and take this as a result.
    If you already have a lot of applications virtualized, sum up the newest versions of your SFT files , double that and you should be fine for a while.

    Persoanlly I think the approach of defining the free space is a little bit risky, because on certains clients it coulöd end up with a very samll App-V Cache.

    Please remember, that if you simply check your current client's App-V cahce, the result may be misleading becasue in Legacy App-V/SoftGrid, often only FeatureBlock 1 was loaded. In SCCM, it always will be the whole package that gets loaded on the client.


    Falko
    • Proposed as answer by znack Tuesday, May 12, 2009 7:18 PM
    • Marked as answer by Aaron.ParkerModerator Monday, December 26, 2011 12:25 PM
    Friday, April 24, 2009 8:29 AM
    Moderator

All replies

  • Hello,

    This depends on your current available harddrive and the needs of your organization.

    How many applications do you have and what size are they? How will you deliver them? What will be delivered to the cache, and what will not?
    Thursday, April 23, 2009 4:08 PM
  • If "moving to App-V" means that all packages(if capable) will now be delivered as virtualied, I would go with the freespace method. Your method of delievery plays a big part in how much space you'll need also. Download and execute drops the sft file to the local ConfigMgr client cache AND is loaded into the App-V cache also, which can eat up a lot of space. Streaming leaves the SFT(s) up on the DP's so the server takes the hit on that space and not the clients.  

    Troy


    TroyW
    Thursday, April 23, 2009 4:20 PM
  • As Troy said, the size of the SCCM cache depends on the deloyment method. 4 GB for the App-V cahce might be enough, but as soon as you deploy larger applcation, you may run out of App-V space.
    If you intent to move from "installation" to "virtualization", you could try to find a Client with a lot of applications installed, add the "Program Files" and "Program Data" information, double it and take this as a result.
    If you already have a lot of applications virtualized, sum up the newest versions of your SFT files , double that and you should be fine for a while.

    Persoanlly I think the approach of defining the free space is a little bit risky, because on certains clients it coulöd end up with a very samll App-V Cache.

    Please remember, that if you simply check your current client's App-V cahce, the result may be misleading becasue in Legacy App-V/SoftGrid, often only FeatureBlock 1 was loaded. In SCCM, it always will be the whole package that gets loaded on the client.


    Falko
    • Proposed as answer by znack Tuesday, May 12, 2009 7:18 PM
    • Marked as answer by Aaron.ParkerModerator Monday, December 26, 2011 12:25 PM
    Friday, April 24, 2009 8:29 AM
    Moderator