Conrad Sallian's community posts

We are excited to announce the public beta of the new Windows version for Remote Utilities and Remote Utilities Server. Check out our blog post to learn about the latest features and improvements.

Download beta:

- Download all modules (zip, 119Mb)
- Viewer (.exe, 31Mb)
- Host (.exe, 26Mb)
- Host (.msi, 26Mb)
- Agent (.exe, 23Mb)
- RU-Server (.exe, 17Mb)

We encourage you to download the beta, test it out, and share your feedback and bug reports in this thread. Your input is invaluable in helping us improve the software. Thank you for your participation!

Hello,

Could you please send us the license key via email at support@remoteutilities.com? Thank you.

Hi Vasilis,

Thank you for your message. We have replied to you via the tickets.

Константин Братулин wrote:

Do you mean that I don't have to buy 2 Started licenses for two techs, but instead I buy one Started license that includes the ability to connect for two techs?

The number of 'techs' that you buy for a license determines the alllowed number of concurrently working Viewers. For example, you have two techs each working from their own workstations, and they need to work simultaneously. For this scenario you need a 2-tech license (Starter if you need to control up to 20 machines, Mini for 50 machines and Pro for unlimited).

If there's just one tech OR multiple techs who don't work simultaneously, a 1-tech license will suffice. It can be shared between techs.

Please, not that a 'license' is not the same as the 'license key'. For example, if you order a 2-tech license you receive one license key which is good for 2 techs. Each tech will use this same license key.

Hope that helps.

Hello,

OK. And with this license I can connect to all PCs in my organization, but simultaneously only to 20, right?

Yes, you can. Strictly speaking, there's no limit to one-to-many simultaneous connections in the program per se. It's a cap set by the license, in this case - Starter (20 address book items max).

But how do I technically make it so that in my absence another tech can connect with my license?

You both register your Viewers with the same license key. If it's 1-tech Starter license you are after, only one person can work with the Viewer at a given moment. I.e. there's no limitation on how many Viewer copies you can register with your key, it's a limitation per concurrent use.

If it's a 2-tech license, two users can work simultaneously, and so on.

Hello Konstantin,

Thank you for your message.

Will after purchasing a 1 license, other operators, within the same network, can continue to connect to hosts using a free license?

Unfortunately, having multiple free licenses per organization would violate our EULA. If you don't have that many users who need a Pro license , you may consider buying a Starter license for them (or one multi-user Starter license, e.g. 5-tech Starter). Yes, they will be able to connect to the same computes if they know access credentials.

Is it possible to use a PRO license for several operators simultaneously or one at a time?

This depends on the number of concurrent techs for the license. If it is a 1-tech Pro license, only one user can work with it simultaneously. The 2-tech Pro license will allow 2 concurrent techs, and so forth.

Are there any restrictions on updates to future versions?

Our updates and upgrades are strictly in accordance with our upgrade policy.


Do not hesitate to ask if you have any other questions.

Hello,

But checking all methods takes quite some time and if I remember correctly there always appears a window to enter the windows domain, username and password and it doesn't even get to single password. And therefore we're faster changing it manually.

Checking here means "go through the list in the order of priority, and select the first enabled authentication method". If 'Auto' is set and Windows Security is enabled on the Host, it will never offer to use the Single password authentication, because the latter is at the bottom of the list.

If you have multilpe auth methods enabled on the Host, but still want to use Single password for some connections, you should explicitly select this method in the dropdown menu in connection properties.

Hello,

What the 'Auto' setting does in connection properties -> Authentication is that it tries all authentication methods in the following order:

Custom (self-hosted) server security
Windows security
RU security
Single password

I.e. once the Viewer determines that the authentication method being checked is available, it uses it. That means that if you have multiple auth methods enabled, the ones that are higher in the list are used first.

For example, if you have Win Security and Single password enabled, Win Security will always be used. If you want to explicitly use a certain authentication method all the time, you should select it in the list.

Why can't we just set a default authentication method?
For IP and Hostnames it should default to windows security and when we try to connect to a Internet ID it should pick single password.

That indeed makes a good suggestion for inclusion in our wish list. The ability to choose a default authentication method depending on the connection type used, that is.

Currently we have to add the Internet ID to the address book and then right click and set it to single password every time.

You can use default connection properties too.

Hope that helps.

Hello Alan,

Thank you for your message.

You are absolutely right saying that VPN is another realm and a huge project on its own. Answering your question about security - absolutely all traffic that Remote Utilities sends and receives is TLS-secured, there are no exceptions. The type of license makes no difference in this respect.

It's only bad when I forget to close the connection when finished

If you navigate to connection properties -> Additional properties, you can enable the 'Log off connection on disconnect' option. If you close the active Full Control window - which is probably what you do when you finish task - the program will also log you off from the remote PC. Currently, because you are still being logged on to the remote PC even after an active session, the alert message is shown.

Hope that helps.

Anthony Pidden wrote:

We could manage a remote session, but it might have to be an assisted view-only session unless we have an agreement in-place, due to the nature of the data we hold and the access this system provides.

We are UK based (GMT+0).

Hello Anthony,

Sorry for the initial confusion and misunderstanding. Currently, RU Server doesn't offer ipv6 support. We will add ipv6 support in the very next server update.

Thank you for your patience.