How to clear App-V Cache

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.

App-V with Java/JRE/JDK

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 inside App-V bubble: Java can also be installed as a local copy with your App-V application. There can be various reasons for doing this:
 a) Application is compatible only with a certain version of Java
 b) Application uses a higher version which is not locally installed.
 c) If Software manager do not want to upgrade the application every time Java gets updated.

In these cases a private copy of Java can be captured with App-V. However, there is a procedure for achieving this.
These steps will be helpful in doing this:

http://packagingguide.blogspot.com.au/2011/11/app-v-for-java-runtime-environment.html

App-V for Royalblue Fidessa application

I want to document the OSD file for Royalblue Fidessa Application here as other capture done alone does not make the virtualized package work. There were certain client customizations which were required and I had to do them in the OSD file.
Here is the OSD file which I used:


<?xml version="1.0" standalone="no"?>

<SOFTPKG GUID="XXXX-XXX-XXXX-XXXX" NAME="Fidessa" VERSION="6.3.9.61056">

<IMPLEMENTATION>

<CODEBASE HREF="FILE://%SFT_SOFTGRIDSERVER%\SCCMData\Royalblue_Fidessa_6.7.0b_VFS_v1.0\Royalblue_Fidessa_6.7.0b_VFS_v1.0.sft" GUID="8XXX5-8XX0-4XX7-AXX1-5171XXXXXA0" PARAMETERS="" FILENAME="%CSIDL_PROGRAM_FILES%\royalblue\fidessa\FtwLaunch.exe" SYSGUARDFILE="Royalblue_Fidessa_6.7.0b_VFS_v1.0\osguard.cp" SIZE="15076089"/>

<VIRTUALENV TERMINATECHILDREN="FALSE">

<POLICIES>

<LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>

</POLICIES>

<REGISTRY>

<REGKEY HIVE="HKLM" KEY="Software\royalblue technologies\Fidessa" NOREDIR="FALSE">

<REGVALUE NAME="ReadWritePath" REGTYPE="REG_SZ">C:\ProgramData\Fidessa\Fidessa</REGVALUE>

</REGKEY>

</REGISTRY>

<ENVLIST/>

</VIRTUALENV>

<WORKINGDIR/>

<VM VALUE="Win32">

<SUBSYSTEM VALUE="windows"/>

</VM>

<OS VALUE="Win2003TS"/>

<OS VALUE="Win2003TS64"/>

<OS VALUE="Win2008R2TS64"/>

<OS VALUE="Win2008TS"/>

<OS VALUE="Win2008TS64"/>

<OS VALUE="Win7"/>

<OS VALUE="Win764"/>

<OS VALUE="WinXP"/>

<OS VALUE="WinXP64"/>

</IMPLEMENTATION>

<DEPENDENCY>

<CLIENTVERSION VERSION="4.6.0.0"/>

<SCRIPT EVENT="LAUNCH" PROTECT="FALSE" TIMING="PRE" WAIT="TRUE" EXTERN="TRUE">

<SCRIPTBODY LANGUAGE="Batch">ECHO OFF \n IF NOT EXIST "C:\ProgramData\Fidessa" MD "C:\ProgramData\Fidessa" \n IF NOT EXIST "C:\ProgramData\Fidessa\Fidessa" MD "C:\ProgramData\Fidessa\Fidessa" \n IF NOT EXIST "C:\ProgramData\Fidessa\Fidessa\install" MD "C:\ProgramData\Fidessa\Fidessa\install" \n IF NOT EXIST "C:\ProgramData\Fidessa\Fidessa\log" MD "C:\ProgramData\Fidessa\Fidessa\log" \n IF NOT EXIST "C:\ProgramData\Fidessa\Fidessa\install\USER.config" cmd.exe /c Echo Y
cacls "C:\ProgramData\Fidessa\Fidessa" /t /e /c /g Users:C \n</SCRIPTBODY>

</SCRIPT>

</DEPENDENCY>

<PACKAGE NAME="Royalblue_Fidessa_6.7.0b_VFS_v1.0"/>

<ABSTRACT>App-V 4.6 SP1</ABSTRACT>

<MGMT_SHORTCUTLIST>

<SHORTCUT LOCATION="%CSIDL_PROGRAMS%\Fidessa\Fidessa" FILENAME="Fidessa.lnk" OVERRIDDEN="TRUE" DISPLAY="Fidessa" ICON="%SFT_MIME_SOURCE%/Royalblue_Fidessa_6.7.0b_VFS_v1.0 Icons/Fidessa 6.3.9.61056.ico"/>


</MGMT_SHORTCUTLIST>

<MGMT_FILEASSOCIATIONS>

<PROGIDLIST/>

<FILEEXTENSIONLIST/>

</MGMT_FILEASSOCIATIONS>

</SOFTPKG>



The Script is the main part and the customization which was required so that the Updates from Fidessa Server are downloaded in local ProgramData directory rather than in bubble. Then this should be able to update the directory inside the bubble, hence made local interaction true. The Directory inside bubble was given write permission. Also all references to C:\ProgramData were deleted in the bubble so that the files are automatically downloaded to the local machine.

Issues while launching and closing of App-V shortcuts

While launching your App-V shortcut, if you notice that the buffering launch on bottom right says 100% but the

launch does not disappear as per normal behaviour then you need to do some modification in your osd file.

This possible is a cause if your application is Java related. You need to modify the Subsystem value in your osd

file.
By default the osd file has this:

<subsystem VALUE = "windows"/>

You need to change this value to

<subsystem VALUE = "console"/>

If you face a similar problem while closing the application or your application does not close completely, then

you need to again tweek your osd file.

By default you have following in your OSD file:

<virtualenv TERMINATECHILDREN="FALSE">

You need to change the value as below:

<virtualenv TERMINATECHILDREN="TRUE">

This will terminate the any child application which is associated with this application and will help to shut

your application down.

Application Virtualization

New technologies, new ways of working is changing our everyday environment.
Application Virtualization is the hot topic these days with Windows 7 coming in picture and organizations across

the globe are integrating App-V in their portfolio of delivery mechanism.

It has been quite some time now that I started work on App-V but did not get a chance to post things on my blog

as my blog was primarily focussed on MSI. I have finally decided to post App-V posts as well on my blog from now

onwards. There are lots of issues we face in everyday work regarding the technology and we try to lookup for

solutions on internet. As a cliche: If someone has already invented the wheel, there is no point re-inventing it.
The sole purpose of my blog is to help others with whatever I learn. I have got numerous solutions for problems

which I have faced and I really thank all those who had posted their solutions on net. This blog is just my way

to contribute back to the society.

All you people out there, please help by commenting, voting, propagating and sharing my blog with your friends

and collegues but with due credit and acknowledgement to the material posted here with my name and blog url as I

still do hold the copyright of the posts here.

Thanks all for your support.

Piyush