PCoIP on 16 bits colors

[Salor10]

One question. When i open a PCoIP session, my display configuration tab does not appear, sometimes, when it appears, i can't to change bits deep to 16 bits, it change to 32 bit when i applied the change.

Can I to do that on PCoIP protocol?? Why the tab configuration appears sometimes, and another not??

Thanks.

[pauljawood]

Hi,

This sounds like a GPO issue and not anything relating to the VM. If you are getting the issue some times and not others are you getting the option when you login locally and not getting the option when you login to the domain.

Is it possible to get some more information please.

-

---

If you found this helpful then please leave some points.

[aj205 · Accepted solution]

PCoIP only support 32-bit color, when you install the view agent it will modify the color setting to 32-bit and not allow it to be changed.

[Salor10]

thank you very much, I had assumed it was because of protocol specifications.

[riazthewiz]

Solar10 is correct. It is totally random so far. We have a bunch of guys here who are testing the view for our Proof of Concept but none of us can figure out when it might show you the settings for color and when it may not. It is totally random. Again all are connected via "View 4 client" or through Wyse P20 (teradici pcoip).

[riazthewiz]

aj205,

Can you please point me to a spec document or link where it is says that the View 4 PCoIP client will always use 32bit.

Also does anyone know of any other trick of switching or defaulting to 16 bits for PCoIP. We already tried the OU poclicy for Terminal Services but obviously that doesn't affect PCoIP, Thanks,

[PCoIPinsider]

This should not be random - "Display Properties" should always be

inaccessible, operating in 32-bit color. Perhaps some pre-release

installations or registry reconfig?

Out of interest, why do you require 16-bit color?

- Ian

[riazthewiz]

Ian,

> This should not be random - "Dis....

It has been random or at least we are not able to recognize the pattern. The VMs were all newly deployed from a new template built from scratch (no PtoVs).

>

Out of interest, why do you require 16-bit color?

We were hoping to compare the performance performance using 16 vs. 32. bit on thin clients. We also wanted to see how much CPU/RAM/Network utilization occurs in each case using the same applications.

riz.

[aj205]

The only reference I could find is in the PCoIP datasheet.

http://www.vmware.com/files/pdf/VMware-View-4-PCoIP-DS-EN.pdf

AJ

[PCoIPinsider]

Riz,

>It has been random or at least we are not able to recognize the

pattern. >The VMs were all newly deployed from a new template built from

scratch (no >PtoVs).

It sounds like the registry key is either not being set correctly on all

machines during agent install or possibly being changed on some

afterwards.

>We were hoping to compare the performance using 16 vs. 32. bit >on thin

clients. We also wanted to see how much CPU/RAM/Network utilization

>occurs in each case using the same applications.

Fixed at 32-bits in current release I'm afraid.

Ian

[Salor10]

Putting
the desktop to 16 bits, is decided by the customer, who believes that
if a 32-bit is fast, 16-bit would be even faster connection. But nothing more.

Thanks a lot virtula people.

Gon.