Random individual and mass client disconnects due to Cisco VSS Inter-switch links
Problem Random individual client disconnect, or mass client disconnects when connecting clients (PCoIP Software Clients, VMware View Clients, or PCoIP Zero Clients) connected to HP Anyware or VMware View virtual desktops.   Cause There have been observed …
How do I change the FQDN (Fully Qualified Domain Name) of a PCoIP Zero Client?
First, change the PCoIP name to a new name. Currently, the "PCoIP Device Name" can only be changed on an individual basis in two locations: The  "OSD--> Configuration--> Label"  tab The  "AWI--> Configuration--> Label"  tab The default format is  …
PCoIP Firmware 4.0.2 Issue Notification
Scenario There is an issue with firmware 4.0.2 where the use of the PCoIP Management Console 1.8.0 could result in rendering the Tera2 zero client non-functional and non-recoverable. This issue may be encountered intermittently when deploying profiles …
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 …
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 …
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 …
Recovering the OSD when the resolution was set to 800x600 or lower which removed functionality.
This occurs because these low resolutions do not display the OSD correctly, and access to some configurations are lost. Previously this was not an available feature which prevented devices being put into un-configurable states by setting resolutions to …