Multiple users discussed a possible issue with Real-time dx and file handles not being released by 2022 servers in a Citrix environment. A similar issue was mentioned where the shell bridge process was hanging onto profiles and causing issues for users. The environment consists of Citrix, FSLogix, and Azure VMs with Windows 2022 Server. The problem is still being investigated and there is a need for visibility to see what is preventing the release of file handles.
Read the entire ‘Troubleshooting FSLogix in a Citrix Environment’ thread below:
Hey everyone.
Is it possible with Real-time dx to see file handles that are still open for users that are logged off (we are having an issue where it seems the fslogix containers are not being released correctly by 2022 servers)?
Or in the FSLogix containers view I could see the drives there that aren’t fully released?
I’m trying to see if I can use FSLogix to troubleshoot this weird issue. Wondering if it is Shellbridge that is causing the problems.
I’ve seen a similar issue like your are describing . It is definitely the shell bridge process hanging on to those profiles and not fully letting go, which then causes a profile issue with a user who is trying to log in , saying “your disk is in use by another computer”. Is this a Citrix environment you’re talking about ?
Yessir. Citrix, FSLogix, Azure VMs with Windows 2022 Server (we just swapped from 2016). Servers that hold the profiles are Windows 2022 servers too.
I just need visibility to see what seems to not be letting go of the file handles.
Continue reading and comment on the thread ‘Troubleshooting FSLogix in a Citrix Environment’. Not a member? Join Here!
Categories: All Archives