02-07-2020 07:47 PM
02-07-2020 07:47 PM
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 open in Word, PDFs to open in Reader and the settings are not sticking. We've tried to apply GPO using the app associations .xml file and it doesn't work. We even went as far as writing policy to modify registry for all app extensions and that doesn't work. NOTE: we are using only remote apps and not a full desktop. This is really the last thing that we can't get to work and are stumped. Any help would be appreciated and would like to know if others have experienced this.
A little more about the setup. We have deployed 2 session hosts with FSLogix containers to host our profiles on a file share.
02-11-2020 10:58 AM
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.
07-03-2020 09:27 AM
@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?