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 contains bug fixes and stability enhancements. In addition, release 24.10 of the Client SDK for Windows includes:
Anyware Software 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.
The Client SDK for Windows does not ship with its own session client binary; it uses the standard Anyware Software 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.
You may not be able to programmatically modify certain session features due to limitations imposed by the operating systems's user interface.
The Client SDK for Windows provides developers tools to create a custom Anyware client with a unique user interface and workflow, or to embed a PCoIP session into another program or solution. Clients built with the SDK can connect to remote desktops using Anyware agents or Remote Workstation Cards.
The SDK is provided as part of HP Anyware by special agreement with HP.
Brokered Session Connection
If you are using a brokered session, this is handled by the broker libraries automatically.
Before you can establish a PCoIP session with a host desktop, gather the following host desktop details:
You can make the installer and uninstaller calls programmatically from your client application. The return and exit codes you should expect are summarized in the following tables: