FSLogix
2 TopicsRoaming appdata using Fslogix
Hi, We are packaging applications to MSIX and deploying them in our Azure Virtual Desktop environment where we are using Fslogix for user profile roaming. From version 2210 (2.9.8361.52326) of Fslogix, the folders below are no longer being roamed: AppData\Local\Packages\*\AC AppData\Local\Packages\*\SystemAppData AppData\Local\Packages\*\LocalCache AppData\Local\Packages\*\TempState AppData\Local\Packages\*\AppData (https://learn.microsoft.com/en-us/fslogix/troubleshooting-appx-issues) Many of our apps are saving user preferences and settings to these folders. The applications are third party made apps that we do not have the code for. This is causing issues for us as the user preferences/settings are not maintained after the logoff process. I have looked for ways around this, but have not been able to find any solutions so far. Has anyone else encountered this issue or does anyone have any suggestions? Thank you1.4KViews0likes3CommentsMSIX AppAttach FSLogix Profile issue between packaged app versions
Has anyone experienced the following scenario: Application (PowerBI) packaged as MSIX and delivered via App Attach: Package Name: PowerBI-2.104.702.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.702.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) End user can access application, app profile data is retained to FSLogix and works as expected between sessions, retaining app settings etc. Now, a new version is required: Package Name: PowerBI-2.104.941.0.MSIX Delivered via App Attach to AVD FSLogix Profile created, and Application user data stored path: \\CLIENTNAME.file.core.windows.net\fslogix\$GUID_username%\Profile_User_name.vhdx\ Profile\AppData\Local\Packages\PowerBI-2.104.941.0\LocalCache\Local\Microsoft\Power BI Desktop (or similar) So, between the different versions of the same Application, I am not able to access the roaming profile application data from the original package, forcing my users to have to re-configure the application afresh for the new release. I could just repackage the new version using the EXACT SAME name, but this makes it impossible to differentiate between packages, and also does not meet any version control naming conventions. Has anyone come across this before, and has anyone discovered a viable solution? Thanks NickSolved2.3KViews0likes2Comments