Is there any advantage to running UltraVNC as a service?
thx
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Advantage to running as a service?
Disadvantages are mainly slightly higher resource utilization when not active.
In some (company) scenarios, security policies may interfere.
Mainly, it is an open, listening TCP port.
Or, someone could connect to a server, while nobody is logged on, and just wait until a new user logs on directly to the server. The new user might not be aware that his session is being monitored (or possibly manipulated).
You can get the advantages of the service without the security implications by not accepting socket connections, but using reverse connection only, like SingleClick.
In some (company) scenarios, security policies may interfere.
Mainly, it is an open, listening TCP port.
Or, someone could connect to a server, while nobody is logged on, and just wait until a new user logs on directly to the server. The new user might not be aware that his session is being monitored (or possibly manipulated).
You can get the advantages of the service without the security implications by not accepting socket connections, but using reverse connection only, like SingleClick.
Are you listing these as disadvantages to RD or UltraVNC ?rmoller wrote:Disadvantages are mainly slightly higher resource utilization when not active.
In some (company) scenarios, security policies may interfere.
Mainly, it is an open, listening TCP port.
Or, someone could connect to a server, while nobody is logged on, and just wait until a new user logs on directly to the server. The new user might not be aware that his session is being monitored (or possibly manipulated).
You can get the advantages of the service without the security implications by not accepting socket connections, but using reverse connection only, like SingleClick.
No, as disadvantages running UltraVNC in service mode as opposed to user (non-service) mode.grindy wrote:Are you listing these as disadvantages to RD or UltraVNC ?rmoller wrote:Disadvantages are mainly slightly higher resource utilization when not active.
In some (company) scenarios, security policies may interfere.
Mainly, it is an open, listening TCP port.
Or, someone could connect to a server, while nobody is logged on, and just wait until a new user logs on directly to the server. The new user might not be aware that his session is being monitored (or possibly manipulated).
You can get the advantages of the service without the security implications by not accepting socket connections, but using reverse connection only, like SingleClick.
You may want to read this topic: [topic=269]XP Remote Desktop vs. UltraVNC.[/topic]
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
The biggest disadvantage is that the service can only interact with session0.
Until win 2000, the console always was session0. But all later version
can have a console session other the 0.
XP: fast user switching
win2003: After a RDP connection
Vista: the console is never session0
As the service can only interact with session0. In XP and win2003 you need to force the console to session0. This can only be done by disconnecting the current console user and restart a new console .
Not a proper way....but the only possible.
Vista is still a big challenge, as service will not work at all.
Natural, security....
A service run as system, while vnc as app takes the user permission.
Until win 2000, the console always was session0. But all later version
can have a console session other the 0.
XP: fast user switching
win2003: After a RDP connection
Vista: the console is never session0
As the service can only interact with session0. In XP and win2003 you need to force the console to session0. This can only be done by disconnecting the current console user and restart a new console .
Not a proper way....but the only possible.
Vista is still a big challenge, as service will not work at all.
Natural, security....
A service run as system, while vnc as app takes the user permission.