This message was deleted.
# citrix-vads
Slackbot
04/22/2022, 7:15 PMThis message was deleted.
s
Salim Hurjuk
04/22/2022, 7:17 PMVDA version
p
Paul Brown
04/22/2022, 7:18 PMSorry. VDA 2112. OS Server 2016
s
Salim Hurjuk
04/22/2022, 7:18 PMThere is ctx article recently published by Citrix
p
Paul Brown
04/22/2022, 7:23 PM👍 1
👍🏾 1
g
Gary
04/22/2022, 7:23 PMs
Salim Hurjuk
04/22/2022, 7:24 PM@Gary shared
p
Paul Brown
04/22/2022, 7:25 PMok. Thanks both. Looks like i've a longer day ahead.
s
Salim Hurjuk
04/22/2022, 7:25 PMOk
p
Paul Brown
04/24/2022, 1:08 AMUpgraded to 2203, which is noted in the CTX article as resolving the problem. It kind of does, i no longer see i bunch of sessions with 5 processes. Now i see users stuck logging off, in director, and all i see on the server is processes, with one process tied to their UID and no way to close it out without rebooting the machine.
Paul Brown
04/24/2022, 10:59 PMSpoke too soon. Seeing the same hung sessions with the 2203 VDA as well as the new issue posted above..
s
Salim Hurjuk
04/24/2022, 11:08 PMCheck your AV scan is in place properly configured
p
Paul Brown
04/25/2022, 1:26 PMAV software is crowdstrike. It does not use traditional exclusions. We've not had any AV exclusion related issues since we implemented Crowdstrike 6+ years ago.
d
Dave Brown
04/25/2022, 3:44 PMI’m still observing this issue with a couple of VM’s running 2203.
Dave Brown
04/25/2022, 3:49 PMIt’s a bit of a mixed bag now, previously with 2109 / 2112 the users session wouldn’t completely logoff correctly. This meant when a user logged back in FSLogix would attempt to create a new session and fail. The user couldn’t successfully connect until the LogonUI.exe was terminated to close the session down. With 2203 we’re seeing users getting disconnected and reconnecting with a new session. If that second session is signed out they can sometimes reconnect to the original session. This is something we need to raise with Citrix support.
p
Paul Brown
04/25/2022, 4:14 PMI'm going to roll back to 1912CU3 i think. 2112 was a shitshow and 2203 if anything is worse. Now i have the VMs being shutdown by the cloud console for for seamingly no reason..
Paul Brown
04/26/2022, 11:23 PM1912CU3 FTW… something else to talk with our account engineer about.
s
Salim Hurjuk
04/27/2022, 6:41 AMVDA2203 - also u are facing this issue?
n
Nick Pylarinos
04/28/2022, 4:11 AMI had experience similar when doing an inplace upgrade of VDA installation - full removal / clean up is the preferred option and installing again from scratch
p
Paul Brown
04/28/2022, 2:18 PM@Salim Hurjuk 2203 was worse.. @Nick Pylarinos we build with applayer, we're not doing an in-place upgrade / downgrade.
So far 1912CU3 is rock solid. i have a small deployment of 2112 with the hotfix i'm watching, and that seems to also be OK. Will be keeping clear of 2203.
s
Salim Hurjuk
04/28/2022, 2:25 PMForme 2203 is working fine.
5 Views