Lag with Wyse 3040 with dual DP displays in portrait mode

We are seeing the exact same thing on our 3040 clients except we're using our monitors in landscape (horizontal) orientation.

We're also experiencing monitor flickering and window "artifacting" where a window will appear on screen but will not be "filled in" unless you move the window to force a redraw.  This happens intermittently and seems to be worse on one of our older code LOB apps.  But it does happen on the latest version of Google Chrome when run on the clients.

We have 28 identical hosts running Windows Server 2016 RDS with 3-4 3040 thin clients connected to each and they are all exhibiting this behavior.

This started for us a few weeks ago after updating ThinOS to v8.5_017.  Unfortunately this is also around the same time that the latest Microsoft Cumulative Update for August 2018 hit so I wasn't sure at first which was causing the issue.  However, after some testing, when I connect to a host using a Microsoft Windows 10 laptop with the latest patches I don't have any flicker or redraw issues.  This leads me to think it's an issue with the latest ThinOS release.

I plan to test a brand new deployment this week with the previous ThinOS version (8.5_012) and see what happens.

Interesting that you're essentially having the same issue, but in landscape mode instead of portrait.  Makes me wonder if the displays involved have any impact on it- we're using 4x3 displays instead of 16x9.

Please keep me posted as to your testing with the previous ThinOS version, as I've been considering that avenue as well.

*exasperated sigh*

Well, I found and installed the Merlin version of the OS (8.5_B009), but it made no difference.  I also downgraded the BIOS to 1.2.0, and it made no difference.  Still scroll lag to the point of being unusable (if you want to be accurate and productive, that is).

ASE-IT, any luck on your end?

I would suggest you open a support case.  Support will have access to existing bug reports, and available resolutions.

I just did exactly that... we'll see what happens.

Perfect.  Keep us updated.   

Yes, in fact.  In my environment rolling back to the previous firmware release fixed all of our flickering and redraw issues.  Seems that there's something definitely not compatible between the 8.5_017 release and Windows Server 2016 running RDS.

What version of the firmware did you rollback to?  DId you make support aware so they can continue to investigate and fix in the 8.5 build?

Interested what you guys have discovered and whether a rollback worked permanently?

We have D10D Wyse Terminals running the same firmware. On delivering a Windows 10 desktop with only the VDA installed and Citrix user experience, on moving explorer windows around the latency goes through the roof and it slows down attempting to re-draw the window location. We are also dual screen - but I will test tomorrow on an individual screen to see how it behaves.

We have also had reports of latency during calls via Avaya Softphone around the same time as we updated all our Wyse devices to 8.5_017, but this could be something separate. I will test this also.

Also curious on what rollback worked (BIOS version, firmware version, packages installed and Horizon version) and if so, permanently.

Currently running the latest BIOS, firmware and packages available for Horizon. 

Have been trying to get 3040 (N10D) devices ready for deployment for two weeks straight and can not get past the performance issues. Chrome kills I/O, YouTube runs like hot garbage on any quality setting. It's a huge step back from our Tera2 clients and PCoIP that we're trying to move away from...

I've tried configuring and shaping Blast in our image but it appears to be just an issue with performance on the thin client. We've been using blast for Horizon Client sessions and RDSH sessions for about a year now with zero performance issues. There was actually a decent step up in performance in most scenarios moving from PCoIP to Blast on Horizon 7.3.1 in the rest of our environment. 

The worst part is the devices are stuck with ThinOS and we can't even try flashing ThinLinux or WES. 
Dell technically owns VMware now.. the last update was in July, I don't even understand how people are using these devices and how this hasn't been addressed...

Hi Sorry about the typo, I mean "WDM".

When we take a TC and attach two screens via DP we see two active screens which show the desktop of the TC BUT when we connect to RDS we only see the Windows Desktop on one screen. We did not configure anything in RDS GPOs except of "limit numbers of monitors" to Disbaled. By default the user is not able to change any settings on the TC due to "privilege level" is set to "None" and "Show Display settings" is set to "No". In the "Display" area we have "Enable Dual Monitor" - Tick "Dual Monitor Mode" - Span Mode "Main Screen" - Screen 1 "Auto detect monitors" - 1 TC Firmware = Wyse ThinOS (8.5_020)

Any ideas on this? Thanks