The following section outlines the configuration parameters involved in setting up a PCoIP session for Windows and Linux.
This section lists the configuration parameters in the Windows Local GPO editor.
| Note: Import the GPO Administrative Template File | |
|
The PCoIP settings will not appear in the GPO editor until the Administrative Template File is imported. If you have not done so, consult your respective administrators' guides on how to import the Administrative Template File. |
The Turn off Build-to-Lossless feature setting specifies whether to disable the build-to-lossless feature of the PCoIP protocol, which is disabled by default.
The build-to-lossless feature is disabled by default for Cloud Access Software Agents in order to provide network bandwidth savings. However, in environments that require high levels of image quality and/or lossless image reproduction, the build-to-lossless feature should be enabled.
This setting specifies the maximum bandwidth, in kbps, in a PCoIP session. The bandwidth includes all imaging, audio, virtual channel, USB, and control PCoIP traffic.
Set this value based on the overall capacity of the link to which your endpoint is connected, taking into consideration the number of expected concurrent PCoIP sessions.
The limit set can vary across usage scenarios, such as the following:
This setting specifies the maximum transmission unit (MTU) size for UDP packets for a PCoIP session.
The MTU size includes IP and UDP packet headers. TCP uses the standard MTU discovery mechanism to set MTU and is not affected by this setting. The maximum MTU size is 1500 bytes. The minimum MTU size is 500 bytes. The default value is 1200 bytes.
Typically, you do not have to change the MTU size. Change this value if you have an unusual network setup that causes PCoIP packet fragmentation.
This setting applies to the agent and client. If the two endpoints have different MTU size settings, the lowest size is used.
If this setting is disabled or not configured, the client uses the default value in the negotiation with the agent.
This setting specifies a lower limit, in kbps, for the bandwidth that is reserved by the PCoIP session. This setting configures the minimum expected bandwidth transmission rate for the endpoint. Note that the session will use less bandwidth than the floor if there is less data that needs to be sent. This setting is useful for two primary scenarios:
Make sure that you do not over-subscribe the total reserved bandwidth for all endpoints. Make sure that the sum of bandwidth floors for all connections in your configuration does not exceed the network capability:
(n users) * (minimum bandwidth) <= 90% of available link bandwidth
The default value is 0, which means that no minimum bandwidth is reserved. When this setting is disabled or not configured, no minimum bandwidth is reserved. This setting applies to the agent and client, but the setting only affects the endpoint on which it is configured.
Bandwidth Floor Configuration Examples
| User Type | Link Capacity [Mbps] | # Users | Packet Loss | Example Bandwidth Floor Configuration | Corresponding Bandwidth Floor Policy [kbps] | |||||||||||||||
| Artist/Designer |
|
|
|
|
|
|||||||||||||||
| Knowledge Worker |
|
|
|
|
|
|||||||||||||||
| Task Worker |
|
|
|
|
|
*The sum total of bandwidth floor values across should not exceed the available Link Bandwidth or the number of users.
This setting specifies the UDP agent port bound to by software PCoIP hosts.
The UDP port value specifies the base UDP port that the agent attempts to bind to. The UDP port range value determines how many additional ports to try if the base port is not available. The port range must be between 0 and 10.
This setting applies to the agent only.
This setting specifies the maximum bandwidth that can be used for audio (sound playback) in a PCoIP session.
The audio processing monitors the bandwidth used for audio. The processing selects the audio compression algorithm that provides the best audio possible, given the current bandwidth utilization. If a bandwidth limit is set, the processing reduces quality by changing the compression algorithm selection until the bandwidth limit is reached. If minimum quality audio cannot be provided within the bandwidth limit specified, audio is disabled.
This setting applies to the agent only. You must enable audio on both endpoints before this setting has any effect. In addition, this setting has no effect on USB audio.
When this setting is modified during an active PCoIP session, it will take effect immediately.
These settings controls how PCoIP renders images during periods of network congestion. The Minimum Image Quality, Maximum Initial Image Quality, and Maximum Frame Rate values interoperate to provide fine control in network-bandwidth constrained environments.
Maximum Initial Image Quality
Use the Maximum Initial Image Quality value to reduce the network bandwidth peaks required by PCoIP by limiting the initial quality of the changed regions of the display image. You can specify a value between 30 and 100. The default value is 80 for Cloud Access and 90 for Remote Workstation Card. A lower value reduces the image quality of content changes and decreases peak bandwidth requirements. A higher value increases the image quality of content changes and increases peak bandwidth requirements. Unchanged regions of the image progressively build to a lossless (perfect) quality regardless of this value. A value of 80 or lower best utilizes the available bandwidth.
Maximum Frame Rate
Use the Maximum Frame Rate value to manage the average bandwidth consumed per user by limiting the number of screen updates per second. You can specify a value between 1 and 60 frames per second. The default value is 30 for Cloud Access and 60 for Remote Workstation Card. A higher value proves smoother frame transitions important for some graphics applications but may use more bandwidth. A lower value uses less bandwidth but may increase the jitter rate of applications with a high source frame rate.
The Agent for Linux uses a single configuration file which is only writable by the administrator.
For information on how to set up your session configuration, consult the respective agent guides for Linux.