It would be a Good Thing if at the VIEWER end there was an exportable log of all viewer sessions. This would be very useful for billing support events, for example, or for documenting how much remote support a given user or computer required over time.
A full-fledged reporting system is on our roadmap. No ETA as of yet, unfortunately.
It would be a Good Thing if you offered different levels of "Small Operator" licenses for small quantities over 10 PCs. You could offer licenses at $199 for up to 20 machines, $299 for up to 40 or 50 machines, and $499 for the current no-limit license. This might get more consultants and small companies to pay for RU.
This is what the "per remote PC" license is for.
One of my clients with 19 PCs is up for a [censored] Central renewal in 6 months. It will cost them $433 as of right now. A 1-operator license for RU is $499, plus the cost of removing LMI and installing RU Host on each machine, so I can't recommend it to them even though RU is a one-time cost (except for upgrades to new versions). 19 RU hosts would cost even more ($27.95 per remote PC = $531.05) and they would still have the costs of removal and installation.
The problem is that this "reasonable" level may differ from customer to customer. There is always someone for whom the price is too high, and also someone who thinks that the price is pretty low. :)
However, we will certainly consider lowering the "per remote PC" pricing and shift the "threshold" towards increasing the number of "per remote PC" licenses equivalent to 1 operator license.
In order to do that you need to build the one-click installer with the following options:
On step 2
On step 3
On step 4
This build will update the Host to the latest version, but the ID, password and other Host settings will remain the same. Also, no notifications to the user will be shown other than standard Windows message about whether the user wants to run such-and-such executable.
The auto-update is a complicated topic that needs to be dealt with care. We will certainly be improving the update process in the future and using RU Server as a central "coordinating hub" is a good idea. Thanks!