PCoIP Host Software Component Overview

The host software is installed using a binary RPM. The RPM includes a kernel driver. Kernel drivers must be built using header files that match the version of the kernel running on the workstation the host software is installed on. This restriction prevents Teradici from distributing pre-built RPMs. The package provided by Teradici allows end users to create the binary RPM.

The Installation category of topics describe requirements and steps to set up a Linux system capable of creating the PCoIP host software binary RPM. The topics are written for a Linux system running CentOS 6.6. The same instructions may apply to other Linux distributions, but may require changes.

The PCoIP Host Software for Linux requires knowledge of the Host Driver Function, User Interface, and the Host Software Daemon components which are summarized below.

Host Driver Function

Host computers containing PCoIP remote workstation cards loaded with firmware releases 3.1.0 or later support an optional feature, the PCoIP Host Driver Function. This feature lets administrators use the PCoIP Host Software for Linux package on the host PC or workstation. This software package works with the exposed PCoIP Host Driver Function PCI device function. If an administrator installs the PCoIP host software package on the PC or workstation, users can manage and use the features of the PCoIP Host Software for Linux when the Host Driver Function is enabled.

Host Software User Interface (UI)

The user application called the host software user interface (UI), is installed when the host software is installed. The UI communicates with the PCoIP firmware via the device drivers installed by the PCoIP host software. You can configure the features of the PCoIP host software through the UI.

Host Software Daemon

Release 4.1.6 and later included an additional software application called the host software daemon. By default, the daemon is enabled and starts running when the workstation boots and is responsable for:

  • Starting the UI when the workstation boots and ensuring one instance of the UI is always running. The daemon restarts the UI if it exits for any reason.
  • Activating the Local Cursor and Keyboard feature for soft client sessions while the login screen is active.
  • Disabling the Local Cursor and Keyboard feature for zero client sessions when a user logs off.

For details on configuring the daemon, see Host Software Daemon Configuration Files.