Conrad Sallian's community posts

Strictly speaking, our Host is also a "server" (as in the "client-server" architecture). It's only that we call it Host to distinguish from RU Server.

RU Server package consists of two parts - a client, which is the Admin Console and the server, which is the actual service running on the computer where RU Server is deployed.

Usually both parts are installed during RU Server installation. Then you can administer the service from the Admin Console - i.e. connect locally from 'client' to 'server' on the same machine. However, you can also connect from Admin Console installed on another computer. Before you do that you should configure access to the service in Configuration -> Administrator console tab ("allow TCP/IP connection"):



That said, for remote management of RU Server it is more practical to just install Host on the RU Server machine connect from the Viewer and then run the Admin Console on the server machine. That's at least how most users use it according to what we can see from the feedback.

My two cents to the discussion.

Hello Trent,

The 7002 release is scheduled for tomorrow (Wednesday).

Jimmie Noble wrote:

Where do I find the version number of the host on my computer?

Hello Jimmie,

On the Host computer - right click on the Host icon in the system tray and select "About Remote Utilities".

You can also check the Host version remotely from the Viewer side. In Viewer switch to Details view (View -> Details) and check the "Version" column. For this method to work you must log in to the remote Host at least once so that it can communicate its version number to Viewer.

Hope that helps.

Hi Cosmos,

I found that the internet-id is embedded in a binary key, HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host\Host\Parameters

Yes, Remote Utilities Host keeps its settings including Internet-ID in the registry.

As far as I can see this is an XML file encoded into a binary reg key. Which would be the fastest way to change the internet-id part of this key to a value of my own (specifically, insert the id of the old xp system)?

It would be more work to do. A better solution would be just to export and then apply the entire key (.reg file) with Host settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host\

than to individually change host paraemeters via the registry (this could end up in unexpected behavior).

Hope that helps.

Hello Keith,

1. You can access Host v6 from Viewer v7. But some features may not work (e.g. File Transfer was re-written from scratch and requires Host v7). Full Control and View mode should work normally.

2. Yes, we recommend updating Hosts in groups, not all of them at once. This has nothing to do with Remote Utilities per se, it can be applied to any remote access software. Programs run in an environment and there are many external factors, both computer and human. A typical example is antivirus software that decides for you which programs you must and must not install/run.

3. Unfortunately, no. We cannot test every possible configuration. But we read any feedback and try to fix bugs exposed during such use.

I also don;t see any indication sin the release notes, but has there been any changes that could have positive impact on accessing active laptops with closed lids ? currently, using legacy-mode "sometimes" works, but not always....

Did you have a chance to test v.7 and see if this issue occurs?

Hi Cosmos,

What I wanted to ask is whether 6.10.x portable viewers can work ok with the new relay and the new hosts. If they could, I could postpone viewer upgrades till I'm finished with all the host upgrades on my net.

This is not recommended. We advise that you first update your Viewers and Server, and only then - the Hosts. That is the Hosts must be updated the last of all.

Hope that helps.

Hi Jaydn,

Thank you for your message.

If you mean the Agent module, it keeps its settings in the registry despite it being a module for spontaneous support. The portability that you describe was never meant to be a use case for Agent. Users are supposed to download Agent on the computer where they run it.

However, you can still achieve what you want. Just create your own pre-configured Agent using the MSI Configurator. You can set the single password in the last step of the configuration process.

Hello John,

So, what solutions exist for essentially unattended upgrade from Agent to Host?

The ability to "convert" Agent to Host (with proper admin credentials required, of course) is on our roadmap.

Hi Cosmos,

1) Yes, of course.

2) In Step 4 of the configurator you select "Skip settings configuration". This will keep your current Host settings intact and only update the program files.

As always, we recommend that you never update all your Hosts at once, especially when a custom installer is involved. Instead, tread carefully and test the update on a few hosts then proceed updating clearly defined groups to ensure that everything is under control.

3)  

I presume that on the relay, the new version will keep the configured users and settings

Yes, but before you start RU server installation create a backup of your existing RU Server data files and registry entry just in case. See this KB article, the section "Where does RU Server keep its data and settings?".  

In the coming weeks we will update the portable viewer software of our teleworkers. Is that ok, or do you expect this rollout to be problematic due to incompatibilities?

If you could wait just a couple of days you can download and use/deploy version 7.0.0.2. This version will have some annoying bugs found in the 7.0.0.0/7.0.0.1 fixed.

Hi James,

You should update your Avast signature database. Avast assured today us that detection is no more:

Hello,

Thank you for reporting this false positive.

Our virus specialists have now cleared its reputation in our database.

With URLs this change should be instant, but it might take up to 24 hours with files.

For future reference you might also find the following article to be useful: Avast Clean Guidelines.


Best regards,

Avast Customer Care