Hello Mike,   We can handle file extensions but I'm pretty sure we only do it in one direction from the client machine to the TS. Eg, open a .doc on the client machine and it opens Word (installed on a VDI or Terminal Server) in a seamless window on the client machine.  With this setup, the User is always working on their desktop so there is no need for the file extension to work backwards from the TS to the Client.   Hope that makes sense, I find it works really well with this setup.  If you want more details on how to set this up, look for Application Extensions in the admin guide.  Thanks, Andrew
I'm sure this is something simple that I'm just missing. However, on a vWorkspace (7.6) server (Win Srv 2003 SP2), how can I set it up so it will open up an application on the client computer for particular file types.  For example, AutoCAD - We don't publish AutoCAD on our Terminal Server - if a user double-clicks on an AutoCAD file in the published explorer, can I set it up so it will automatically launch AutoCAD on the client's computer?
Force opening of the local app