New Azure Solutions Center documentation on Microsoft FSLogix for the enterprise - NOW available!
This article provides insights on designing, sizing, and implementing a Microsoft FSLogix Profile Container solution for large enterprises, as well as shows how to avoid performance problems in production. This article is an extension of the Windows Virtual Desktop (WVD) at an earlier released Windows Virtual Desktop at enterprise scale article. We cover the following topics: FSLogix filter driver architecture - explained Profile Container and Office Container Multiple profile connections Performance requirements Storage options for FSLogix profile containers General Best practices Azure Files best practices Azure NetApp Files best practices Storage permissions Storage exclusions Antivirus exclusions When to use Cloud Cache Disaster recovery Backup and Restore Maintenance Best practice settings for enterprises There has been done some hard work behind the scenes to get this document ready and online. By WVD Engineering, GBB, Fast Track, Azure CAT - thanks to everyone involved. FSLogix Best Practices shortlink: aka.ms/fslogixbestpractices Windows Virtual Desktop Best Practices shortlink: aka.ms/wvdbestpractices Read the full contribution here: https://docs.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop-fslogixAnnouncing FSLogix release changes and Windows multi-session updates in Azure Marketplace
Starting on August 8th, 2023 (patch Tuesday), Windows multi-session images will come with the latest version of FSLogix already installed. This means that you can skip the hassle of installing or updating FSLogix on your virtual machines and enjoy its amazing features right away.Announcing FSLogix 2201 hotfix 1 (2.9.8171.14983) has been released!
FSLogix Release Notes - FSLogix | Microsoft Docs Summary This update for FSLogix 2201 includes fixes to Cloud Cache and container redirection processes. No new features are included with this update. Changes IMPORTANT This is a **hotfix** for FSLogix 2201 (2.9.8111.53415). If you are using Cloud Cache or have experienced intermittent system crashes as a result of FSLogix, it is recommended to install this update. Resolved an issue with Cloud Cache where disk read / write blocking could potentially create a deadlock to the disk and cause the Virtual Machine to become unresponsive. Resolved an issue that would cause a Virtual Machine to crash while removing profile redirections during the sign out process. File Information Download the following package: Download FSLogix 2201 hotfix 1 (2.9.8171.14983)
FSlogix Profile Disconnects
Hi, Just wondering has seen this issue with their AVD instances and FSlogix in regards to profile container disconnects. We have version 3.25.822.19044 and my theory is that computers that go into sleep mode (due to power timeouts) are not cleanly triggering the disconnect procedure for the container to be cleanly disconnected. We have noticed this by the users .VHDX.metadata file not deleting on their log off. It's also not releasing the Handles and Leases for their containers, making them sign in with a temp profile if they try again. We are just running a standard regedit profile setup based on this page, https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples Just seeing if anyone else has any fixes in place? Or is this a known issue. Thanks Josh.
Error removing Rule at logoff
Hello folks. during user logoff Fslogix is trying to remove some rules but get an exception [ERROR:80070490] Error removing Rule: C:\Users\username\AppData\Local\CrashDumps (Element not found.) As a result it removes "users profile" and "local_username" folder correctly with no issues, but sends Error to the logs. It's spamming the logs because it will put error one every excluded folder from redirection. We don't use any FSLogixAppsRuleEditor or something else, checked by ."\frx.exe list-rules -verbose" it returns - "No rules" The redections.xml looks like [...] <Exclude Copy="0">AppData\Local\CrashDumps</Exclude> [...] Is this an known issue ? Thinking it came around with 3.25.202.4223. Thx Jens
Old file server still present in registry on user profiles
We are running FSLogix 2.9.8884.27471 on Server 2022. Our domain controllers are all Server 2022. We just migrated to a new file server. The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server. We only changed/migrated the general file server used for general file storage. After we powered off the old file server, Citrix users complained of "slowness" when using File Explorer. We discovered that there are a bunch of references to the old file server in each user's FSLogix profile registry. If we mount the FSLogix profile, when a user is logged out, and delete the references from a user's profile registry, the "slowness" issues with File Explorer, are resolved. The registry entries that seem to be present in each user's profile are located in the following: HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints 2 (there are a couple mount points still present for the old file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) When we delete the "Favorites" entries, we find that after a user logs in/out, the "Favorites" entry updates properly to the new file server path. We can also remedy the File Explorer "slowness" by simply powering on the old file server. Again, all of the sharing on the old file server has been disabled. So it seems like as long as a user can "ping" the old file server, then that's all FSLogix needs to ensure that File Explorer works. This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles. Instead of either leaving on the old file server powered on, or manually editing the registry in each user's profile, is there a way to remove (or update) these registry entries that point to the old file server?
Windows Server 2022 and FSLogix profile roaming problems
Hello! Recently I've been tasked with enabling profile roaming between two Windows Server 2022 hosts, which are added to the same collection. Both of them are hosting internal developed app. After enabling fslogix on one of them, I've encountered some errors, users getting blocked from logging in. Those are the errors users are getting when trying to log in into the host that uses FSlogix: 1) Failed to acquire mutex for user: EXAMPLE-USER 2) Failed to acquired cleanup session registry lock for user EXAMPLE-USER (SID=S-1-5-21-1715567821-2139871995-725345543-32785) (Elapsed time: 60000) (The wait operation timed out.) User is from different domain that has Forest trust type set to Transitive. We have multiple domains accessing this VM and users from all of them are having the same problems when fslogix enabled on it. User has access to both VM and Azure Storage Account File share when profiles are being saved (both SMB and on Azure portal access) FSLogix policy is set like this: Policy Setting Comment Delete local profile when FSLogix Profile should apply Enabled Policy Enabled Enabled Policy Setting Comment Set Outlook cached mode on successful container attach Disabled Size in MBs Enabled Size in MBs 10000 Policy Setting Comment VHD location Enabled VHD location \\<example>.file.core.windows.net\profiles FSLogix/Profile Containers/Advancedhide Policy Setting Comment Keep local folder after user logs out Disabled Locked VHD retry count Enabled Locked VHD retry count 3 Policy Setting Comment Locked VHD retry interval Enabled Locked VHD retry interval 5 Policy Setting Comment Prevent login with failure Enabled Policy Setting Comment Prevent login with temporary profile Enabled Policy Setting Comment Redirect temporary file folders to local computer Enabled Redirect TEMP, TMP and INetCache to local drive Policy Setting Comment Remove Orphaned OST Files On Logoff Enabled FSLogix/Profile Containers/Container and Directory Naminghide Policy Setting Comment Swap directory name components Enabled Policy Setting Comment Virtual disk type Enabled VHDX Any ideas how to solve it or what might have caused it?FSLogix Customer Experience Survey is live!
All... I am pleased to announce our Customer Experience Survey is now live! FSLogix is looking for feedback from our customers and community to help shape the current and future iterations of the product. FSLogix is widely used across Azure Virtual Desktop, Azure, and On-Premises deployments and we want to ensure we continue to deliver fixes, enhancements and features that are meaningful across these segments. Thank you and we look forward to your responses!
