Transferring non-HID USB devices from the client to the host is called bridging. Both the Anyware agent on the host machine and the Anyware client must enable bridging before devices can be transferred. By default, Windows Anyware agents allow bridging of all USB devices.
Once you have successfully established a session between a Anyware Client and a PCoIP host, you can start developing your own Anyware client. To begin, set up your client development environment, as discussed next.
To set up your client development environment:
Before developing your custom client, you should set up a working Anyware system. HP recommends establishing a small proof-of-concept system for custom client testing, consisting of a host machine with an installed Anyware agent.
License Requirment
The following table outlines the system requirements for the Anyware Client for Windows:
HP may request a support file from your system to help troubleshoot and diagnose issues.
To create a support file:
There are two phases in a PCoIP session:
The steps indicated below are used and documented in the bundled sample code. Refer to the code for specific function calls, expected return values and error-handling requirements. The example C++ code can be found in the SDK package located here:
The core library allows an application developer to integrate a PCoIP session directly into an application. The core library facilitates connection to a remote host, decoding PCoIP image data directly into an application supplied frame buffer as well as remoting audio, keyboard and mouse events and supported USB devices.
When using the -l option with broker_client_example parameter to automatically pass session information to the session
client, you can pass additional session client parameters by enclosing them in double
quotes.
This release of the Client SDK for Windows contains bug fixes and stability enhancements for a seamless user experience. In addition, it includes the following feature: