SC as a service and autoreconnect

[superwopguy]

It would be absolutely amazing if you could add some simply functionality to UltraVNC SC.

Basically just add the following 2 features that regular winvnc has

The new pathched version of winvnc allows both these switches
-service
-autoreconnect ID

Can you please add these switches also to UltraVNC SC

That way I will simply run the UltraVNC SC executable just once and never have run it again. Because it will be a service.

By the way, UltraVNC RULES, there is no product out there that can ever compare. Keep up the good work.

[Rudi De Vos]

Service:
Service was removed from SC.

1) You can only support the admins: service require admin to be installed.
2) Security , when you run as service, you are "local system"
You can do everything you want, unless the person who run SC 100%
trust you. In most of the cases, company's will give you user access, but not "local system access". They would not allow to run you SC on there system.
3) Running as service you have trouble with RDP and "Fast user switching"
As application you can even give support to someone working in a remote RDP session.

There are some disadvantages for not running it as service, but the security risk is to high. Would you allow and extern support company to have access to your SAP server knowing they have access to all...

[superwopguy]

I wanted to use regular winvnc service as a reverse connect. And that works fine, I'm Using "Autoexnt.bat"

net start winvnc
"c:\program files\ultravnc\winvnc.exe" -autoreconnect ID:1234 -connect 192.168.1.101::5800

But then I have the problem of security. No password is required to connect because both computers are establishing the connection. Maybe if you could add a switch to the winvnc service requesting a password.
For Example:

winvnc.exe -password foobar

The reason why I was going to run UltraVNC SC instead is because I can hide the rc4.key within the executable. This makes the connection much more secure because only people with the rc4.key file can remotely control the computer. Otherwise with regule winvnc the rc4.key is exposed in the directory or the registry. And also, I would need UltraVNCSC to autoreconnect as does the regular winvnc. If both these products could somehow share these switches I would be set. Can you please help me. I need to be able to connect to approx. 200 separate workstations through a repeater. Each workstation would have there own unique ID#. I can do this with your wonderful product assuming the repeater can accept 200 workstations waiting for a connection. The only problem I have with regular winvnc is that I cannot set a password that must be entered as the viewer is connecting to the server. This is the only problem I have with UltraVNC. Please help, Please suggest a plan for me. And thank you so much for developing the best product in the world.

[superwopguy]

Sorry I forgot to add that if i had to choose I would rather use UltraVNCSC. Could you please add the following switches to UltraVNCSC if possible.

-service
-autoreconnect ID
-password

That way I would just have to execute the UltraVNCSC executable once and never worry about it again. And I would have 2 modes of security. 1 would be the password and 2 would be the rc4.key file.

Thanks you so much for all your hard work. If you are not willing to release UltraVNCSC with the -service could you please atleast add the autoreconnect ID switch to the UltraVNCSC. Thank you so much.

[Superwopguy2]

If everything I'm asking seems overwelming then all I ask is one thing. This one thing would add so much security to reverse connect. All I ask is that you add a password switch in the regular winvnc reverse connect.

For Example

winvnc -autoreconnect ID 1234 -connect 192.168.1.101::5800 -password foobar

PLEASE add the password switch to the regular winvnc commands.

Thank you so much.

[redge]

The reason why I was going to run UltraVNC SC instead is because I can hide the rc4.key within the executable. This makes the connection much more secure because only people with the rc4.key file can remotely control the computer. Otherwise with regule winvnc the rc4.key is exposed in the directory or the registry.

sc is not more secure with rc4.key because the file rc.key is unziped to folder %temp%

[supewopguy2]

Is it true that we can add a username and password to the Single Click, so that the viewer has to input the username and password before taking control? In that case I would prefer to use Single Click unless these 2 features can also be added to the regular reverse connect of winvnc.
I am requesting for 1 of these. Please tell me when this can be done.

1.) Please add a password switch to the reverse connect of the regular winvnc command line.

OR

2.) Please add the autoreconnect switch to the UltraVNC Single Click

And

3.) If possible Please add the service switch to the UltraVNC Single Click