This message was deleted.
# citrix-vad
s
This message was deleted.
r
a quick check here, nothing is modifying the CtxUvi via GPO , right? I know you said it works with 2305/2308. But just confirming.
d
Hi Ray, no, already checked this one. I also uninstalled the older VDA and performed a fresh installation of VDA 2311.
There is absolutely nothing you can do. An admin has to logoff the session, a user can only disconnect but this doesn’t help.
d
2311 introduced auto codec select so maybe you can force a different one to see if it works. https://docs.citrix.com/en-us/citrix-workspace-app-for-windows/graphics-and-display#automatic-selection-of-video-codec
d
Yes, I also thought about this, but the version of the WSA doesn’t matter, it’s all about the VDA version.
d
hmm i think WSA matters "Starting with 2311.1 release, Citrix Workspace app for Windows now automatically detects the best video codec to use. During installation of the Citrix Workspace app for Windows, the decoding capabilities of the endpoint are evaluated. Based on this information, Citrix Workspace app for Windows selects the best codec to use with the VDA when the session starts"
j
@Rody Kossen FYI
r
@Dennis Few questions: • Does the VDA have a (v)GPU? • Are there any errors in the Eventlog? • Did you create a support case? If so, can you share the ID? • Do you have CDF Traces from VDA and CWA? If so, can you share them with me? @Danny The auto codec select is only available in CWA 2311+, so that would not impact users with older CWA version. Also, the codec only is applicable if you have a video playing (If you use our default policy) or with Fullscreen video codec policy active (which I do not expect here).
d
ah yea seems I thought it was only happening with CWA 2311 and figured thats the only big change. my bad
d
@Rody Kossen helped me with that. It turned out that it was due to the target fps. We changed it from 40 to 45 and the issue was gone. I don’t know exactly if it has something to do with the NVidia vGPU we use in the VM. All I can confirm is, that the issue also occurred without a GPU added to the VM.
d
thanks for the update