The conundrum of the unload least recently used in an App-V Stand-alone mode implementation
May 13, 2011 Leave a comment
During a recent engagement at a client, one of the complaints I heard from System Administrators and App-V Administrators was that App-V packages were being removed from the App-V cache when new applications are deployed to App-V clients in an App-V stand-alone mode implementation. This environment had a mixture of App-V clients streaming packages and stand-alone clients, and no one with the App-V client in streaming mode had complained about this arbitrary removal of App-V packages.
The things that jumped out from this explanation were the “MinPackageAge”, the “UnloadLeastRecentlyUnused” and the size of the App-V cache. Although, it was glaring that this behaviour was due to the limited size of the App-V cache, the removal of previous applications automatically was still unacceptable. In a full infrastructure mode, the App-V client would have had the capability of re-streaming the package and users may not have noticed the removal of the application.
My recommendation for a stand-alone implementation will be to change the default behaviour of the App-V client “UnloadLeastRecentlyUsed” policy as below:
The removal of deployed applications should be a conscious decision and not an automatically configured option, as the automatic removal of software could lead to customer dissatisfaction, increased helpdesk calls and administrative burdens.Some school of thought, do advocate increasing the “MinPackageAge” to a very high value. The argument for this is based on the fact that if an application has perhaps not been launched in a long time, the probability of it being used again will be low.
On a side note, the price of hard disk drives have crashed in recent times, so you can also increase the capacity of the disk and also prevent your business from saving files locally.