Kim Dawson wrote: All day long, the pop up for this host comes up every few minutes to tell me it's online.
Yes, that. That's exactly what mine does. All day, computer online pop up, computer online pop up, computer online pop up. The PCs at the same location with the older version host/viewer do NOT have this issue. The new version simply isn't as stable as the old version.
This happens to me all the time! The old versions of remote utilities are good, they never drop. [censored] never drops, [censored] never drops, [censored] sharing never drops, Remote Desktop never drops, but the new version of Remote Utility drops ALL THE TIME! It is about where I can't use it anymore. This is over very solid network connections. The new Remote Utilities simply isn't stable. I have tried this from multiple locations, to multiple locations. It is always dropping.
I can't reproduce it 100% in a normal way, but I can force it to happen if I hold SHIFT while I minimize the session and then click into another program, and then release shift. The client doesn't see me release shift that way. When I go back to the session, shift is still active.
Although that's not an exact replica of what really happens, maybe something similar to that is happening with the ALT key sometimes when you alt tab back into the program sometimes.
I don't know if that example helps or not, but it is way to force a similar situation.
This happens all the time. When I Alt-Tab out of the session to another window on my computer, when I go back to the session, the Alt key is stuck down, or the shift key is stuck down. This happens multiple times per day, its horrible. I have to completely exit the viewer and the entire program, then go back into it. Multiple times, everyday, and it happens on multiple computers.
My local computer is Windows 10. The computers I connect to are various, XP, 7,8,10.
It is NOT sticky keys. I don't push the same key 5 times and activate the accessibility features.
It's like remote utilities doesn't realize that the keys have been released.
When the host is a single monitor, I can use stretch mode on the viewer and then simply resize the window to zoom out to get a good size of the remote screen on my desktop. When the host is multiple monitors though, and I want to see all the monitors, the stretch mode is really small and I can't zoom in much because it is so wide, it hits both sides of my local monitor... and if I use normal mode, it is way too big and I have to scroll a lot to see everything. I need to be able to control the zoom so I can get somewhere between the 2. I need it bigger than stretch mode, but smaller than normal mode.
In VNC, I could use the + and - keys at the top to quickly and easily zoom to whatever size needed.
Windows is Windows 10 (but I am pretty sure Windows 8 is the same issue).
Windows 8 and Windows 10 have "SmartScreen" filter that throws huge warnings when running programs that it doesn't know if safe or not. To actually run them, you have to choose "More Options" and then choose an option to allow to run the program anyway.
For me personally, I don't care. Remote users, however, are not as willing to do this because if Windows says it is dangerous, then they question it.
This crosses over to the other post I made about switching from agent to host. They can run the agent (unmodified) without any warnings, and then I can upgrade through viewer to a modified host (without any warnings). However, that is when the ID gets changed.
So, if I have the remote user install the unmodified host, I have to walk them through the install options and then how to create an ID after that. If I do the agent-to-host, I still have to have them tell me the initial ID/pass (which is good because the agent puts it right in the center of the screen), but then I have to have them go into the host after upgrade and tell me the new ID.
I'm trying to simplify it so they tell me the initial ID/Pass from the agent that pops up in the center of the screen, and then, if needed, I can switch to host without having them have to go into host and get the new ID, and without them having to install modified host themselves and have the big windows warnings.
One workaround that I have played with is installing the self-hosted server at my location, and putting that address into the modified host that I use to upgrade through viewer. That works because then I can see the new ID inside the server as soon as the viewer does the remote upgrade. However, that seems like quite a lengthy workaround just to get the ID.