Conrad Sallian's community posts
[FIXED] Remote connection drops after upgrade to 7.0 - and other issues
Thank you for your feedback. We are currently examining the issue. Could you please send us your host logs to support@remoteutilities.com ? You can locate the Host log in C:\Program Files(x86)\Remote Utilities - Host\Logs\
Thanks.
Version 7.0.0.0 can't add old license key
Thank you for your feedback.
We didn't intend to trick anyone. Beta version is, well, beta version. It can be any number. And initially we indeed wanted to make it another minor release. But then it were a lot of quite serious improvements so it could easily become version 7. That said, there is 7 years span between version 6 and 7 - unlike our competitors we do not release a major each and every year whether it's justified or not. Otherwise there would already be version 14 :)This is really disappointing. I really wish you called your 6.12 beta version 7.x instead of tricking us into thinking it was another 6.12 release. I wouldn't have bothered testing the betas if I knew this to to be the case. "
And we made the final release before the end of this month, just as we promised.Further, when someone inquired about getting a new beta update before March 1 expiry, this critical fact was neglected and downright misleading: "Yes, the final release will be made before the end of this month.
Your address book will remain intact. Besides, there is address book backup enabled by default.I just installed the RU Server 3.0 and then realized with the version bump to v7, I would need to pay for an upgrade. So now I'm stuck on a mix of 6.10.x's, beta 6.12's and a RU server running 3.0 I need to downgrade to 2.7 release. I really hope it doesn't bork the address books or settings.
As for paid upgrade - our upgrade policy has always been very precise on this point. We exactly follow this policy.
We'll fix that page now leaving only version 6.10.10.0 avialble for download. Yes, the last minor update of version 6 is 6.10.10.0. And the server is 2.8.2.0.
https://www.remoteutilities.com/download/older-versions.php
So what is the last official 6.x release that I can still run? The 6.10.10 that is ancient and buggy that is almost 2 years old? I don't even know if there was a minor update put out after the last time I upgraded my license in May 2019. Can you update the page above to include them, please?
Thanks.
Version 7.0.0.0 can't add old license key
Server port management has become even more powerful. In a nutshell the improvement is described in this blog post. We'll also update our documentation very soon.
Version 7.0.0.0 can't add old license key
Thank you for your message.
That's wrong. When you install the server it migrates all the server settings from 2.x.x.x to 3.x.x.x. And it even supports connections from 6.x.x.x clients (here client means "client-server" architecture, so clients can be Viewers and Hosts.Server 3.0 is not compatible from the previous version 2.x.
Please, do not mislead other users.
No, it is not compatible. Why should it? We have our upgrade policy, we must separate 6.x.x.x users from 7.x.x.x. Besides, the new key format was necessary for implementing a new license key management system in RU Server.The 7.x client is not compatible with the 6.x license and the free license cannot be upgraded
Free license just needs to be generated anew using this form https://www.remoteutilities.com/support/free.php . We are not taking the right to use the free license from anyone.
This is also wrong. I personally tested the free license generation form immediately after the new release yesterday . And I've just tested it too. It works, generates and sends a key.rlicense file via email which is the license file for the new version.When I try to request a new one, the old 6.x version comes
No. You can generate a free license for version 7 and use it. If for some reason you still like version 6 you can keep using it too by the way (with the 6.x.x.x key, of course).Do I understand correctly that lifetime free license ends version 6.x?
For example, our paid customers who upgrade to version 7 will be able to keep their version 6 keys and use them, so they remain valid (not blacklisted). That is to ensure smooth transition from version 6 to version 7 in case there are hundreds of remote pcs. A customer may generate their 7 key now and actually upgrade only later, so we understand that.
Version 7.0.0.0 can't add old license key
Thank you for your order!
Yes, the message template contained the key in the body as well as attached. We updated the template so now it only contains the attachment.
It will also work that way, that's right. The .rlicense file is just a plain text file. However, Viewer 7.x.x.x no longer accepts text directly but only as a file with .rlicense extension.I then input that file to the license key dialog. It seems to have worked.
Let me know if you need further assistance.
Version 7.0.0.0 can't add old license key
Version 6.x.x.x keys are incompatible with version 7.x.x.x. You must upgrade your license key using this form https://www.remoteutilities.com/buy/upgrade-form.php
Yes, now there's a key file (key.rlicense) that you need to drag-n-drop to License key storage, or just open the Windows Open dialog and select the file on the disk and it will get added to the license key storage.7.0 seems to need a licence key file, whereas previous versions wanted a text string.
How do get my existing starter licence into v 7.0?
Hope that helps.
Remote Utilities 6.12 Beta
This release marks the end of the beta testing phase. Further posting in this discussion will be closed. Your posts are welcome in the main forum discussions.
6.10.10: Can I view both monitors over RDP?
Thank you for your message.
Are you sure this option is in RU's connection properties, and not RDP's client properties? When you run the RDP mode the program simply starts the Microsoft's own RDP client.
As an alternative you should use RU's own Full Control and View mode.
Host mouse disabled
The Host side user won't be able to control their mouse only if you enable Lock host's mouse and keyboard in connection properties as Polina mentioned above.
If you did NOT enable that feature, the Host mouse should be available to remote user. Please, note that during a remote session the remote user will be able to move their mouse but once you touch yours the mouse cursor will "jump" to the position of your cursor.