MicrosoftAfter upgrading to this version of Fslogix wsearch keeps locking users. User remains in logging off status and "cannot" be logged off traditionally. Only solution is to force-close all processes under the useraccount and closing the handle on the Azure File for the VHD. Once the deadlock occurs, all users on the server will get stuck signing off when attempting to do so untill server reboot.
Environment:
Windows 2016 Session Host fully up to date
FSLogics pointing to an Azure File share for the VHD's and RoamSearch enabled
Classic load balancing/session broker solution with 5 servers all experiencing the issue seemingly random.
Disabling the wsearch service on the machines "fixes" the issue.
Edit: The user session no longer deadlock after the wsearch change but we are seeing sessions disconnecting due to their VHD being detaching. Or their VHD detaching as a result of the bug. When disconnected users can no longer reconnect to that session. Has to be closed and then the user can log on fine again. No trace in the FSLogix Profile/Network/Service logs of any deconnections or attempts to reconnect. Tempted to open up a case with the Microsoft Azure team if it's on the side of the Azure File Share, FSlogics or a Windows Server 2006 issue
2nd Edit: Case opened with MS and the issue is indeed the VHD files that are being detached. May not be a true FSlogix issue but only a secondary effect. Will keep the post active for the time being and keep you posted on what the actual cause was.
Hello,
What do you mean "The user session no longer deadlock after the wsearch change" ?
What change you made against the Wsearch?
I've exactly the same issue, and yes we are still on 2016 Windows Servers.
Using this Fslogix version 2210 hotfix 4 (2.9.8884.27471)
killing/restarting wsearch helps, It happens randomly for users
Would be helpfull if you share what exactly you changed last time.
Thanks in advance !
