sade055

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_ALLOWE...

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: &ltsubsystem VALUE = "windows"/&gt You need to change this value to &ltsubsystem VALUE = "console"/&gt 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: &ltvirtualenv TERMINATECHILDREN="FALSE"&gt You need to change the value as below: &ltvirtualenv TERMINATECHILDREN="TRUE"&gt This will terminate the any child application which is associated with this application and will help to shut your application down.