Conrad Sallian's community posts

Hi Ashley,

This is a side effect, unfortunately. And it only manifests itself when Windows 7 and older is used. Starting Windows 8 and higher a new monitor driver is used and hence no such effect.

Let me know if you have other questions.

Hello Ashley,

Thank you for your post.

Could be a bug. We'll check it out. What is the operating system on the remote and local PCs?

Hi PA,

By zip file you mean this one, the main "package" on the download page, correct? This is in fact just Viewer and Host zipped in a single file for convenience. You can as well download them separately below on the page.

Anyway, we'll take a look and contact Symantec regarding this issue.

This has already been implemented:

Self-hosted server solution page , see "Sync server role" section.

Also, you refer directly to the tutorial in the documentation about how to set up sync: https://www.remoteutilities.com/support/docs/setting-up-sync-server/

Hope that helps.

Hello,

Thank you for the suggestion. Did you try the Send message connection mode? Or are you looking for something else?

Hello Brian,

Thank you for the suggestion. I'll add it to our wish list.

Hello PA,

Back in December we received a response from Symantec, see below. They said they removed the detection but it could be that it is back again. We will check that out. Thank you for letting us know.  

In relation to submission 12613.

Upon further analysis and investigation we have verified your submission and, as such, the detection(s) for the following file(s) will be removed from our products:

File name: agent.exe
MD5: 6e8f173ac4686a122b2a599821f63d8d
SHA256: e41f8f603ef2292f8f9b18c40ae167243f4180fa835bbf67c3d533348d2e­7e32
Note: Whitelisting may take up to 24 hours to take effect via Live Update

Hello Brian,

Thank you for your post.

It is this very forum https://www.remoteutilities.com/support/forums/forum2/ .  We review user suggestions on a regular basis and many of them end up being included into our roadmap and sometimes even into our immediate development plans.

Hi James,

Starting version 6.5 an Internet-ID code is unique for each PC. It is always the same. For backward compatibility, if you upgrade older Hosts to the new version their Internet ID is not changed so that you can still connect to them using the old ID. However, once you manually change the ID on those Hosts it will change to a new value and will stick to that value from then on.

BTW, let me explain what happened in the situation described by the initial post in this thread. We resolved this through the tickets and the problem was the machines were cloned after the ID was generated. The Internet ID code is stored in the Host settings in Windows registry. If you install the Host, then generate the Internet ID and then clone the machine, of course you clone everything including the Internet ID code.

So the proper way to do that is to clone the machine after you install the Host but before you generate the ID. In other words,the ID should be generated once the machine is deployed.

Let me know if you have other questions.

Hello Paul,

Yes, indeed strange. Maybe we can have a remote session then then next time you are in front of your Host PC? Could you please send a support ticket and I'll instruct you further.  

Thanks and Happy New Year!