Limits on Customization

Limits on Customization

The macOS has elements which are part of the operating system user interface and cannot be modified programmatically, as described in the following sections.

macOS Limitations

The following run-time limitations are enforced by macOS on the application menu (beside the menu apple icon menu):

Anyware Support Bundler Tool

Anyware Support Bundler Tool

HP Anyware's support team may request a support file from your system to help troubleshoot and diagnose PCoIP issues.

Customizable Script

This script can be customized, in the case where the log files are located in a different location the script should be updated appropriately.

To create a support file:

Core API Integration

PCoIP Core Library Integration

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.

Xencelabs Pen Displays

Supported Xencelabs Pen Displays

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 macOS Client to a Windows Graphics or Standard agent.

Establishing a PCoIP Session

Establishing a PCoIP Session

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:

About PCoIP Sessions

About PCoIP Sessions

Establishing a PCoIP session involves a number of key components, including system actors, PCoIP session phases, and connection brokers as discussed next.

System Actors

There are at least three components that work together to create a PCoIP session:

The Broker Client API Example

The Broker Client Example

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

Wacom Support

Wacom Tablet Support

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

Locally terminated Wacom tablets are much more responsive and tolerate low latency connections.

Customizable Session Features

The following PCoIP session features can be customized:

  • Session Menu bar Visibility
  • Disable Hot Keys
  • Windowed or Fullscreen Mode
  • Set Host Resolution
  • Custom Client Branding
  • Image Scaling
  • Maintain Aspect Ratio
  • USB Auto Forward
  • USB VID/PID Auto Forward
  • Disable USB
  • Locale
  • Session Log ID
  • Log Level
  • Log Folder
  • Log Prefix
  • Force Native Resolution

Examples show command-line usage

About Brokered and Non-Brokered Connections

About Brokered and Non-Brokered Connections

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