Conrad Sallian's community posts

Allan Hall wrote:

Tried to find this feature today and could not. Still working on it?

Allan

Hello Allan,

There is a check box in the Agent window called "Run after reboot":



You need to check that and then reboot as normal - either directly using the Windows Start menu -> Restart etc. on the remote desktop, or by using the Power Control mode. If the above mentioned checkbox is set, the Agent should restart after the reboot.  

Hope that helps.

Hello Larry,

Currently, we see that the only solution would be to automatically adjust capture settings when such "animation-rich" Windows elements are viewed remotely. This feature is planned for one of the future updates.

Thanks for the info, Ian! We'll check it out.

Looks like it could be a glitch in 6.7.0.1. We are currently preparing 6.7.0.2 update, and it will be most likely released today. The problem should be fixed in that update.

Hello Ian,

Thank you for your message.

And what interface language do you use? Or did you get the message right when you launched the Viewer?

Hi Allan,

Occasionally however I get an end user that I know will need help later and it would be nice to be able to install the host at that time right from the agent. Glad it is on the wish list!

By the way, the current workaround would be just to leave (not to delete) the Agent after the first session and have the user run it when they need another session. If the Agent isn't deleted from the computer, the ID and password stay the same, and so you don't have to update your record in the Viewer address book.

This workaround is good, of course, only if you don't need a truly unattended access (i.e. without a remote user ready to run the Agent for you). Here is a blog post on the Host vs. Agent subject .

Thanks for a great product and particularly for all the affordable licensing options you have. That really helps out the small business guys.

Thank you for the kind words!

Hello Allan,

Thank you for your post.

I attempted to install host while connected through agent the other day and it did not work, kicked me off. I tried to search but didn't see an "approved" way of installing the host from the agent, what am I missing?

You are not missing anything. Currently, "converting" Agent to Host isn't available. So in order to install the Host it's better, to choose the "conventional" path, that is prepare a one-click installer, and have someone run it on the remote PC when they close the Agent.

However, the converting feature is on our wish list and we'll implement it some time soon.

PS. Just bought my license, really enjoying the product, looking forward to a faster file transfer folder browsing experience you all were talking about back in December.

Thank you for the order! We will do our best to re-write the File Transfer mode later this year to make it quicker.

Don't hesitate to ask me if you have other questions.

Hello,

Thank you for your message.

I have played with previous releases and noticed that after an installation I get a popup notification that RU was installed successfully with an OK and Tell me more button. Can that be removed?

This message only appears when/if you select "Generate internet-ID" option during MSI Configuration, install the Host and then connect to the Host the first time.

In order to remove the message, you need to click on the OK button while being physically at the remote PC. The button won't work if you click on it remotely, i.e. through a remote session.

Any suggestions on removing this? And also providing an option to disable this in the future?

If the first connection is established from a Viewer registered with a PRO or SITE license, the message is not shown at all. Please, check out our license comparison.  See "Full silent install" at the bottom of the table.

Hope that helps.

Hi David,

In the case of [censored] there is a "console 9 character ID" that is assigned to the "machine itself", and if you connect to that then it's as if you are sitting at the console of the server. However, each RDP / session (or user profile) also has its own separate 9 character ID. I think it is assigned per user profile?

With Remote Utilities you connect to the same ID and then simply switch to a desired terminal session on the toolbar ("Terminal user switch" icon).

However, if you want each terminal user to have their specific instance of Remote Utilities agent running (and thus have a dedicated connection entry in tech's address book for each terminal user), then you should use Agent instead of Host. Users don't have to re-download the Agent for each session though - they can leave it on their computer and run on demand. Here is a blog post about the differences between Host and Agent.  

I want the same functionality in RU - I want to do a support session with them on their desktop. I *don't* want the RDP behavior of taking over a session and kicking the exisitng user off their session.

That shouldn't happen.

I think TV's way of doing this only works for Internet 9 character connections, not for direct IP connections, because the server will (usually) just have one IP for all users?

An IP address belongs to a network interface rather than to a specific application. I'm no expert in virtualization, but I can guess that it's still possible to set up virtual IP addresses on the same subnet (and hence accessible the same way the server can be accessible) for terminal users/sessions. More on the subject.

Hope that helps.

Hello David,

Thank you for your post.

Remote Utilities allows you to switch between existing/running terminal sessions if that is what you mean.  However, Remote Utilities itself cannot act as Microsoft Terminal Services and create sessions.

Hope that helps.

That sounds interesting, thank you both for your input. We will try to investigate the issue. Perhaps there is something we can do about this.

By the way, a new update has been released today (28 June, 2017), version 6.7.0.1. You can download it from here https://www.remoteutilities.com/download/ . You may try to update Viewer and Host and see if the issue persists with this version too.

Thanks!