Calling USB functions will fail unless the application a user uses for calling the functions is signed and the USB service trusts the application.
The application must be signed in a way that is trusted by the OS. To check this:
The Client USB package must be uninstalled before installing a new version.
To update the Client USB Package:
The sample Collaboration Broker Client demonstrates how the APIs can be used to customize and control the pre-session and session phases of the Collaboration connection. Invoking the Collaboration Broker Client API is a two-step procedure, where as a first step, the Collaboration Broker Client Example is built.
Invoking the Broker Client API is a two-step procedure, where as a first step, the Broker Client Example is built. The second step consists of running either a prebuilt PCoIP binary, or a prebuilt AWS binary.
Finding the Latest Information
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: