There are a couple of unattended machines that I access regularly. Rather than visiting the the web hosting page, I would prefer a "one click" option. Is there any way to achieve this?

Also, I realize that our ScreenConnect server mediates at least the initial connection between "host" and "client". (BTW, I think you've got those two words backwards. <g>) Is this only to exchange IP addresses when the session starts, or is there some other reason? I ask, because the IP addresses of the clients will be known, and could be stored as part of any "shortcut". Would skipping contact with the server make things any faster to get the session running?

Thanks in advance for any help!

Mike Hanson

I have control of the server, so I could theoretically change the web.config, if you think that's the best route (and aren't concerned about side effects). For example, if this was the "global" web.config for the entire server, I would consider that to be a negative side effect. :D

As for browser, I'm normally a FF user, but your stuff doesn't play nicely with FF+NoScript. Therefore, I've been using Chrome in my testing today. I've currently got a shortcut to take me directly to the hosts page, but then I need to choose "Unattended" then click on the appropriate machine. Then I have to wait for the various hand-shakes, etc. I'm used to using VNC, which makes contact in just a couple of seconds. It doesn't have to be that fast, but faster would be good. Once connected, your product works FAR better than VNC. :)

BTW, I'm just started a trial today, but I'm 99% certain that I'll be purchasing your product. I'm very pleased with what I see!

I've never had a problem with FF and no-script. Been running that setup since I first purchased screenconnect. You just want to make sure you have the latest MS .Net framework add-on installed to launch sessions from the browser instead of being requird to download and run the executable.

BTW, thanks for the video, Jake. It's similar to what I was already doing. Even so, it takes:

1. 5 seconds to get to the page showing the unattended clients
   
2. 10 seconds from the time I click to open the client, until the remote control window appears
   
3. 6 seconds for the remote control window to display the contents of the client's screen
   

That's 21 seconds, all accessing a local ScreenConnect server and a local unattended client. I'm assuming this will be even slower once I move my ScreenConnect server to an offsite server.

Contrast that with only 3 seconds to bring up the same client with UltraVNC. Since I know which client I want, I would like to be able to eliminate #1 above. Since the addresses of both my machine and the unattended client are known, I would hope that a good chunk of the mediation phase in #2 could also be eliminated.

IOW, if I could get that 21 seconds down below 10, it would be bearable, as the quality of remote control with ScreenConnect versus VNC would weigh heavily in balancing my satisfaction. :)

Please let me know if there's anything you can do to improve these numbers.

I clocked 8 seconds from launch to ctrl-alt-del, not bad for me although I do get the point of the request. Would be nice to be able to create shortcut's on the desktop to individual servers so it's a one click connect.