Forum Discussion
The FSLogix 2201 Public Preview is now available
SteveDMSFT We notice that we still have some sessions that do not clean up properly.
The command 'frx.exe list-redirects' shows no open redirects and the .vhdx is dismounted properly.
However, there is "C:\Users\<username>" and "C:\Users\local_<username>" after the user logs of. The "local_<username>" we can remove; but the "C:\Users\<username>" will stay locked untill a reboot.
If the user would logon to the same RDS server again, they will get a "C:\Users\<username>.FSL0" and "C:\Users\local_|<username>.FSL0"; but that causes issues with Outlook OST cache that still excepts the path without .FSL0.
The following rekeys are set:
- HKLM\SYSTEM\CurrentControlSet\Services\FRXDRVVT\Instances\frxdrvvt\Altitude = "138010"
- HKLM\SOFTWARE\FSLogix\Apps\CleanupInvalid Sessions = dword:1
Revent logs:
==
[08:24:59.681][tid:00000dbc.00000c9c][INFO] Unregister app notifications
[08:24:59.790][tid:00000dbc.00000c9c][INFO] Accessing network as user object
[08:24:59.790][tid:00000dbc.00000c9c][INFO] Adjusting symlinks
[08:24:59.837][tid:00000dbc.00000c9c][INFO] Status set to 1: Cannot load user's profile
[08:24:59.837][tid:00000dbc.00000c9c][INFO] ErrorCode set to 1064 - Message: An exception occurred in the service when handling the control request.
[08:24:59.837][tid:00000dbc.00000c9c][ERROR:00000428] invalid string position (Uitzondering in de service bij het verwerken van de besturingsopdracht.)
[08:24:59.853][tid:00000dbc.00000c9c][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\ShutdownOnUserLogoff. Using default: 0
[08:24:59.853][tid:00000dbc.00000c9c][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\RebootOnUserLogoff. Using default: 0
[08:24:59.853][tid:00000dbc.00000c9c][ERROR:00000428] UnloadProfile failed. Version: 2.9.8048.43478. User: Username. SID: S-1-5-21-xxxxxxxxxxxxxx. SessionId: 2. FrxStatus: 1064 (Uitzondering in de service bij het verwerken van de besturingsopdracht.)
[08:24:59.853][tid:00000dbc.00000c9c][INFO] unloadProfile time: 172 milliseconds
Cheers,
Peter
- SteveDMSFTFeb 10, 2022
Microsoft
PdfPeet, have you opened a support case? If not, could you please do so? That's the best way for us to collect logs and triage the issue. - stefanoscloudFeb 03, 2022Copper Contributor
I have already mentioned this behavior with _local profile not being properly deleted occasionally. As I mentioned in my previous comment, this case was open as Microsoft Technical Support case and got escalated all the way to even examining OS system dump but no solution was found even though it was verified as a bug. The case was finally closed without a resolution. This issue is happening from previous versions for over 1 year now and there is still no official response from Microsoft on why the identified bug has not been resolved yet. In my article (https://stefanos.cloud/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/) I provide a detailed analysis of the issue and of the troubleshooting steps performed in coordination with the FsLogix support team and product group. Numerous FsLogix users with same issue have contacted me from various countries asking if there any further update I can share with them.
Again, this is affecting many customers and it is very important to have a final resolution. We need your feedback on this, thank you.
- PdfPeetFeb 05, 2022Copper Contributor
For now I've scheduled a simple script that runs every 30 minutes during the nightly hours to:
- Check if there are any users still logged on through RDP
- If not, check if there are any local_ of profile folders still there that shouldn't
- If so:
- Run an "frx.exe list-redirects" and cleanup where needed (doesn't seem to be needed anymore since the 2201 release)
- Run an "frx.exe stop-agent" & "frx.exe start-agent" (this removes the locks from the profile folders; without having to reboot the server)
- Do additional cleaning
- Registry: ProfileList and ProfileServices\References
- Profile folder: take ownership and remove "local_<usersname>" and "<username>" folders
It's not ideal, but it keeps servers clean.
- kesslersebFeb 09, 2022Copper Contributor
Hey,
can you share the script?
That would be great! 🙂
We have a new installation for a customer that is currently working very well.
In another installation there is the problem that the domain account "Administrator" has a black screen after login. Can anyone confirm this problem?