« Back to docs

Installing and removing VNC Connect

These instructions explain how to install VNC Connect (version 6.x) on principal Red Hat-compatible Linux computers.

Note

You can perform all the operations on this page at the command line. Check out our example script.

Upgrading to VNC Connect

If you are upgrading from VNC 5.x and have a valid Personal or Enterprise license key, installation should be seamless. You do not need to stop VNC Server, and any configuration changes you have made will be preserved. If you wish to enable cloud connectivity, perform this post-install step.

If you have an out-of-date Personal or Enterprise license key for VNC 5.x, you must purchase a subscription as a new customer.

If you have a Free license key for VNC 5.x, you can migrate to a new, free Home subscription providing you install VNC Connect desk-side. You cannot migrate over a remote control session.

If you wish to upgrade from VNC Enterprise Edition or VNC Personal Edition 4.x, we recommend you first contact Support.

Downloading VNC Connect

Download the appropriate VNC RPM installer for the architecture of the computer you want to control. VNC Server and VNC Viewer are included as separate installable packages.

If you do not have administrative privileges, or want to specify non-default installation locations, download the appropriate generic installer instead, and run the script provided.

Note

VNC Viewer is freely available to download as a separate app if required.

Installing VNC Connect

Note the following:

  • VNC Server depends upon xterm. You must install it and all its dependencies first.
  • VNC Server conflicts with TigerVNC, a pre-installed third-party VNC-compatible application. Conflicting binaries (Xvnc and vncpasswd) are renamed on installation, and restored if VNC Server is uninstalled.

Using desktop tools

To install VNC Server, open <VNC-Server>.rpm using a suitable package manager, and follow the instructions. Administrative privileges are required. To install VNC Viewer, repeat this operation for <VNC-Viewer>.rpm

At the command line

Installing at the command line or via SSH may be quicker and more convenient providing defaults are acceptable. To do this, run the following command as a user with administrative privileges:

rpm -U <VNC-Server>.rpm <VNC-Viewer>.rpm

Licensing VNC Server

You must apply a subscription to VNC Server. If you do not, remote access will not be available.

Note

VNC Viewer does not need to be licensed.

Using desktop tools

Open the VNC Server dialog and select Licensing from the menu to open the graphical License Wizard. Follow the instructions to sign in with your RealVNC account credentials.

If you have an Enterprise subscription, direct connectivity will be automatically enabled, and you are prompted to enable cloud connectivity at the same time.

At the command line

Note

You can only license VNC Server at the command line if you have an Enterprise subscription.

A 25 character license key for offline or remote deployment is available from the Deployment page of your RealVNC account. To apply it, run the following command as a user with administrative privileges:

vnclicense -add KEY

Direct connectivity is automatically enabled. To enable cloud connectivity, and optionally join one or more existing computer groups in order to restrict access, run the following command as a user with administrative privileges:

vncserver-x11 -service -joinCloud TOKEN [-joinGroup GROUP-NAME]...

Cloud connectivity tokens are available from the Deployment page of your RealVNC account.

Setting up the environment for VNC Server

VNC Server in Virtual Mode

If you are using the latest Fedora distributions, you may need to change the desktop environment.

VNC Server in Service Mode

If you are using Fedora 22 or later, you must swap the Wayland compositor for X in order to remote the login screen. Open /etc/gdm/custom.conf in a text editor, uncomment the following line, and then restart the computer:

# WaylandEnable=False

SELinux

Policy modules will have been automatically registered if SELinux was enabled during VNC Connect installation or upgrade. If you enable SELinux afterwards, run vncinitconfig -register-SELinux to register these policy modules manually.

Note

Policy modules cannot be registered on versions of CentOS/RHEL earlier than 5.0.

Starting VNC Server

To start VNC Server in Service Mode, run the appropriate command as a user with administrative privileges:

systemctl start vncserver-x11-serviced.service #systemd
/etc/init.d/vncserver-x11-serviced start #initd

For other command line operations and modes, see these instructions.

Removing VNC Connect

Using desktop tools

To uninstall VNC Server, open a package manager, conduct a search for the realvnc-vnc-server package, mark the package for removal, and apply the change. Administrative privileges are required. To uninstall VNC Viewer, repeat this operation for realvnc-vnc-viewer.

At the command line

Run the following command as a user with administrative privileges:

rpm -e realvnc-vnc-server realvnc-vnc-viewer

Note

To completely remove (benign) configuration and other files or settings that may remain, follow these instructions.

×