- This topic has 7 replies, 5 voices, and was last updated 4 years, 5 months ago by
.
-
Posts
-
Hello,
currently, we are having problems with implementing a new environment. Here are specifics about our systems:
Devices: WYSE 3040
ThinsOS ver.: 8.6.027
BIOS: 1.2.5
Horizon: 5.01
ESX ver.: ESX 6.7 Update 2
Horizon enviroment: Horizon 7.9
Protocol: BlastWith that configuration, working with horizon is impossible. We are facing massive “mouse-lags” and lags with opening e.g. apps and explorers.
The thing is, we haven’t had those big problems with earlier versions of horizon. I mean, it wasn’t perfect but it was workable. Seems like, higher the version, bigger problems we have.
We will be so grateful if someone has stable configuration and he’d like to share some info to help us, or maybe some advise how to prepare the non-lagging environment.
Also, is there any way that we can run HTML5 redirection on Wyse?
Thank You in advance for the help.
Have you checked the few configuration options under General Settings – Horizon?
CG
I’m running a similar setup albeit slightly behind;
Devices: WYSE 3040
ThinsOS ver.: 8.6.027
BIOS: 1.2.4
Horizon: 5.1.19052918
ESX ver.: ESX 6.5 Update 1
Horizon enviroment: Horizon 7.7
Protocol: BlastNot seeing the same issues, is rolling back an option at all?
Devices: WYSE 5060
ThinsOS ver.: 8.6.027
Horizon: 5.1.19052918
ESX ver.: ESX 6.5 Update 1
Horizon enviroment: Horizon 7.10
Protocol: BlastThe same mouse lag problem. Tried this solution but it doesn’t work https://kb.vmware.com/s/article/53152
We have also one PCoIP optimized Wyse 5060. When we choose PCoIP for horizon session there is no any problems with mouse but only for Blast.
We have a deployment of about 1500 terminals using WTOS 8.6_019. Horizon Client 4.8, on Windows 10 guests on a Horizon 7.8 back end. We haven’t seen “mouse lag” issues, but, we have heard from users about sessions locking up. IE the Horizon session is locked, but on the ThinOS side, the terminal is fine. 5070s mostly, some 5010s.
We’re about to test out Horizon 5.1 clients and firmware 8.6_027, but, if anyone can add to this thread, as the OP states, with any findings they have from being on a similar platform, it would be great to hear.
Our 5010 Windows 7 PCoIP environment seems fine.
We’re also using WMS 1.4 for management/config.
So far we have done limited testing with 8.6_027 on the 5010/5070 units, with Horizon 5.1 clients on a 7.8 back end, but, so far it’s been successful. We really need to expand soon to have a more confident statement in this, but, thus far we have really nothing to name as a fault.
- You must be logged in to reply to this topic.