For most use cases UDP is more ideal and is what the Blast protocol first attempts to leverage by default.
In the context of optimizing Blast for your environment, one of the first questions to ask about your Blast traffic is whether UDP or TCP is used for the transport protocol. Then, from the UAG appliance to the virtual desktop or RDS host, traffic flows over 22443. For the secondary protocol, Blast Extreme in this example, traffic flows over 8443 between the client and the UAG appliance. Typically, the primary protocol is completely over 443 between the Horizon client and UAG appliance, as well as between the UAG appliance and Horizon Connection server. If you go with the default port of 8443 for Blast traffic here's what the traffic flow looks like when remoting into a Horizon environment through a UAG appliance: This is what we're primarily concerned with when optimizing the Blast experience. The secondary protocol is the display protocol itself, what translates/transmits pixels from within a virtual desktop OS to the display of an endpoint device. The primary Horizon protocol is all about authenticating against the Horizon environment through XML over 443. Under the section titled, "Horizon Protocols," i t details the distinction between a primary and secondary Horizon protocol. We can configure these policies and store in templates to avoid repetitive configurations.The blog post, Load Balancing Across VMware Unified Access Gateway Appliances, contains one my favorite descriptions of Horizon sessions. Local policy management reduces required policy updates from centralized GPO. This difference in policy does make sense considering HPT helps you to monitor performance data of local system and hence can be better managed with local polices depending upon local OS as we can use HPT on client operating systems like Win 10 and on RDSH as well. To clear this preference GPO setting, select Disable. When enabled, Horizon Performance Tracker starts automatically when a user logs in to a remote application connection. To clear this preference GPO setting, select Disable.Įnable Horizon Performance Tracker auto start in remote application connection When enabled, Horizon Performance Tracker starts automatically when a user logs in to a remote desktop connection. When enabled, you can set the frequency in seconds at which Horizon Performance Tracker collects data.Įnable Horizon Performance Tracker auto start in remote desktop connection. Horizon Performance Tracker basic setting Below are the details of available policies.CPU usage of the encoder in current user session.
Overall bandwidth for incoming and outgoing traffic, averaged over the sampling period for display protocol being used i.e.Number of imaging frames encoded over a one-second sampling period (FPS).The name of encoder used in display protocol.Protocol specific data – Encoder and CPU: HPT provides you with quick insights into performance data such as: This can be very useful while troubleshooting virtual desktop performance related issues. So to investigate this problem, where do you start? and how do you collect the data?Īs mentioned earlier, HPT collects the performance data and displays it. Just imagine that one of the end user is complaining about VDI desktop performance being slow. HPT runs in a virtual desktop and displays the collected performance data of display protocol (PCoIP or Blast) along with system resource usage such as cpu usage. VMware Horizon Performance Tracker or HPT feature is available with Horizon 7.5 and later releases.
#Vmware horizon client bandwidth requirements how to#
We will discuss monitoring data provided by HPT, Requirements of HPT, Installing HPT, how to use HTP, and lastly but important one, differences of policies when managed in domain GPO and when managed with Local GPO. In this post, we will be exploring Horizon Performance Tracker feature and I will be using term HPT here onwards in this post to refer Horizon Performance tracker.
0 kommentar(er)
