sade055

This has become my favorite site today because one of the issue which I was facing in App-V while testing was because the App-V cache was not getting cleared. I used one of the method used here and it worked for me. I want to share this link with all and want to bookmark it for myself for future reference. http://esense.be/33/2010/04/15/softgrid-clear-the-appv-cache/ In Summary, these are a few good options to start with: First, get a list of all AppV applications: sftmime query obj:app /short Remove all applications from the cache: sftmime.exe remove obj:app /global /complete Remove a specific application from the cache: sftmime.exe remove app:”applicationName” /complete Hope your issues are solved with this as well.

It is very critical to understand how to handle installation of Java related applications in App-V environment. While some are of the view that the application should be installed along with Java in the same bubble while some say that the Java version installed on the base machine can be used. Here is how you can do both of these in a proper way: 1) Java installed locally on the machine: If Java is locally installed on the machine and you capture the App-V application, then you will see a hard coded entry in the registry. This basically points the App-V application to look for Java in this local machine location. If you upgrade your Java version from say 1.6.21 to 1.6.24, then you do not need to worry, however, if you do a major upgrade from 1.6.21 to 1.7.xx then you need to upgrade your App-V Application as well. You need to maintain the software library for all these applications and then upgrade them as part of Java Upgrade in the organization. 2) Java is installed as local copy in...