VMware Horizon® View with PCoIP® and Blast Extreme. It comes with support for Linux® operating systems and Cloud Desktop OS and protocols including:ġ. The CD8841 thin client device might resonate with your particular VDI environment as it did in my case. I was not familiar with their VDI endpoints but after understanding my business model, they suggested a thin client solution that delivered. However, my personal favorite is ClearCube because their customer support team has been very responsive to my needs. All three vendors offer endpoints that support the Blast Extreme protocol. I would recommend you to narrow down your choices to Wyse, HP and ClearCube. Blast Extreme, on the other hand, is a single-codec protocol. This expands your options because you can then choose between various codecs for specific tasks. Personally, I prefer PCoIP because this protocol comes with support for multiple codecs which deliver great UX and offer optimal bandwidth and CPU load in VDI environments. We're opening a BCS case shortly, but I wanted to add that we're seeing the same lack of resiliency since we upgraded to Horizon 7.4, that we didn't see on previous 7.x releases. It's been resolved for us each time by recycling the Connection Server services overnight when fewer users are connecting (or by taking them out of the load balancers one by one and recycling the services), but that is getting old and not sustainable.
We have had to constantly monitor the inventory and manually power them on, sometimes dozens at a time (we have a lot of VMs). This has happened at least 3 times over the last 2 weeks, and it's begging to impact production (VMs powered off so users can't access them). We also have provisioning problems (failed customization, "Error", "Missing", etc.). This operation stops working once the vSphere unavailability above take place. We have power on policies on all of our VM pools (persistent, ful clone VMs), where if a VM is shut down by a user, View tells vSphere to power it back up almost immediately.
#SSL ERROR VMWARE HORIZON CLIENT 4.7 WINDOWS#
We are seeing that if a vCenter goes down (for a maintenance reboot, Windows patching, etc.), View logs that it's unavailable for the duration that it's down, and reconnects when it's back up, but has severe issues until a Connection Server service restart takes place on one or all of the Connection Servers in the pod. We're experiencing similar issues since upgrading to Horizon 7.4 from 7.2.0 about a month ago.
0 kommentar(er)
