This message was deleted.
# citrix-vad
s
This message was deleted.
👍 11
✅ 1
r
Yeah, already ran into this. There was a thread on this earlier. Most of us rolled back to CU3...
j
Now you can go back to CU4
r
waits for CU5
👍 2
😄
j
lol
s
I literally just ran into this issue this morning... You saved me a headache @Jarian Gibson
j
@Rody Kossen saved you. I just posted it.
s
Thanks @Rody Kossen 🙂
r
Your welcome! I couldn't do a ping to everyone so Jarian rang that bell for me haha
🙌 3
🙌🏻 1
This issue, iirc
r
Yes, same one indeed. There were a few threads here as well
r
QA is GA 🙄
😂 1
s
Hot fix didn't work, rolling back to CU3...
r
Did you update your master image or how did you deploy it? It needs an reboot
s
Updated the master image and pushed to the MCS catalog...
r
Did you check that it used the new dll?
o
VDA cleanup needed?
s
Thanks for making this an alert, that is helpful.
s
Looks like my problem isn't related to this CU4 issue, rolled back to CU3 and still doesn't work... False alarm from me...
s
Careful, even with this 2012 still has the Ben Splittgerber noted MAC disconnect issue, as well as the Tpoppelgarrd noted fslogix profile lock issue that windows KB5007266\1-2022 was suppose to fix but has shown in dif environments to not be fixed.
r
@stormlight or @Thomas Poppelgaard: Is the FSLogix not a Microsoft issue? Or is it only reproducable with 2112?
r
We build a new environment on Server 2016/2019 with VDA 2112, FSLOGIX 2109, Crowdstrike and WEM Cloud. Initially it worked okay (limited use and low user load) but as the load increased we saw many failed connections, server lock ups, profile locks, etc... We made sure the Microsoft patch KB5010196 was applied as well as the Citrix hotfix. Nothing worked. We tried Cloud Cache, not cloud cache. It was a miserable few weeks. We ended up moving back to 2106 and now the environment is working vey well again. Not sure but 2112 didn't like something.
r
That sounds like my story but we are on 1912... We have Windows Server 2016 VDA, we have gone thru a full review with Citrix they made some recommendations including upgrading to CU4... yup and is all kinds of issues. Disconnects, lock ups.. miserable experience for everyone..
m
I just wanted to add, that 2112 with the public hotfix also still doesn't work for uns. We have two affected environments: A random user gets disconnected from the farm, for an yet unknown reason. As he tries to reconnect, he can't reconnect / create a new session, because of the "FSlogix error" disk in use. In Studio and Director there is no session for the user. By asking the Fileserver, where the VHDX lock comes from, I can find the VDA where the VHDX is still mounted. There I found a disconnected session in the Task Manager. Opposed to the other cases I spectated, it was a "complete" session. By that I mean, that each program was still running. Like Outlook and Edge. Normally I only find like ~6 processes in those sessions. I started a graceful logoff from Task manager and the user could login once again. Sadly I have no CDF traces, yet, but I will take that ticket as an excuse to implement it. tl;dr: Random unwanted disconnect, Session still exists, but Citrix doesn't know about it, reconnect impossible, as VHDX is locked.