Anyware Support Bundler Tool
Anyware Support Bundler Tool
HP may request a support file from your system to help troubleshoot and diagnose issues.
To create a support file:
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:
Anyware Client for Windows now supports USB webcams when connecting to a Anyware Agent for Windows. USB webcams can now be used while in the remote desktop, including with applications such as Microsoft Teams or Zoom.
For detailed information which models have been tested and the performance metrics associated with these models see here. This knowledge base article also deals steps on how to test and verify other webcam models.
As of 21.07, this feature is enabled by default.
The Client SDK for Windows does not ship with its own session client binary; it uses the standard Anyware Client for Windows binary instead. Therefore, you must first download and install the Anyware client application, and then invoke it from the SDK.
Establishing a PCoIP session involves a number of key components, including system actors, PCoIP session phases, and connection brokers as discussed next.
There are at least three components that work together to create a PCoIP session:
If you need to support more than 20 USB devices, or if you expect your users to control which devices can be bridged, they can be manually added by opening the client’s USB Devices menu and enabling them.