This guide provides information for system administrators who are looking to implement, install, and develop HP Anyware solutions.
The material in this guide is based on the supported features and requirements of HP Anyware 2025.03. Earlier versions of HP Anyware, and its components, may not provide the level of support documented here.
Load balancers may be added to an HP Anyware deployment to distribute system and to optimize performance by distributing PCoIP connections across several Anyware Connectors.
HP Anyware enables PCoIP connections between users and remote workstations or desktops using any of several connection models dependent on number of users, location of users relative to remote workstations, your desire to incorporate public cloud workstations and your authentication requirements.
HP Anyware deployments are built from several distinct components that all work together. This page introduces the most common components you'll need to understand.
The PCoIP protocol provides remote desktop access to physical or virtualized computers, enabling fully interactive, visually seamless, and secure computing anywhere as a progressive alternative to a local deployment model.
Xencelabs Pen Displays are supported in the locally terminated mode, where peripheral data is processed locally at the Anyware Client. It is also supported in the bridged mode, where peripheral data is sent to the desktop for processing.
Support is available when a connection is initiated from a Windows Client to a Windows Graphics or Standard agent.
The following table contains a brief description of the header files included in the Anyware Client SDK for Windows:
Note: Location of the Header Files
The header files are available at the following locations in the Anyware Client SDK for Windows package:
External Dependencies
Boost and Qt are external dependencies that the SDK expects to be installed on the system on which the example code is being built.
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.