RemoteApp: Couldn't open this program of file

Question

We have MS Windows 2016 RDS deployment with some published RemoteApps. And everything works well except one thing: file type associations works only when users open their files from UNC fileshares, i.e. \fileserver\fileshare\somefolder\file.ext.
But there is no luck if users try to open files from local disk on their client PCs like C:\somefolder\file.ext or users have that UNC fileshare mapped as network drive, i.e. H:\somefolder\file.ext.
In that case it is always errors like "Couldn't open this program of file. Either there was a problem with %ProgramName% or file you're trying to open couldn't be accessed."

PS: Users connect to the RDS farm through "RemoteApp and Desktop Connections" in the control panel.

Answer 1

Hi,
Check if you have set file type associations configuration via RemoteApp Properties. Some information in the link below:
https://community.spiceworks.com/topic/2084569-remoteapp-and-local-files
Also I suggest that if you have enabled the setting below in group policy.
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\
Open local files with published applications
https://social.technet.microsoft.com/Forums/en-US/04cc3a3e-1041-4c36-ad0e-1f9f3191ea02/open-local-files-with-published-applications?forum=winserverTS
Best Regards,
Carl

Answer 2

Thanks, Carl, we have enabled this setting

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Do not allow drive redirection = Disabled

and it did the trick.

As for setting

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\
Open local files with published applications

I really doubt it exists.

Answer 3

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Do not allow drive redirection = Disabled

Fixed it for me as well.

Note: It was not obvious that this is a server-side setting. Of course I applied it to the workstations during my first attempts. I had a feeling Remote Desktop Session Host meant it should be on the server, but I ignored my gut and wasted a ton of time trying other things.