what is your guys optinions/experiences with running FSLogix profile containers from a Windows Server Failover Clustering (WSFC)? The only thing from Microsoft is that Continuous Availability should be enabled on the share https://learn.microsoft.com/en-us/azure/azure-netapp-files/enable-continuous-availability-existing-smb

We have been running FSLogix profile containers on WSFC for over a year with no issues. Before FSLogix, we were using file-based Citrix Profile Management. It was not a good choice - slow and required a lot of Citrix policy setup. FSLogix has been a significant improvement. CA was not enabled by default on our setup and we only just enabled it today. After enabling, CA is confirmed as enabled as users log on to their Citrix desktops - no forced reboot or service disruption needed. A few things from our experience: 1. Ours is a regular Failover Cluster File Server (Active/Passive), so CA was definitely needed. If you are already on SOFS (Scale-Out File Server) with the proper storage setup, CA may not be as critical since you get Active/Active redundancy out of the box. 2. Enabling CA was zero-risk for us. No File Server reboot needed and existing sessions were not affected. With 1:1 VDI auto-rebooting on logoff, CA applied naturally on the next login. 3. CA mainly helps you during planned maintenance. For unexpected node failures, Active/Passive WSFC still has its inherent limitations regardless of CA.