That's right, and that is why we notified our users beforehand.
Can you please set the access back up today so I can update the hosts???
I'm sorry, but we are planning to restore access no earlier than Thursday or even Friday. The users need to understand that it's not just a mere accidental downtime. We need to cover as many users who still have not upgraded as possible.
You are probably using version 5.x. A month ago we informed our users that they would need to upgrade to version 6 within a month until August 10, 2015. We also sent a newsletter to all free user e-mails that we have in our database.
You need to upgrade your installations to version 6. Don't worry about the free license - it's still free. You just need to upgrade the program.
In a couple of days we will restore access for another week specifically for those users of version 5.x who didn't upgrade yet and who can only remotely access their Hosts. A week will be enough for them to remotely upgrade their Hosts (we explain how) and then we'll terminate access to our servers for free license users of the version 5.x forever.
To sum it up - you need to upgrade to version 6, both Viewer and Hosts.
Is the migration as easy as installing the paid key and removing the free key from the key bank?
Exactly. You don't need to re-install anything. Just delete the free key from the License Key Storage and install the commercial key instead. This will make your address book capable to hold an infinite number of records.
Can I do all this remotely (a few of the remote hosts are physically a few hundred miles away)?
Remote Hosts have nothing to do with the registration process. It happens on the Viewer side only. Provided that you use version 6.x of course.
Io rX wrote: Installation of the RU-host. I first logon to the machines with an RDP-session when the client is connected with a VPN (user initiated). I installthe RU-host with elevated privileges and then get an ID from the RU. Restart the machine. The I try to connect with the RU-Viewer to the ID acquired I can't connect.
If you have a VPN tunnel why would you want to use the ID connection? This unnecessarily complicates the issue by routing the remote access via our servers. Instead, just use the VPN IP address (or dns name if any) of the remote PC for direct point-to-point connection.
I mean you can try to adjust printing options after you received the printing request from the remote PC but before you actually send it to the printer.
In the Remote Printing window, when you click "Print all pages" or "Print selected page" you are shown a dialog window that prompts you to select the printer. Beside the dropdown printer selection menu there is a "Properties" button. Depending on your printer model the properties can provide a whole variety of options for the printing outcome.
Well, that's not exactly the reason, although we you are probably right - a more general assumption is that we try to keep our default hosted service as simple as possible. You know, the more moving parts a system has, the more it is prone to errors and malfunction.
Whereas with RU Server we can experiment and add more advanced features. By the way, using e-mail for what you described is probably overkill. If both Host and View keep connection with the RU Server alive a notification (or a desktop alert) could appear right in the Viewer. So we'll give it a thought and adjust our plans regarding the RU Server roadmap accordingly.