Installing the PCoIP Host Software Binary RPM

This topic describes how to install the binary RPM created from the source code package. To install the software you will require sudo command privileges.

Before installing the PCoIP host software, ensure no other copies of the software are installed by checking if the file pcoip_agent exists in the /usr/bin directory. If this file exists, remove it by following the instructions Uninstalling PCoIP Host Software.


  • PCoIP host software release 4.1.6 adds experimental support for Teradici PCoIP software clients. As an administrator, you cannot run the host software installer while connected to a host system using a software client because the local cursor feature is disabled during the installation process which disables the user’s keyboard and mouse. This prevents the user from completing the installation process.
  1. From the previously open terminal window, set the working directory to kernel/linux/obj/

    cd ..
    cd obj


    • Additional directories are created when you unpack the source code package.
    • If not at the default command prompt working directory enter cd ~/Downloads/PCoIP_Host_SW_Release/pcoip_ host_<version>/kernel/linux/obj/
  2. Enter the following command, where < build number > is the release build number.

    sudo yum install -y pcoip_host-<build number>.x86_64.rpm

    This installs the following files:

    • /usr/bin/pcoip_agent: This is the GUI that configures the PCoIP kernel driver. The UI accepts multiple command line options. See Command Line Options—pcoip_agent for a description of the supported options.
    • /usr/bin/pcoip_lockscreen: The GUI calls this script when locking the screen after a PCoIP session is disconnected. This script has been tested on systems running KDE3, KDE4, and Gnome. Verify this script works if the host software fails to lock the screen when a PCoIP session is disconnected.


      • The pcoip_agent and pcoip_lockscreen files are written to the /usr/bin directory when the host software is installed. If you want to move these files to a different location, such as a network drive, you must move both files to the same directory. When the pcoip_agent begins execution it searches for the pcoip_ lockscreen script in the /usr/bin directory. If the script is not found the pcoip_agent then looks in the directory the pcoip_agent is stored in.
      • If the pcoip_agent and pcoip_lockscreen files are moved, and a new version of the host software is installed, the administrator must remove the old copies of these files and replace them with the new files found in the /usr/bin directory.
    • /usr/bin/pcoiphostswd: This is the host software daemon. See Overview for a description of what the daemon does and Host Software Daemon Configuration Files for instructions on how to configure the daemon. If you want to establish a PCoIP session with a workstation from a soft client, do not disable the daemon.

    • /usr/bin/pcoip_starthostsw: The daemon uses this script to start the host software executable (pcoip_agent). Administrators who want to modify the command line options passed to the host software executable should modify the daemon configuration settings in section 3.5.1 "Host Software Daemon Configuration Files".
    • /usr/bin/pcoip_xauthority: The daemon uses this script to acquire an XAUTHORITY cookie. The script is run by the daemon as root. The daemon calls this script to provide some flexibility to the end user. If the script does not support the window manager running on the workstation, the script can be modified to support the new window manager without recompiling the daemon. See the script for details on how to update it if necessary.
    • /lib/modules/< kernel_version >/kernel/drivers/input/misc/pcoip_host.ko: This is a kernel driver that communicates with the PCoIP host card.
    • /etc/init.d/pcoip_host: This is a script that executes when the system boots. Links to the script are found in the /etc/rcx.ddirectories where x is >=0 and <=6. This script handles starting and stopping the pcoip_host driver.
    • /etc/init.d/pcoip_hostcheck: This is a script that executes when the system boots. Links to the script are found in the /etc/rcx.d directories where x is >= 0 and <=6. This script checks for the pcoip_host kernel module and builds it if it doesn’t exist.
    • /etc/udev/rules.d/10-pcoip_host_udev.rules: This file creates a special character file in the /dev directory used by the UI to control the driver.
  3. Non CentOS 6.x Distributions: Some Linux distributions require additional changes to the X Windows configuration file etc/X11/xorg.conf. These changes are not required on CentOS 6.x, but they are required on CentOS 5.x, SLED 11, and Fedora 13. The changes ensure the X Windows evdev input driver processes the data received from the PCoIP mouse device driver.

    Add the following line to the ServerLayout section:

    InputDevice “PCoIPMouse” “SendCoreEvents”

    Create the following new InputDevice section:

    Section “InputDevice”
    Identifier "PCoIPMouse"
    Driver "evdev"
    Option "Device" "/dev/input/pcoip_mouse"
    Option "Mode" "Absolute"
  4. Restart the system.

    sudo reboot