Forum Discussion
FSLogix Profile does not completely unload after a User logoff
The symptoms of the problem: a) User attempts to login b) Temp profile is created because FSLogfix could not load the profile c) User logs off d) Task Manager still shows a stuck process under t...
Update as of [05/06/21]:
It appears that the previous instance fixed itself. but ....
I have the exact reoccurrence [05/06/21]. The symptoms are exactly the same.
New possible Cuase;
- The FSLogix profile is an SMB share on a cluster volume. The Cluster Manager is showing some issues that I have yet to understand, and fix.
more info to follow as I learn more of what is going on.
--Action plan: get away from Cluster and move to Azure Storage account with AzureFile
It appears that the previous instance fixed itself. but ....
I have the exact reoccurrence [05/06/21]. The symptoms are exactly the same.
New possible Cuase;
- The FSLogix profile is an SMB share on a cluster volume. The Cluster Manager is showing some issues that I have yet to understand, and fix.
more info to follow as I learn more of what is going on.
--Action plan: get away from Cluster and move to Azure Storage account with AzureFile
Did moving to Azure Files resolve your locked profile issues?
I have a few different instances around using both methods and get significantly less issues with the Azure files method than on a drive attached to a server, personally I think this maybe due to bandwidth limits of the VM that hosts the profiles and the bandwidth limits of Azure Files are generally a lot better and also there are less factors with this.
That being said the latest FSLogix update claims to resolve yet more of these issues and after doing the update before this one i have seen less issues still so it maybe you want to look at updating fslogix's on all AVD's first located here Microsoft/FSLogix Updates