File associations on client PCs with RemoteApps
I have setup RemoteApps from a 2008R2 server acting as a Remote Desktop Server.
The client is a charity and volunteers will access the remote apps from their home computers.
I am not clear about how file associations work where the following programs are available as RemoteApps: 1) A specialised "not for profit" database solution which keeps client records and associated documents, which could be Word, Excel, pdf and other types of file. 2) Word 2007 3) Excel 2007.
1. The remote user opens the RemoteApp database and selects a word document. Does this trigger the local or the remote version of Word to open?
2. The user opens the RemoteApp database and also the remoteApp Word 2007. Does this trigger the local or the remote version of Word to open?
3. The remote user opens the RemoteApp database and selects a pdf document. Does this trigger the local version of Adobe Reader to open or is Adobe Reader expected to also be distributed as a RemoteApp?
4. The user opens a locally stored document for which the relevent RemoteApp is running. Does this trigger the local or remote version of the app to open?
Thanks
The client is a charity and volunteers will access the remote apps from their home computers.
I am not clear about how file associations work where the following programs are available as RemoteApps: 1) A specialised "not for profit" database solution which keeps client records and associated documents, which could be Word, Excel, pdf and other types of file. 2) Word 2007 3) Excel 2007.
1. The remote user opens the RemoteApp database and selects a word document. Does this trigger the local or the remote version of Word to open?
2. The user opens the RemoteApp database and also the remoteApp Word 2007. Does this trigger the local or the remote version of Word to open?
3. The remote user opens the RemoteApp database and selects a pdf document. Does this trigger the local version of Adobe Reader to open or is Adobe Reader expected to also be distributed as a RemoteApp?
4. The user opens a locally stored document for which the relevent RemoteApp is running. Does this trigger the local or remote version of the app to open?
Thanks
1) Remote app
2) Remote app
3) It has to be provided as a remote app
4) In normal conditions - local one. If you provided remote app via MSI with extensions support configured - it may open remote one but this is not very good idea because all user documents will open via remote app.
2) Remote app
3) It has to be provided as a remote app
4) In normal conditions - local one. If you provided remote app via MSI with extensions support configured - it may open remote one but this is not very good idea because all user documents will open via remote app.
basically you are working on the remote server with everything.
the desktop shell is not shown but you are still there.
to get an idea.. open a remoteApp and while in it press ctrl+alt+end then click taskmanager..
if you were to swap to virtual Application (app-v) you would run virtual applications on the client and thus allowing more interaction between the client and the application.
I have a situation were the application is client server and the client and the server need to be in the same subnet. so I use remoteapp.
since the files are saved on DFS the users experience issues when they try to open results on the client because the terminal server puts the result on a different server in the DFS and the replication is slower than the user wants.. another example of typical issues with remoteApp.
the desktop shell is not shown but you are still there.
to get an idea.. open a remoteApp and while in it press ctrl+alt+end then click taskmanager..
if you were to swap to virtual Application (app-v) you would run virtual applications on the client and thus allowing more interaction between the client and the application.
I have a situation were the application is client server and the client and the server need to be in the same subnet. so I use remoteapp.
since the files are saved on DFS the users experience issues when they try to open results on the client because the terminal server puts the result on a different server in the DFS and the replication is slower than the user wants.. another example of typical issues with remoteApp.
> to get an idea.. open a remoteApp and while in it press ctrl+alt+end then click taskmanager
Ok it opens locally not remotely
> I have a situation were the application is client server and the client and the server need to be in the same subnet. so I use remoteapp.
And what about TSGW? Subnet is not important in this scenario...
> since the files are saved on DFS the users experience issues when they try to open results on the client because the terminal server puts the result on a different server in the DFS and the replication is slower than the user wants.. another example of typical issues with remoteApp.
RemoteApp saves files immediately because it has DFS in server subnet. With App-V you have to save files trough WAN links. I know it's possible but it will me buch slower.
Ok it opens locally not remotely
> I have a situation were the application is client server and the client and the server need to be in the same subnet. so I use remoteapp.
And what about TSGW? Subnet is not important in this scenario...
> since the files are saved on DFS the users experience issues when they try to open results on the client because the terminal server puts the result on a different server in the DFS and the replication is slower than the user wants.. another example of typical issues with remoteApp.
RemoteApp saves files immediately because it has DFS in server subnet. With App-V you have to save files trough WAN links. I know it's possible but it will me buch slower.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial