Conrad Sallian's community posts

Hi Ron,

I'm also not sure the value of having separate login and logout concepts warrants the added conceptual complexity, but that's for another time.

The logging on and off feature, although may seem superfluous at first glance, actually serves its own purposes. First,  it allows to see remote screen previews on the thumbnails. Also, it is when you are logged in on the remote computer that you can remotely update the Hosts. Finally, it works as a "preliminary connection" - it lets you connect to a remote PC to check what's going on there before you distract the remote user from their work. For example, you may log in, take a quick look at the remote screen preview, see that the remote user is working and send them a quick message.  

There are use cases where a user goes fr om one connection icon to the next using the same connection mode each time. Mine is the other high level use case wh ere the user goes from one connection mode to the next while using the same connection.

I agree that for this use case the old system was faster.

To sum it up, this is a classic situation when there are two conflicting use cases, so the only way to resolve this would be to simply let the user decide. I will add a suggestion to our wishlist - perhaps we could implement an option that would allow users to set the desired behavior of the ribbon.

Hi Ron,

I understand what you mean. Previously (an update or two back) the behavior of the ribbon toolbar in the Viewer window was different. The buttons there were used to launch a connection mode for a selected connection right away. This was some sort of a duplication of what could be achieved by right-clicking on the connection icon and selecting the target mode from the menu.

So we decided to change the ribbon behavior so that it would offer an alternative way to run a connection mode. If a user has a connection mode they use most often, they can simply select this mode on the ribbon and then use a double-click on a connection to launch it in that mode.

Hope that helps.

Hi Ron,

I'm glad to see that you managed to figure out the issue. And all the credit should go to Benny for providing such a detailed and to-the-point answer.

As for the WoL in Remote Utilities, we'll definitely be improving it in the future. We have some suggestions on our wish list, namely to use one Host to wake other computers on the same LAN.

Hello Max,

I created a ticket.  Thanks.

Hi Michael,

We need to check this issue closer. May I move this forum thread into tickets, because we might need some log information from you etc?

Hello Michael,

Thank you for your message.

What country are you in? Specifically, where the Viewer and Host PCs are located?

Hello Ron,

Thank you for your message.

I have found people on the Web claiming to be able to restart a computer using WOL with other software from S5.

You can wake a computer with WoL but this has nothing to do with specific software. It's a matter of whether the network card supports it and set up properly. Here is more information https://www.howtogeek.com/192642/how-to-remotely-turn-on-your-pc-over-the-internet/

Hope that helps.

Hello,

An RSS Subscribe link is now available on the Release Notes page https://www.remoteutilities.com/product/release-notes.php

Thanks.

Hello Serg,

How does a user lock his terminal session's desktop?

The user locks their terminal session desktop the same way as a regular desktop during a Windows session - by clicking Ctrl Alt Del and selecting Lock.

User properties, Remote Control tab. Here's a picture: http://windows-active-directory.com/wp-content/uploads/2013/12/user-account-properties-remote-control-tab.gif

Remote Utilities only allows you to view what session/sessions there are. We cannot interfere with how Terminal Services work.

Hello Serg,

Thank you for your message.

If you have a permission to control the desktop of a terminal server - you can control the desktop of any terminal user, right?

This depends on what you mean by "control". In Remote Utilities you can switch to any actively running terminal session, but you can only view the desktop if it's unlocked. If the terminal user's desktop is locked (by the user) you won't be able to view it.

Active Directory have a user setting for this

Could you please clarify, what specific setting you mean? Thanks.