RealVNC GPO Install not showing in systray

0

Have installed RealVNC 6.3.2 on a test PC using the GPO Computer Configuration.

However when it is deployed to the test machine, I can see VNC Server in the start menu (doesn't produce any dialog box when clicked on), cannot see a VNC Server icon in the notification area/systray, and when trying to connect get "The connection was refused by the computer", which according to https://www.realvnc.com/en/connect/docs/connect-error-ref.html#connect-error-ref infers that the server isn't running (despite services.msc stating it is) or it is listening on the wrong port. Unless I am missing something, without the notification area/systray icon for RealVNC, I cannot check on which port it is configured to listen on.

My assumption is that VNC has been installed on some system account, and hence the GUI is appearing on a different console. Though the install docs didn't mention any issue with deploying to PCs, Users, or both.

Anyone know what is going here?

user66001

Posted 2018-12-31T23:20:34.083

Reputation: 1 050

Which version of the RealVNC server are you running? – srk – 2019-01-22T09:35:49.957

@srk - Updated question with version no. as requested. – user66001 – 2019-01-22T17:14:24.417

Are you physically in front of the desktop with the problem, or are you using a different remote access tool like Microsoft's Remote Desktop (RDP)? – srk – 2019-01-29T11:53:05.047

Desktop is in the same building, but I RDP'd into it when I logged in. Hopefully you're not saying that Windows doesn't run the same login process when RDP'ng as opposed to logging in locall? – user66001 – 2019-01-29T13:44:04.880

Yes that is the case, you won't see the VNC Server (or any of its UI) in your RDP session as it only tracks the console session (i.e. what the local user would see). The server is probably running (as that is the default when it installs) but if you haven't added a subscription/license key then you won't be able to connect to it. – srk – 2019-02-02T12:14:11.170

I think the license is what is missing here, now that you mention it. I have RDP'd into machines with licensed RealVNC installed before and been able to interact with it in ways I can't with this unlicensed install (because of course non-commercial users would never need to remote into another PC, in let's say, their home...) – user66001 – 2019-02-02T16:14:14.593

No answers