This message was deleted.
# citrix-vads
Slackbot
04/28/2022, 2:26 PMThis message was deleted.
b
Balint Oberrauch
04/28/2022, 2:27 PMCVAD 1912 CU4?
j
James Rankin
04/28/2022, 2:27 PMYes, yes it is....
b
Balint Oberrauch
04/28/2022, 2:27 PMsimilar to: When you exit from a Citrix virtual session, one or more of the following issues might occur:
ā¢ The VDA still lists the terminated session and the logonui.exe process. The logonui.exe process can be forcefully terminated.
ā¢ The session appears with a blank username in Citrix Studio.
ā¢ You might not be able to launch further sessions.
j
James Rankin
04/28/2022, 2:28 PMIs that from a KB, or the fixes for CU5?
b
Balint Oberrauch
04/28/2022, 2:28 PMr
Ryan Gallier
04/28/2022, 2:28 PMYeah, CU4 is just a giant failwhale
š 1
š¤·āāļø 1
b
Balint Oberrauch
04/28/2022, 2:28 PMagree at all
r
Ryan Gallier
04/28/2022, 2:29 PMi've blacklisted it in our enviornments
j
James Rankin
04/28/2022, 2:29 PMSounds similar, but not exact - will deffo give it a try
r
Ryan Gallier
04/28/2022, 2:30 PMThere is something in CU4 that is certainly fucking with the logoff/logon cycle... could have other ramifications for sure
š 1
p
Paul Nachfoerg
04/29/2022, 8:42 AMWe advised all our customers to stay away from CU4. CU5 so far is working as expected.
j
James Rankin
04/29/2022, 9:42 AMI still get the same issue after updating the VDA to CU5 š
p
Paul Brown
04/29/2022, 8:58 PMPaul Brown
04/29/2022, 9:00 PMI had to run though this. Seems the only VDA that consistently works without this issue in our environment is 1912CU3. Even the patched 2112 randomly has ghost sessions.
I'm going down the path of re-investigating some of the published work arounds for other issues that we have still in our group policies. One in particular i'm currently re-testing after reverting; CTX225819. Specifically because of this note appended to it.
"If you are using Azure Active Directory (AAD), do not make the registry change described in this article."