I have setup 2 groups, A and B. Auto-logon has been setup for all connections in both groups. I open the Viewer application and go into group A. If I then close the application and open it back up, all of the connections in group A will automatically logon to the host, but if I then navigate to group B none of the connections will automatically login. If I then close the application again (being inside group B) and open it again, the Viewer will start inside group B and all of those connections will automatically login. But again, none of the connections in group A will be logged on.
Edit: Conrad, maybe you can move this over to the feature requests. It looks like the Viewer will automatically logon to the hosts, but only after what looks to be a 30 second timeout. It would be helpful if the auto-logon process happened continually in the background or at least is initiated once the group is selected.
Thanks for detailed info. We'll check it out and see if we can fix this.
David wrote: I'm not sure what this means because I searched through the manual as best I could - but I have one remote host that always shows up in the Viewer as being "Locked". I'm not sure what this means, but the Viewer cannot connect to this particular host at all. What does this mean?
The lock means there is a Host installed on the remote PC, and it's accessible via network, but you are not yet logged on into the remote PC. Here "to be logged on" means to log on using Remote Utilities, not Windows log on. More information is available in this feature description https://www.remoteutilities.com/support/docs/logon-and-logoff/
I'd like to add to this issue as well. When using the blank/lock screen, is there a way to turn off the local console from rendering the mouse pointer? It looks odd to see the mouse move around the screen on top of the chosen blank/lock screen. Additionally, when certain UI elements are chosen in the remote session (Windows Start menu, any combo box or list, and sometimes the minimize and maximize function), they will quickly flash on top of the blank/lock screen. This is also strange and will prevent me from using this feature only because I feel like it would generate additional calls from neighboring users that see this behavior and don't see someone sitting at the computer.
Thank you, David. We've added this to the list of things we should consider when improving the blank screen mode.
I would like to have something to put real notes in about the computer that I'm working on, future tasks, current state, or who it belongs to (this can change frequently at a few of my client companies). To expand on this further, it would be even better if this information could optionally be displayed in a column of the details view in the Viewer, and optionally included in the reports from Inventory Manager.
When the system goes back to the customer after repair RUT needs to be removed. It is solely to control is locally from my PC during the repair.
This makes things easier. You only need to install the Host, set access password and know the local IP address of the remote PC to be able to connect to it.
Does the Viewer get notified or automatically see the newly created PC if I run the one click created installer? I will look into this.
No. There is no central "server" to facilitate such notifications. You simply install the Host module on the remote PC and then create a new connection in the Viewer where you specify the IP address (or Internet ID if you use it) of the remote Host.