Hi Nathan Jones,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
To provide a more comprehensive solution to the issue you are experiencing with FSLogix in your AVD environment, I would need some additional information. Here are some details that would be helpful:
- What version of Windows are you using in your AVD environment? (e.g., Windows 10, Windows 11, etc.)
- What version of FSLogix are you using? (e.g., FSLogix 2.x, FSLogix 3.x, etc.)
Regarding your cloud storage solution for FSLogix, are you using:
- Azure Files?
- Azure NetApp Files (ANF)?
- Another cloud storage solution (please specify)? Are you using any third-party tools or software in your AVD environment that may be interacting with FSLogix?
https://learn.microsoft.com/en-us/fslogix/concepts-container-storage-options
In your Azure VD environment, you don't have a traditional "File Server" like in a typical on-premises setup, the file server could be:
- The RDS server itself, which hosts the user's data and FSLogix VHDX files.
- A separate server or storage solution, such as Azure Files or Azure NetApp Files (ANF), that stores the user's data and FSLogix VHDX files. To determine the correct location, you should identify where the FSL VHDX files are stored in your AVD environment. Once you've identified the correct server or storage solution, you can adapt the steps to unlock the stuck FSL VHDX file.
The most common issues and solutions are listed here: https://learn.microsoft.com/en-us/fslogix/troubleshooting-old-temp-local-profiles