<https://support.citrix.com/s/article/CTX547782-cv...
# citrix-vad
m
https://support.citrix.com/s/article/CTX547782-cvad-2303-users-stuck-on-welcome-screen-when-reconnecting-to-a-disconnected-session?language=en_US Seeing a similiar behavior in 2203... Notably, running NVIDIA GRID... is there a way to "disable" Citrix graphics when utilizing NVIDIA grid in Win11-VDI altogether?
r
If you disable "Citrix Graphics" you won't see anything on the screen 😉
But this issue is specific to 2303 and is not applicable to 2203. What issue are you seeing?
m
It's similiar where end users get stuck on the Welcome screen, however I think we may have a profile issues... we're running Liquidware's ProfileUnity presently for profile disks, and the particular issue has crept up since the latest release of ProfileUnity... Can't tell if it's a Citrix-ProfileUnity Problem, ProfileUnity/Defender/Trellix problem, or what. The machines go flatline in terms of CPU usage, and get stuck on end-user login, no errors reported, just stuck
The last rev of ProfileUnity has caused us such greif, I've got an FSOGIX pilot underway, nevermind we just re-upped our licensing with Liquidware.
We've also had the Exchange Encryption black screen issue till I stumbled upon the IDD suggestion this week, appreciated by the way, as with all the Reduction in Force Email threads rolling around, lots of encrypted emails lately senior management has been grumpy they couldn't read
But the "gremlin" remains where I've got stalled logins for end users that is "random" even after terminating profile data on non-persistent desktops
Very complex issue
r
Hmm, sorry to hear. Hope you can get to the bottom of it. I would see if you can step by step disable components and figure out when it happens
m
So we recently have turned our attention to GPU only by happen chance, not convinced the gremlin I'm chasing is or isn't GPU related. We're just unpacking IDD vs DDAPI this side of TTC3.0 which will allow us to run more modern CVAD releases to your point
We've rolled out IDD in 2203 to impacted users, and retained DDAPI for everyone else this side of TTC3.0, but the question I had to to your bunch was best practice, as I felt I was missing something, which I was
8.75x perf delta from IDD to DDAPI was a 1+1=3 moment. I can buy 2203 IDD support is nacent, absolutely
r
I would not rely on WinSAT..
m
Indeed. However it's all I'm allowed on my production networks
r
If you run:
winsat features
You should see the NVIDIA GPU, even with IDD
Are you running:
winsat dwm
to get Video Memory throughput?
m
yes
FYI, have to call it a day... My civilian oversight is leaving the building, means I have to, as well
Cheers