I can't have Viewer open all the time because I get too many "... is Online" pop ups. All connections are on broadband cable with no known network issues. Happens to different users. Popped up 3 times in the few minutes I've been drafting this message so far. (Probably over 10 popups during the rest of this drafting).
Make sure that you have version 220.127.116.11 installed on both ends (Viewer and Host). What you describe looks like an older issue (v 6.6 etc.).
The Last IP doesn't show the last IP that the user used, or were NAT'd behind. My best guess is that its one of your relay servers, but I don't know why you'd have a column dedicated to that when the last seen IP of the user would be more more useful.
Your guess is right. Actually this column was more intended for direct connection, rather than for Internet-ID connection. Still we already have this suggestion on our wish list and will soon make the IP address information to traverse through the server to the Viewer from Host and vice versa.
So now I think I should look into self-hosted to avoid this relay bounce.
This is a good idea. However reliable our public service is, your own self-hosted server will always win simply because you fully control its configuration (for your custom needs, such as ports etc.) and also because it may be located close to you which will significantly reduce the distance and number of hops the IP packets should travel.
For one Win10 machine, logging into it is SOOOOO slow. So many times I would get failed logins because the time between typing the password and the character registering in the windows 10 login box would be in SECONDS. No change after at least 3 version updates. You just can't work on lag that I haven't experienced since 1998.
The default screen size/ratio needs to be changed more often then not. With TV, I never have to mess with scaling, I just maximize the window or I snap to half screen. No needing to scroll vertical or horizontal bars by default except with Remote Utilities.
When you first connect to a remote computer the default value is "Normal", not "Stretched". However, if you change that value for a specific connection in your address book or on the fly during a session, the program will remember this setting for that specific connection/remote PC.
Also, you can set default connection properties that will be used for all newly created connections. In the Modes section you can set the View mode to your liking. Learn more about default connection properties on this page.
If I don't experience really laggy logins, I still experience laggy mouse movements. Was so frustrated when I had to use it today. I don't think that PC had a password set, so I don't know if that had the really laggy login and might just be same as issue 3 above.
Please, refer to what I said about performance and using the self-hosted server. Also, for the last couple of weeks we have implemented some fixes to our server software as well that should reduce the number of such issues. Finally, the upcoming version 6.9 is going to be more optimized in this respect so it should be faster both during the initial connection (authorization) and subsequent remote session (data transfer).
6. In previous versions, remote access broke by Windows updates, I believe. Requiring re-installation and manual intervention and lost headless access. But I'm guessing that was a hard lesson learned and will be prevented from happening again by installing the software in the appropriate places from now on.
This used to be a problem a few updates ago.
We are going to release version 6.9 very soon so stay tuned. Given some serious updates in this version we are going to run open beta testing first available for everyone.
We will do our best. But there are only two reports so far. It would help if either you or Espen (the topic starter) shot a video of the process on the Viewer side so that we can see exactly what happens when you run the Full Control mode. You can send the video (or the link to it) at firstname.lastname@example.org.
Yes, you can. First, let me tell you just in case that a "hardware-bound" ID had only briefly been introduced in one of the previous updates. But then we realized that it was a bad idea and cancelled that change. So currently the Internet-IDs are not hardware-bound. Even if two machines are perfect clones of each other their IDs will be different.
Here is how to get a unique ID automatically on each cloned machine with a pre-installed Host:
1. Configure your custom Host (Standard MSI) using the MSI Configurator. Make sure that you enable "Generate Internet-ID" option and send ID via email etc. on the 3-rd step of the configuration process.
3. When the Host has been installed copy the program files and export the Host's registry entry with the settings (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host ) and embed them into your system image.
The trick is that you install the Host but not run it yet (to avoid generating Internet-ID too early). The first run of the Host should happen when the cloned system runs/starts up the first time rather than during the image creation.
We are not sure what might be causing this, apart from possible routing/network issues on the Hosts' side. Do you have a system administrator on those site/sites who could check connectivity with your server and figure out the bounces?