Forum Discussion
Default apps in WVD
We are dealing with an issue with WVD Remote Apps where we cannot set or maintain default apps for users. For instance, we want the default browser to be Chrome, mail to be OutLook, .doc files to op...
DavidBelanger
Microsoft
MicrosoftHi stevenzelenko, am I correct that you want files on the remote server to open with the right app as defined on that remote server?
Or are you trying to associate local files to open in a remote app?
David
Essentially correct. We want the server apps to be associated with the files in user's FSLogix profile. So if a user has a pdf file in OneDrive or in their documents folder, it should associate with Reader.
So far we have tried an associations xml file via GPO as well as some registry settings. We'd like chrome for browser, outlook for mail, word for doc and docx, etc. Every session all apps return to Windows 10 default. So for instance, if we click a URL it will open in edge, a mailto: within outlook will prompt which app to open with and will always default to the windows mail client. Even if the user selects outlook and check to remember this app, if they log off and back in, that gets reset. We are forcing users to one drive and opening files like PDFs and .docs seem to work ok but PDF will always prompt the user to choose a default application for PDFs. It's like it doesn't honor the GPO or registry and will always default to using Windows 10 default apps.
We are using remote apps only and the profiles are handled with FSLogix containers.
stevenzelenko Did you find a solution to this? We have the exact same problem. The XML file through GPO works fine for full desktops, but looks like its ignored with RemoteApps.
- Has a solution been found for the inability to set default apps using the "Set Default File Associations" XML with GPO in a WVD setup utilizing only RemoteApps?
Mtollex70. We have just experienced the same issue. if we setup a user without launching full desktop the default app associations don't apply but if we log in as full desktop then convert back to remote app, default associations start working. has anyone else experienced this or know of a fix?
Same here. Don't confuse the issue with trying to associate local files with remote apps. That's not what the poster is asking.
Poster has a situation where he needs to have a Remote App start from within another Remote App. E.g. the primary Remote App has an "Export to PDF" button, so you expect the file to exported, saved somewhere in a temp directory and then to be opened by you preferred PDF reader. Instead, it asks the user with which application the file should be opened. This is annoying, especially in some cases where the required association is not standard and the user has to go browsing the file system to choose the executable file of the secondary application.
His problem (and mine and many others) is that the default association xml file that you can set through Group Policies, has no effect if you open the Remote App only. It does work when connecting to a full desktop session and after having logged on once to a full desktop session, it also works for the Remote App.
