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.
This Blog is for all people working or related to the MSI and App-V. There are lots of issues we face in everyday work regarding the technology. The sole purpose of my blog is to help others with whatever I learn. All you people out there, please help by commenting, voting, propagating and sharing my blog with your friends and colleagues 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.
Thursday, December 08, 2011
Wednesday, December 07, 2011
Definition of Application Re-Packaging
I have been often asked about the proper definition of Application Re-Packaging. This is the best I could find:
Application Re-packaging solution offers customized application configuration and repackaging of third-party or internally-developed applications to standardize the installation routine, reduce deployment errors, and minimize support costs.
Application Re-packaging solution offers customized application configuration and repackaging of third-party or internally-developed applications to standardize the installation routine, reduce deployment errors, and minimize support costs.
Subscribe to:
Posts (Atom)