Sneak Peek at new VMware View 5.0 PCoIP GPO

VMware View 5.0 NDA has been lifted and by now VMware and bloggers should have started to announce the new features. VMware View 5.0 is mostly about improving user experience with several adjustments to PCoIP and the addition of a user profile management tool.

Read my article What’s New in VMware View 5.0 (beyond Marketing).

With View 5.0 new customization options have been added. These options are customizable via ADM templates and require the creation of specific GPO (Group Policy Object) to be applied on VMware View desktops, client computers and even View servers.

I have previously written about how to use GPO for Optimizing PCoIP Display & Imaging, Addressing Self-Service Password Reset with VMware View 4.6 and even on how to use them at Printing Architectures for VDI.

Just like in previous releases of View there is a ADM template specifically for PCoIP settings. I will comment on those items that offer the most improvement on user experience.



Turn off Build-to-Lossless feature – This is the feature that will put PCoIP in parity with ICA when the discussion is around bandwidth consumption. Build-to-Lossless is On by Default and included in the PCoIP protocol within VMware View.

Turning Off the Build-to-Lossless imaging feature will cause images and desktop content not to be built to a lossless state.  Turning Off Build-to-Lossless will provide bandwidth savings for constrained bandwidth network environments.

Be careful when disabling Build-to-Lossless if your users are picky about image quality or there is a need to provide lossless imaging.



Configure the maximum PCoIP session bandwidth – This is the old PColPMaxLinkRate. Read more at Optimizing PCoIP Display & Imaging.


Configure the PCoIP session MTU – This policy can be used to set the Maximum Transmission Unit (MTU) size  for UDP packets for a PCoIP session.

This MTU size includes the IP and UDP packet headers. (TCP uses the standard MTU discovery mechanism to set MTU and is not affected by this setting.)  The MTU size will not generally need to be changed from the default unless there is an unusual network setup which causes PCoIP packet fragmentation.

This policy applies to both server and client; the MTU is negotiated to be the minimum of the server and client settings.

Leaving this policy Disabled or Not Configured means that the default will be used by this endpoint in the negotiation otherwise the Configured value will be used by this endpoint in the negotiation.  The MTU setting has a maximum value of 1500 and a minimum value of 500.  The default MTU setting is 1300 bytes.


Configure the PCoIP session bandwidth floor – This is then old pcoip.device_bandwidth_floor. Read more at PCoIP: Unleash the Throughput.


Enable/disable microphone noise and DC offset filter in PCoIP session – Unless you are using Zero Clients and the Teradici audio driver this option is not applicable to your environment. Additionally, the Teradici audio driver is not supported by VMware.


Configure the PCoIP session audio bandwidth limit – Great customizable option to constrains the maximum bandwidth that can be used for audio (introduced in VMware View 4.6)

The audio processing monitors the bandwidth utilized for audio at any given time. The processing selects the audio compression algorithm used based on providing the best audio possible given the current bandwidth utilization. If the bandwidth limit is set, then the quality is reduced until the bandwidth limit can be respected.  If minimum quality audio cannot be provided within the bandwidth limit specified then audio is disabled.

To allow for uncompressed high quality stereo audio the value for this setting should be above 1600 kbit/s. A value setting of 450 kbit/s and higher will allow for stereo high quality compressed audio.  A value setting between 50 kbit/s and 450 kbit/s will result in audio ranging between FM radio and phone call quality.  A value setting below 50 kbit/s may result in no audio playback.


Configure clipboard redirection – This policy configures the allowed direction of clipboard redirection. Also allows administrators to configure the direction to which copy/paste is allowed.



Configure PCoIP client image cache size policyNew feature implemented on VMware View 5.0 Windows soft client to improve user experience. This feature enables control over the size of the PCoIP client image cache.  The client uses image caching to store portions of the display which have been previously transmitted to reduce the amount of retransmitted data. When this policy is Not Configured or Disabled, the client image cache size defaults to 250 MB.




The 3D features available in VMware View 5 are part of the improvements in vSphere 5 when utilizing virtual hardware version 8. VMware View 5 leverage those improvements to deliver Windows Aero and 3D and they are not controlled by PCoIP display protocol Group Policies.


1 ping

  1. Dan

    Great Write Up.
    For the PCoIP BTL policy, does that get applied to both client and server? Or just client?

  2. Andre Leibovici

    The GPO used for the BTL is named (agents.ADM) and is only apllied to the virtual dekstops computer objects. There is another ADM template specific for the clients (physicial computer with the VMware Windows SoftClient) but this one does not control BTL.


  1. VDI for me. Part 4 « A glimpse into the life of IT

    […] deployment.  With View 5, it works quite well out of the box.  I will defer to this post http://myvirtualcloud.net/?p=2061 on some common, View specific GPO settings you might want to adjust, especially in a WAN […]

Leave a Reply