Is it possible to associate specific file extensions on client machine with virtual application from host? Thanks, Dave

For this example let's assume that there are some .docx files on the client machine and MS Office Word installed on the server. The goal is to open the local .docx file with the server winword.exe with a double click using the association mechanism. It can be done in the following steps:

• on the server: enable client filesystem mapping (Preferences/Options/uncheck 'Disable filesystem mapping' - setting this option requires Winflector server restart)

• on the server: publish the winword.exe application

• on the client: create a batch file, for example cword.bat with the following content:

set P=%~pnx1

C:\Winflector3741\client\wfc.exe -addr=10.1.18.72 C:\ "C:\Program Files\Microsoft Office\Office15\Winword.exe" "C:\WFMOUNT\C%P%"

The call above assumes that Winflector client is installed in c:\winflector3741 directory on the client computer, and winword.exe program is installed in C:\Program Files\Microsoft Office\Office15 directory on the server computer with IP address is 10.1.18.72.

• on the client: create an association between .docx extension and cword.bat (set cword.bat as a file which should be used to open .docx files) - it is system dependent how to create an association

That's it - now after double click on a .docx file the cword.bat will be called. The .docx file name will be passed as a parameter. For simplicity the script above asumes that the file is located on the local client drive C:. In order to support any drive the script must be a little bit complicated:

set DR=%~d1

set DL=%DR:~0,1%

set P=%~pnx1

C:\Winflector3741\client\wfc.exe -addr=10.1.18.72 C:\ "C:\Program Files\Microsoft Office\Office15\Winword.exe" "C:\WFMOUNT\%DL%%P%"

This script can be further enhanced to support network paths, include Winflector user specification or detect incorrect file name.