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:
There are two phases in a PCoIP session:
The SDK package comes with a sample command line pre-session client called the Broker Client example, which calls the included broker client libraries and establishes a PCoIP connection. The Broker Client API example demonstrates the success path for establishing new PCoIP sessions.
Do not Use the Broker Client Example in Production
The Session Client SDK for Windows supports Wacom tablets in two configurations: bridged, where peripheral data is sent to the desktop for processing, and locally terminated, where peripheral data is processed locally at the Anyware Client.
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.
The following PCoIP session features can be customized:
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.
PCoIP-compatible brokers are resource managers that authenticate users and dynamically assign authorized host agents to Anyware clients based on the identity of the user. Anyware clients can connect to Anyware agents using a PCoIP-compatible broker, called a brokered connection, or directly, called a non-brokered or direct connection. The broker c
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:
To send the Ctrl-Alt-Del keyboard command to a remote workstation, select the Connection > Send CTRL-ALT-DEL menu option.