About the App-V Client Cache size not being (fully) controlled by the Registry Value FileSize

Abstract:

The App-V Client comes with the Registry Value “FileSize” in the “AppFS” key that indicates to control the App-V client’s cache size. This is not the case.

Instead, there might be a difference between the FileSize Registry value on the one hand and the actual maximum value and the value shown in the App-V Client Management Console on the other hand.

To adjust the maximum cache size using centrally controlled methods you have to initialize/flush the App-V cache or to use Microsoft’s App-V Cache Resizer Resource Kit tool.

The Issue

You may define the size of the App-V cache using the SWICACHSIZE parameter during installation to set the maximum cache size to either a fixed value or to a define the reserved free disk space.

As a visible result, both the App-V Client Management Console and the Registry show the maximum Cache size.

If you want to decrease the cache size, you have to “initialize” or “flush” it. The described issue does not occure then.

If you want to increase the cache size afterwards, you simply may try to increase the FileSize RegValue, for instance by means of a Group Policy change or an automated Registry modification.

If you do that, the result will (of course even after several Reboots) look like this;

• According to the Registry the Max Cache Size is about 8,000 MB
• According to the App-V Client MMC the Max Cache Size is about 6,144MB

App-V Cache Size difference

The Enforced Cache Size (i.e. the “real” Max Cach Size) case is set to the value shown in the MMC: 6,144 MB. The cache won’t grow beyond that.

So you increased you cache size by increasing the Registry Value but your applications still don’t fit into the Cache file. Strange, right?

The Reason

As you may have noticed, modifying the Registry Value does not automatically modify the Enforced Cache Size, this is the lesson we have learned.

The Enforced Cache Size is a property of the App-V Virtual File System Driver, but not of the FileSize Registry value. This property can only be modified by using the right APIs of the driver.

When the value is modified using the MMC, actually two things happen: The MMC triggers the API to set the Driver’s Property. The Registry Value is set “only” as a side effect of that process.

The Solutions

Actually, there won’t be a “fix” for that behavior, because this is how Microsoft designed it.

But how can the Cache Size setting be adjusted properly? Well, there are some options:

(Note: All methods preserve the User Settings. They aren’t affected negatively by modifying the Cache File)

1. Use the App-V (Client) Management Console:
   • CON You only can increase the value
   • PRO All Clients including 4.1 and 4.2 are supported
   • PRO It keeps the Client Cache, i.e. applications don’t have to be re-streamed
   • CON: This Solution can’t be automated/centrally controlled
2. Use the App-V Cache Resizer Resource Kit Tool http://technet.microsoft.com/en-us/appvirtualization/dd277292.aspx
   • CON You only can increase the setting
   • CON This solution works only for version 4.5 and above. It can’t be used for 4.1/4.2 clients
   • PRO It keeps the Client Cache
   • PRO Automation / Central deployment is possible
3. Enforce the Cache to re-initialize
   • PRO You can decrease and increase the setting
   • PRO All Clients including 4.1 and 4.2 are supported
   • CON The Cache is flushed: All applications have to be “re-streamed”
   • PRO Automation / Central deployment is possible

	Increase Cache	Decrease Cache	Keep Cached content	Automated deployment	Clients supported
Client MMC					4.1, 4.2, 4.5, 4.6
Cache Resizer					4.5, 4.6
Initialize Cache					4.1, 4.2, 4.5, 4.6

How To Initialize the SoftGrid/App-V Cache

To re-initialize the Virtual Application Cache, you set the “State” value to 0 (Zero) and reboot the Client machine

This forces to re-create the Client Cache. All previously cached applications are erased from the cache and have to be re-loaded. Application Records, Shortcuts and User settings are not affected.

The App-V Blog gives a more detailed description at http://blogs.technet.com/appv/archive/2007/11/14/softgrid-operations-guide-part-2.aspx, also you may refer to Microsoft’s KB article at http://support.microsoft.com/?scid=kb%3Ben-us%3B931575&x=21&y=12.

Of course Ment’s Application Virtualization Client Diagnostics and Configuration tool described at http://www.softgridblog.com/?p=114 also is capable of resetting the cache.

Depending on the App-V Client Version, the “State” value is located in the follwoing Registry Keys:

App-V 4.5/4.6, 64 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS

App-V 4.5/4.6, 32 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS

SoftGrid 4.2/4.2: HKEY_LOCAL_MACHINE\SOFTWARE\Softricity\SoftGrid Client\CurrentVersion\AppFS\

Advertisements

---

Posted in App-V, Tools
Tags: 4.5, 4.6, 4.6 SP1, App-V, HowTo, Tools