This message was deleted.
# citrix-vads
Slackbot
02/01/2023, 2:04 PMThis message was deleted.
j
James Rankin
02/01/2023, 2:10 PMHaven't come across that, but on the subject, I recently saw something that promised the end of countless VDA upgrades to support Teams functions and a possibility of feature parity from "desktop" to "VDI" - there is light at the end of the tunnel....
🍻 2
đź‘Ť 1
k
Kris C
02/01/2023, 2:12 PMThanks James,
That sounds hopeful!
o
Oz Zy
02/01/2023, 2:51 PMNice. Feature parity nirvana would be fantastic
v
Vadim Gonzalez
02/02/2023, 4:07 AMWe have updated some VDIs (win 10) and servers (win 2016) with 2203 CU2. It shows “optimized” when logging on to VDI. But a number of times when I tried to log on XenApp server banner was missing and usb camera not working. I looked though Teams logs and there was something like “vdi mode not detected” or similar So I though something is wrong with either Teams or new VDA. But at least one user managed to logon and get “Citrix HDX optimized”. I have just retested and it worked from a WIndows laptop Teams 1.5.00.3362. VDA 2203 CU2. Looks like we also have latency issues with this new VDA.
j
James Rankin
02/02/2023, 9:13 AMDid you install with the correct switches?
k
Kris C
02/02/2023, 9:13 AMThank you, Vadim.
Always something with these VDA's...
I may try 2212 and see how I get on. I want a solid, stable VDA that enables latest Teams goodies.
Kris C
02/02/2023, 9:20 AMHi James,
Typical ALLUSER=1 ALLUSERS=1
I can see Websockets running, menus have their typical HDX appearance (i.e no Zoom, secondary ringer, etc. )
Ill have a look through the logs.
Little fed-up with Teams at the moment...
v
Vadim Gonzalez
02/02/2023, 11:58 AMwasn’t me installing Teams this time. But we use the same bat file, just replacing msi file (machine wide 64 bit msi). only these switches are bing used (ALLUSER=1 ALLUSERS=1) no other modifications. And it works but not always. For the last couple of days we were testing it it was not working more often than working. (I mean optimised mode)
k
Kris C
02/02/2023, 12:55 PMIt seems to show "Citrix HDX Optimized" in the about banner for my admin account that I'd installed Teams with. Not for any other of my test accounts, though, as said above, it LOOKS to still be HDX'ing despite not displaying the banner.
Kris C
02/03/2023, 12:28 PMUPDATE:
This could be related to a preview shim that MS recently applied to allow some specific previewing of Teams HDX features. We are having it rolled back to the standard. Will see if this helps.
đź‘€ 2
m
Matt Nation
02/07/2023, 4:31 PM@Vadim Gonzalez "Looks like we also have latency issues with this new VDA" - are you seeing issues where latency actually 'looks' good but you notice tons of delays within the session? I didn't see this until we started piloting CU2.
v
Vadim Gonzalez
02/09/2023, 12:05 AMOK, so we tried to go scientifically and put some stats. As it’s hard to rely on users feedback.
I decided use PS script on the server to grab the stats instead of collecting info from Director or Systrack
So ICA latency raises dramatically for the users running on new VDA.
I tested with the same test user, the same endpoint watching YouTube video on servers running old and new VDA
You could run the script attached on your test server and compare the results -it also dumps all samples and averaged values to csv files
My test case was:
launch session.
Wait till Teams fully launches.
Open Chrome
Open YouTube video set it to 1080
Start collecting stats with a script.
k
Kris C
02/10/2023, 10:00 AMThanks Vadim,
I think im going to pull the plug on the 2203.2 VDA upgrade. Im just not happy with the stability and what I've seen from other adopters (Who are rolling back..)
Kris C
02/14/2023, 3:41 PM@Vadim Gonzalez
Curious, do you still see the ICA Latency issues if you run straight through Storefront as opposed to traversing any Netscalers?
I seem to get triple figure ICA latency only when going through NS. its fine direct through SF. This also applied to internal NS.
Kris C
02/14/2023, 3:47 PM• When you run Connection Quality Indicator on VDA version 2112, incorrect Round Trip Time (RTT) and latency values might be reported.
• This fix allows you to use the legacy NetScaler L7 latency measurement when the HDX Adaptive Scaling feature is disabled. The NetScaler L7 latency and VDA HDX Adaptive Scaling features cannot be enabled simultaneously.
• For the functionality in the fix to take effect, you must disable the HDX Adaptive Scaling feature in the VDA registry as follows:
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\icawd
• Name: AdaptiveScalingEnabled
• Type: DWORD
• Value: 0
• [CVADHELP-19781]
Kris C
02/14/2023, 3:48 PMSeems to fix the (erroneous?) ICA Latency values for me. Even through NS, ICA latency is now back to typical response.
o
Oz Zy
02/14/2023, 4:07 PMinteresting. Thanks!
v
Vadim Gonzalez
02/15/2023, 6:20 AMCitrix support suggested to test going directly via Storefrorent after asking to update receiver on our Thin Clients. Receiver version is really old 14.x but that’s the last available for this hardware (Thin OS 8.6 on Dell Wyse 5060). We haven’t tried this reg fix. And we have just sealed our Feb vdisk with downgraded VDA. so we start focusing on upgrading the rest of components to 2203 first and then try VDA update again