How has licensing changed between RealVNC 6.x and RealVNC 7.x?

In RealVNC 7.x there are some changes in licensing to be aware of.

Licensing RealVNC Server 7.x using the cloud

RealVNC 7.x continues to be able to be licensed via the cloud, there are no actions required when upgrading cloud-joined RealVNC Server 6.x to RealVNC Server 7.x.

Licensing RealVNC Server 7.x offline, using an offline license

While RealVNC 7.x can continue to be licensed offline, it moves away from using a 25 character key and instead uses an offline license file, or token. The offline license can be obtained in the same way as the offline license for RealVNC 6.x, which is by accessing the Deployment page of the VNC Connect portal.

When upgrading offline-licensed RealVNC Server 6.x to RealVNC Server 7.x, RealVNC Server 7.x will honour the RealVNC 6.x key until its expiry date. However, it will show a message in the Message Center that "licensing has changed".

To remove this message, obtain and apply the RealVNC 7.x offline license as shown here: Updating an offline license.

Licensing using policy

New policy template files are required to license RealVNC 7.x. You can read more about where to download these and use them here: Remotely Configuring and Locking Down VNC Connect Using Policy
Note: existing policy templates applying a RealVNC 6.x offline license key will be honoured by RealVNC 7.x until the expiry of the RealVNC 6.x offline license.

Licensing using MSI transform

The MSI transform property to apply an offline license has changed from LICENSEKEY to OFFLINELICENSE. For more information about licensing using an MSI, please see Deploying and Licensing VNC Connect using Windows MSIs