How do I license and configure RealVNC Connect on a Windows computer over RDP?

Follow

Licensing RealVNC Connect

Once you have successfully installed RealVNC Connect (v8) or RealVNC Server (v7), you need to manually open the License Wizard to apply your subscription.

You can do this by navigating to the installation directory:

  • For RealVNC Connect (v8), C:\Program Files\RealVNC\RealVNC Connect
  • For RealVNC Server (v7), C:\Program Files\RealVNC\VNC Server 

Then locate and double-click the License Wizard application:

  • For RealVNC Connect (v8), vnclicensewiz.exe
  • For RealVNC Server (v7), rvnclicensewiz.exe 

Once the License Wizard is open, you can either: 

  • (All subscriptions) Sign in to your RealVNC account to enable cloud connectivity, or;
  • (Enterprise subscriptions only) Apply your offline license (located under the "Deployment" section of your RealVNC account)

Configuring RealVNC Connect

RealVNC Connect (v8)

When viewing the My Device or Inbound Connections Settings page while connected to RDP, the Inbound Connections page will still be displayed as not enabled (screenshot below):

Due to the way RDP creates it's own virtual session and runs RealVNC Connect Inbound in the background, the application when installing it through RDP is not currently able to check whether the service has started which is why the page doesn't update. However, you can confirm whether the service is running by opening Services via the Windows Start Menu and checking whether the "RealVNC Connect Inbound" service is running.



As soon as you’ve installed and licensed RealVNC Connect, we recommend disconnecting your RDP session and connecting using RealVNC Connect or RealVNC Viewer instead. Once you connect via RealVNC Viewer/RealVNC Connect and go to Inbound Settings, you should see that it is enable and have access to further options.

RealVNC Server (v7)

When connected by RDP, you will not have access to the RealVNC Server icon. This is because RDP doesn't actually show the console session (the screen you'd see if you were sitting in front of the computer). It creates its own virtual session, meaning that RealVNC Server is in fact running correctly in the background, but the system tray icon will be showing on the console session, not within your virtual user session.

As soon as you’ve installed and licensed RealVNC Server, we recommend disconnecting your RDP session and connecting using RealVNC Connect or RealVNC Viewer instead. You will then be able to access the RealVNC Server UI and tray icon.

If you cannot access the remote device either directly or using RealVNC Connect, you will need to configure RealVNC Server's configuration in the Registry.

Was this article helpful?
46 out of 75 found this helpful

Comments

0 comments

Article is closed for comments.