File associations for local apps.

Is it possible to configure the 2x Applications Server (or Client) so that when a user attempts to open a foreign file through a published application, the 2x Client will associate that file extension with an application on the local client (users PC)?

For example, let's say I publish Outlook for a user. He opens an email and notices that the email has an attachment, which is a MSFT Word document (.doc). The 2x server does not have MSFT Word (or the Office suite) installed, however the user does have MSFT Word installed locally on his PC. When he attempts to open the .doc file from his email, the 2x Client will redirect the open command back to his locally installed version of Word.

Is this doable? I've scoured through the forums and haven't see anyone referencing this.

Thanks.

 

Bump

 

Hi,
Currently it is not supported.

Tom

 

Ok, that's understood. However, with all the people publishing an email client, I can't believe they haven't run into this same problem and found a work around?

I'm not publishing an email client to my users, but my issue posses the same problem. I have an application that Accounting uses and they attach .pdf, .doc and .xls files within the system. As of right now, I'm going to have to install and publish Word, Excel and Adobe Reader.

Anyone have a better idea on how to get around this without publishing these additional apps to all my users?

 

File association is only working the opposite

IE local word document, no word installed, run published word and display/edit document

The point of publishing applications is to make the admins life easier, ie install office suite once rather than on every workstation.

 

This is only available for mailto and url links, please check the terminal server properties and look for url/mail redirection. Clients needs to have this enabled as well

 

Hi,
Although it is not possible currently, it can be a good feature of 2X AppServer in such scenarios where users want to run CPU intensive applications like AutoCAD etc.
Simple scenario:
Publish AutoCAD.
Client access the published app.
Local AutoCAD runs instead of the server side AutoCAD.

Tom