winvnc -noconsole

[redge]

winvnc -noconsole

Please add it to winvnc 1.0.3
this is big great feature stop the infame black screen monitor of terminal server console. (known as remote desktop connection)

Hope almost everyone want it.

[rmoller]

Sorry, but it is not clear what you want to accomplish.

VNC is typically used to access the console, and it works as long as the console is also session 0.

What would be the desired benefit of -noconsole? What would you expect to see?

As VNC works right now, what you get is the screen from session 0, which is normally connected to the console. If mstsc.exe /CONSOLE has been used against a server, VNC will still server the now disconnected session 0 , i.e. the black screen. The console will be instead be connected to another session, say, 3. Use MS Windows command line utility qwinsta.exe to query actual sessions.

It is a limitation in Windows, that all services, Winvnc included, run in session 0. To be able to serve another session than session 0 requires that the Winvnc service cooperate with a servicehelper process running in that other session.

One could propose that all Winvnc -servicehelper sessions register themselves with the Winvnc service at startup. The Winvnc service should then route the incoming VNC client to the console session instead of session 0.

[redge]

play with XP Fast User Switch (FUS) and you can understand the problem of multi users sessions. (local and remote without disabling ms remote desktop

I see realvnc enterprise added -noconsole to winvnc for users able to switch between multiple users sessions WITHOUT black screen (local and remote from same or different remote access computers.

winvnc running as service -noconsole

all connections working at same time
vnc1 able to see session1 of user1 (local)
vnc2 able to see session2 of user2 (remote)
vnc3 able to see session3 of user3 (remote)


without any issue (just disconnect and autoreconnected to correct session requested, not just rejected or redirected to welcome screen.