We have completely removed FSLogix as its just too unstable and the workaround of doing the reboot is not acceptable when you have 40 or 50 users on an RDS box
FsLogix - Unclean logoff causing locked files until server reboot
Problem is described by M4deman under unclean-logoff-causing-locked-files-until-server-reboot
It seems to have something to do with the 2009 version.
The latest version of FSLogix is installed whats-new
Description
After a user logoff, the "System" Process (PID 4) locks the following folders:
C:\Users\local_username\AppData\Local\Microsoft\Credentials
C:\Users\local_username\AppData\Roaming\Microsoft\Credentials
The user is completely logged of, according to Task Manager.
In the FSLogix Profile Log file I can see the following:
[07:53:55.601][tid:00000c90.0000ce44][ERROR:00000020] Delete profile failed for sid S-1-5-21-3364776539-3721753400-1968955100-1179, Cleaning up manually. (Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.)
The last sentence means that the process cannot access the file, because another process already uses it.
Also the whole "local_username" folder cannot be deleted:
[08:23:15.479][tid:00000c90.0000bcc4][WARN: 00000005] Failed to delete C:\Users\local_usename (Access is denied)
Access Denied
Does someone have any info on this behaviour?
Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Client for IT Pros | User experience | FSLogix
107 answers
Sort by: Most helpful
-
SMB Solutions Cloud Services Pty Ltd 31 Reputation points
2021-09-13T07:15:50.647+00:00 -
Андрей Михалевский 3,461 Reputation points
2021-09-13T07:33:50.367+00:00 @SMB Solutions Cloud Services Pty Ltd And what conclusion does Microsoft make in your application?
-
Micheal Thompson 1 Reputation point
2021-09-13T07:37:09.63+00:00 I was thinking of writing a script to help mitigate this issue.
It would be configured as a "task scheduled" script on Citrix VDA machines, and would follow the following steps.
- Iterate over current online/disconnected users on the VDA machine and store them into an array.
- Compare current online/disconnected user's profiles created under C:\Users against users in that array, if any exist that aren't actually online we know they are broken.
- After determining which users are broken, we can dismount their VHDX, and use handle to close any open files/folders, and delete the user profiles still left behind.
I'm not sure how practical this is, but if Microsoft isn't going to be looking at fixing this issue anytime soon, it's time we either look for an alternative solution or try and put measures in place to mitigate this?
Does anyone see any potential reasons why a script of this nature wouldn't work?
-
CitrixMember 6 Reputation points
2021-09-13T07:54:18.67+00:00 Im agree that help MS Support has given according to this Fslogix problem, is very bad.
But the 2105 preview version did solve our problem, we havent got accept from customer for upgrade to public version of 2105 yet.
Did also experience this problem on another customer, but a simple upgrade to the public version of 2105 version, did solve the problem. (here we experienced fslogix service go nuts, so the VDA lost connection and sense.May some of you take a full screenshot of your GPO with Fslogix setting?
From my perspective, I would say MS has fixed the problem with 2105 release.
-
CitrixMember 6 Reputation points
2021-09-13T08:01:29.623+00:00 What kind of Antivirus solution do people run here? Trend or Symantec? Defender?
Also try extend GPO refresh values to run refresh once a day or something, see if that may help?