Can I use Cisco Express Forwarding per-packet load sharing with PCoIP Protocol?
No, Cisco Express Forwarding (CEF) per-packet load sharing causes out-of-order packets which is not compatible with real-time protocols such as PCoIP Protocol.  Cisco has similar recommendations against CEF per-packet load sharing when using Voice-over-IP …
What are the priorities for video, audio, and USB PCoIP traffic?
PCoIP technology gives priority to USB and audio, while imaging uses remaining available bandwidth. PCoIP technology optimizes user experience for a given bandwidth by adaptively controlling quality and update rate of the image data, and optionally …
Does the PCoIP Zero Client have left hand mouse configuration settings?
The PCoIP Zero Client currently has no specific left hand mouse setting. The PCoIP Zero Client configuration options in the OSD were designed to negate the necessity for right hand or left hand functionality therefore both buttons act the same. Right hand …
Can I share the network connection of the PCoIP Remote Workstation Card with that of the host PC/workstation?
No, the network interface on the PCoIP Remote Workstation Card is independent to that of the host. It is not possible to communicate to the host operating system via the PCoIP Remote Workstation Card network interface. Therefore, you must connect both the …
Could the use of two DVI channels be a sources for delay which might cause jitter in a PCoIP Remote Workstation Card configuration?
Using the two DVI channels on a PCoIP Zero Client to PCoIP Remote Workstation Card with the Dual-link DVI connector converter to achieve a 2560x1600 resolution is NOT a source for delay which might cause jitter. The use of two DVI channels could be one of …
What do the 4 different types of flash descriptions found in the PCoIP Zero Client logs mean?
These descriptors are found at the start of the event logs on the left hand side of the logs. NOT FOUND : There is no value set in flash for the parameter in question.  As a result, firmware reverts to the default value stored in the firmware image …