Frequently Asked Questions

The following are answers to commonly asked questions when contemplating how to develop custom Anyware Clients using the Teradici Anyware Client SDK.

Q: Can I brand the pre-session client with my company logo and colors?

Anyware Client SDK for macOS 25.06

The Client SDK for macOS 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.

What's New in This Release?

The latest release 25.06 of the Client SDK for macOS fixes known issues, bugs and stability enhancements. In addition, it includes the following features:

The Collaboration Broker Client Example

The SDK package comes with a sample command line pre-session client called the Collaboration Broker Client Example, which calls the included broker client libraries and enables you to join a PCoIP collaboration session. The Collaboration Broker Client API Example demonstrates the success path for joining a PCoIP collaboration session.

Setting Up the Development Environment

Once you have successfully established a session between a Anyware Client and an Anyware 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:

Creating a Branding Package

In order to customize your session client, you must create a client branding package using the HP Custom Branding Package Utility. The HP Custom Branding Package Utility is located in the following location:

• macOS clients: "path-to-unzipped-sdk-package"/sdk/usr/bin/TeradiciBrandingPackageUtility

To create a custom branding package:

Branding Your Session Client

You can customize the branding of your custom session client in several ways by creating a client branding package. These customizations affect the user’s experience once they have connected to their PCoIP session. The following elements can be customized in the session client:

Using The Broker Client Example

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.

Supporting USB Devices

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. Administrators can globally disable USB bridging support, or enforce device whitelists or blacklists, using GPO variables on the host machine. Clients cannot bridge devices that are disallowed by the agent.