Community

For those of us that have been using the free corporate eval use license for the past DECADE or so...  Here is what changed, what I encountered, and what to do to EASILY fix this:

TERMINOLOGY:  
HOST or SERVER => SLAVE, PASSIVE software.
RU's def for their software installed REMOTELY, on your TARGET's PC, i.e., your client's PC (friend, relative, customer, "support target", dumb friend, etc). you want to "view" or control.  (Note, you could also have this software component installed on your PC that is used to control others' PCs.)

VIEWER = > CONSOLE UI to CONTROL "host", or slave, passive PCs.
RU's def for their software installed on YOUR PC that is used to remotely connect to many other hosts.

MY experiences:
-- I updated MY PC's "viewer's" software to 2.6.2.0 some time ago, as it had been nagging me for months, (November, 2024).  No apparent issues, except whenever I connected to the remote "host", RU's local viewer software complained that the remote client's HOST RU software also needed an update.  

I finally relented a few weeks ago, and used the REMOTE method of updating the remote PC's "host software".   It seemed to do the update fine, but I didn't reboot to test the connection at that time.  I lost power several times today and the remote PC (10 feet away), rebooted today.  My PC's laptop still had the "viewer" open, so I simply reconnected to the remote PC, and logged back in successfully.

(I wanted to only update at least one remote "host" PC that was 10 feet away, in case I needed to use the keyboard / console to fix any RU connection issues.  I'm very cautious about this, since if you experiment around with updating a PC 100 miles away, with NO ONE at the other end to intelligently and patiently make adjustments, you might lose all connections until you DRIVE there personally to fix the problems.  5,000 miles away??  OK, then FLY there first.)

Messing with my local PC's viewer software, I accidentally closed the viewer, and reopened it..  Whoops!!  "Please install a VALID license to use the VIEWER".  Hmmm, so for the next two hours, I puzzled out my problems.  I'm super cautious, since I could never update one remote PC's host software, 100 miles away.  I tried to apply the OLD License.TXT file that I was using in 2022.  I renamed it "OLD-License.RUlicense" and imported that file.  It did not work.  I finally relented and got a NEW license by clicking on it, in the Viewer's help screen, which opened RU's website, and I applied for a new (replacement) license, which was then emailed to me as an attached file.  

I installed that new file into the viewer on my laptop's PC, and then tried to connect to my remote PC's "host" RU software.  Would it connect??  Or, as I feared, insist that I also install that new license file on the old client's PC, running the RU host software??  Shocked, I was happy to see that it connected, and I would NOT have to do anything else to either my laptop or my PC, which was 10 feet away.

More importantly, the next time I connect to the PC 100 miles away, I will try to do the REMOTE "host" software update for RU.  (NOTE that there might be false positive malware issues caused by Microsoft, or other security vendor's products that could prevent an update! -- See elsewhere here in this forum to verify.)

In short, updating the LOCAL VIEWER's PC with a new license, should not affect your remote client's HOST software, or the connection to their PC's.  The "new" license is for 10 "hosts" which you connect to using your local RU viewer software.

Thanks to the RU team..  Except for this mandatory update, the software is bulletproof.  I still wish there were an easy way to make the host's Windows clipboard's auto-synced as active/disabled, AND the state of this feature.  It's the one potential security risk for the client's PC, since they may not be aware that YOU will be capturing anything that they clip, while you are connected to their PCs RU host's software.  The emailed license came with a request to submit a review for the RU software, which I intend to do later, as a token of appreciation and thanks.

Conrad Sallian wrote:

Hi Alan,

Thank you for your message.

I still wish there were an easy way to make the host's Windows clipboard's auto-synced as active/disabled, AND the state of this feature.

It is available. Please, see Settings for Host -> Other -> Disable clipboard transfer. You can either disable it for the Host to Viewer direction, or for both directions.

Y --- I know it is there, but I think this is one of the most potentially dangerous features, and needs to be more prominent as well as easy to change.  Just as it is important to know if someone is watching your PC while someone from support SEES your PC, it is even MORE important that I know IF they see it, (which they'd have to be quick to capture my login to something), or if like many do, COPY and/or PASTE my PW to a site, AND NOW, without realizing it, my support guy has a copy of that PW.  Even if HE doesn't do anything with it, that PW is now on his PC.  If I was running a support company, I'd shudder to think of a bunch of employees that were accidentally capturing PW's.  Remember, there are also excellent reasons why I NEED to copy or paste to / from a client as well.  

I have another FREE program I use and love, MYPhoneExplorer, which I use to SYNC my Phones and PC's.  https://www.fjsoft.at/en/   They have FIVE options I think, (or should), to send clips ONCE or ALWAYS:  

• Take my PHONE's clipboard CONTENTS and SEND THAT to my PC
  
• USE my PHONE's clipboard and SEND ANYTHING I CLIP, including my current contents, to my PC
  
• Take my PHONE's clipboard CONTENTS and SEND THAT to my PC
  
• USE my PC's clipboard and SEND ANYTHING I CLIP, including my current contents, to my PHONE
  
• Take EITHER my PHONE's OR my PC's clipboard CONTENTS AND FUTURE CLIPS, and SEND THAT to my PC OR my PHONE
  

I'd think my preference would be for you to just SHOW the STATE, and then add an easy way to set those parameters, (Not, in general settings).    Having it set in any specific way, ensures I won't use it selectively, and will likely either capture everything, or not be able to transfer any clips without a hassle when I need it.