File association in App-V 4.6 SP1
The App-DNA report of an application gives below with an Amber compatibility for App-V.
To make FTAs global, you can manually create the FTA within the App-V Client Management Console and specify to \"Apply to all users\", which would store the FTA information in HKLM. Another option is to edit the OSD file by adding '/global' to the syntax in the FTA section of the OSD; i.e. sftmime add type:tst /app \"TEST Application\" /global. The global parameter will specify the FTA to be written to HKEY_LOCAL_MACHINE\\SOFTWARE\\Classes\\ (Everyone). To add multiple FTAs you will need to create a link to the application. To do this create the first FTA; i.e. sftmime ADD TYPE:LOC /APP \"MyApp 1\" /DESCRIPTION POC-FILE. You will then need to link additional FTAs to the same application using the syntax (Softgrid.[type].File); i.e. sftime ADD TYPE:LIN /PROGID SoftGrid.LOC.File.
I tried searching a lot and it seems that this was the thing till App-V 4.5 and it is no more there in App-V 4.6 SP1. Not sure though but after reading a lot of posts and forums I could find only this. Could anyone please help me by telling how to resolve this issue in App-V 4.6 SP1.
The File association is for only current user and I want it to be per machine.
Thanks.
Answers (3)
4.6 SP1 does not require this remediation it is already there.
Did you try editing OSD file directly or through GUI as suggessted by AppDNA
Comments:
-
As I mentioned it is not there in the OSD file. - piyushnasa 12 years ago
-
Are you using latest AppDNA? - jagadeish 12 years ago
-
If Yes then Do you think AppDNA people have to update their database???? - jagadeish 12 years ago
Just starting to play with appv, but from a bit that I have read, can't you install the app per machine during sequencing, and thus shortcuts are captured as per machine?
I read from one blog that he litterally re-packages the app with customizations and THEN sequences... Would this work for you?
I just sequenced it any how and with RTSP protocol and deployed. It is working fine for File Association for all users. So I think 4.6 SP1 does not require this remediation it is already there.