This message was deleted.
# citrix-vad
s
This message was deleted.
๐Ÿ‘ 3
k
2203 is just around the corner ๐Ÿ˜‰
n
Yes, but I have to upgrade to CU4 or CU5 before moving to that one. ๐Ÿ˜ž
w
I see PVS 1912 CU5 is also available
m
Is 2203 base of LTSR or 2112 + fix?
r
Yes, from how it was explained to me, and according to the latest blog they stated is based from 2112 experince.
n
Yeah, I specifically asked that question, and was told it would be 2112 with all available fixes included since then.
a
CU5 has fixed the session disconnect/reconect bug CU4 introduced on Server 2019 for a client.
r
Nice
m
I want to hop on here and say that at least at my customers 2112 + public hotfix 1 didn't solve anything. I still have to extinguish fires every day (disconnected sessions), because nothing is working. I raised a Sev 2 case 3rd March and got one answer since then.
k
Hopefully this issue has been resolved in 2203
n
I mean, if it's fixed in a hotfix or patch, I was told it would be included in the next LTSR.
k
It should also be included in 1912 CU5
m
@Nick Panaccio (rant) If the same hotfix is included in 2203, that we applied on 2112, nothing will change and 2203 will cause quite some trouble.
๐Ÿ˜ž 1
n
That would be extremely disappointing.
That said, we have no S19 VDAs as of yet, so this would only be going on W10 and S16.
k
Well, if Citrix has managed to fix it in 1912 CU5, one would expect to also be able to fix it in 2203
m
If you are right, then most of my problems should magically vanish, when we switch at these customers from 2112 to 2203.
๐Ÿ‘ 1
k
With Citrix, there is no magic involved...ever ๐Ÿ˜›
โคด๏ธ 2
r
What he said LOL
๐Ÿ‘ 1