Forum Discussion
User settings and perferences with App Attach
Hi everyone,
I'm currently working in a test environment where I have several msix app attaches.
Everything works fine, except the User settings.
For example the dark mode setting in adobe dc reader, is not saved after ending the user's session in azure.
So after you end the session completely it is like a freshly installed app without any settings saved.
The same thing happens for SAP and other applications.
The User settings are saved, if I install the app locally on my computer.
Is there a way to fix this?
Many Thanks
4 Replies
When I create a package of an app like Adobe Reader, I add the PSF with MfrFixup to the package. This will redirect those changes to the user local profile %localappdata%\packages\{PackageFullName}\Localcache area. In an AVD environment I would then use FsLogix to redirect for roaming purposes. You can either have a general rule to redirec all of %localappdata%\packages (and eat up a lot of disk) or make specific app package rules for the files you need. For most all that is the registry.dat file and a single configuration file for the app.
FSLogix discards these settings due to default exclusions, which is why we added an extra option in AppVentiX to retain them.
User settings in MSIX AppAttach end up saved into the users AppData\Local\Packages area, even if the original application would have saved them under AppData\Roaming or (as in this case) HKCU.
In a non-persistent VM, something has to save that off to a safe place and restore it. Often, customers will use FSLogix for this purpose, however the rules of what to grab for each app will be different when natively installed versus MSIX AppAttach deployment. Other products with similar capabilities exist also, but all need adjustment for existing rules when switching from native to packaged apps.
Hopefully this will help you get it squared away.
Hi NZ463,
I’m having the same problem, did you find any solution?
