Conrad Sallian's community posts

Hello Dan,

Thank you for your message.

Unfortunately, modern antivirus software is incapable of distinguishing between good and bad software. They prefer to be on the safe side and block just everything which even remotely resembles an "intrusion attempt". They couldn't care less about the fact that their "detections" wreak havoc on the work and infrastructure of their own customers.

I recommend that you use this form on the Symantec website to report the issue. We will send a false positive report through that form too. The more reports they receive the better chance that they fix this false positive issue sooner.

Let me know if you need any other assistance.

Hi Derek,

I know of similar self-hosted options, where the software licence is $800.

Yes, each company sets its own prices as it seems. Perhaps, that specific company has large marketing budgets that can bring in a lot of customers who can afford to pay for a self-hosted option.

I suppose my question was more like: "From who and how come your profits?"

Our profits come from our sales. We sell commercial licenses for Remote Utilities, specifically Starter, Mini, Pro and Site. I'm sorry that I wasn't clear about that at first.  

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

Hello Derek,

Thank you for your message.

In what way are we customers paying if it is not in money?

Free license users are helpful in several ways:

- They help spread the word about Remote Utilities.  
- Many of our free license users end up purchasing a commercial license when they exceed the free license limits.
- Reporting bugs in the software and giving us ideas on improving the program.

Who and how is supporting this company? Is it only large-scale users who pay for more features/computers?

The only source of our financing are our profits. This is boring and not something TechCrunch or Mashable will be willing to write about :)  

Also, why is the self-hosted server software free?

Because the competition is fierce.

You'd think we'd have to pay for that, at least, because if we are not using your software for the internet-ID connection, you don't have our information on your servers (but we hope we can trust you anyway?)

Information that goes through our ID servers is encrypted. We cannot read it anyway. And yet, we also provide the self-hosted server for companies who need even more security and who cannot trust just any third-party developer or cloud hosting provider.

You can also refer to this FAQ page, and specifically the second question on that page. It lists all possible cases when Remote Utilities may contact our servers (e.g. update, Internet-ID connection etc.) and all of them can be either disabled, or replaced with self-hosted alternative such as the self-hosted server.

Let me know if you have other questions.

Hi Michael,

Ok, no problem. Feel free to update this thread if you encounter this issue again.

Thank you.

Hi Michael,

I wonder what error that was. Do you have a screenshot or description?

The certificate should be valid. Although it is a regular Code Signing Certificate, not an EV (Extended Validation) one used in our vanilla version, but Windows still shouldn't be unhappy with it.

Hello Michael,

Thank you for your post.

I have successfully created MSI files using the Configurator with the Host installed in the past. I tried today and it failed with a warning dialog that states "Remote Utilities Host was found on this computer. It must be uninstalled.

Please, check if there is a registry entry

HKEY_LOCAL_MACHINE\SOFTWARE\Usoris

. If so, feel free to delete this key restart the Viewer and try configuring again.

By the way, we recommend that you use the Online configurator option over the Legacy option. With the Online configurator option your Host installer will come signed with our digital signature. Besides, this ensures that the input Host file (the vanilla Host fed to the configurator) is the correct file.

Hello Alan,

I'm really sorry for that. I would only be happy to be more specific but this is all I know.

Thanks!

Hello,

We have checked this case with the screensaver starting on the log in screen, but didn't find any anomalies. Here is how we tested:

1. Host - Windows 10. Screensaver enabled with a 1 min interval,  and starting on the log in screen.  

2. Viewer - Windows XP. "Remove wallpaper" and "Lock workstation on disconnect" options are enabled in connection properties.  

3. When connecting to remote Host in Full Control mode, wallpaper is removed. When closing the Full Control mode  (without logging off the Host in the Viewer) , the screen is locked. Launching the Full Control mode again - the screensaver is shown. Need to click on the screensaver screen to invoke the log in/unlock screen, then entering into the system - the wallpaper is removed.

4. The same as above only this time not just closing the Full Control mode but also logging off the remote Host. When logging back on again, starting the Full Control mode, going through the screensaver screen and unlocking the machine - the wallpaper is removed.

Could you confirm that you do the same? By the way, what operating system is on the Host and Viewer side? Also, please make sure that you update RU Host and Viewer to the latest version (currently it's 6.8.0.1).

Looking forward to your reply.

Hello,

Thank you for your post.

Perhaps you were enabling the "remove wallpaper" option from within the session window (i.e. clicking on the gear icon on the toolbar in the Full Control mode).

If this is so, try to permanently disable the wallpaper for this connection in your address book. Right click the connection icon in the address book, select Properties:



then navigate to the  Additional Properties tab, select "Remove wallpaper" checkbox and click OK to save. The wallpaper should get removed now each time you connect to that remote computer.

Hope that helps.

Hello Alan,

We will do our best to release it as soon as possible. Currently, we are also working on 6.9 update which will provide some significant changes and improvements to the Host authorization system and also introduce a 2-factor authentication.