Community

Anton Kalugin wrote:

No. Viewer only stores keys in the License key storage.

Where does the Portable Viewer store its License Keys?  Are they stored in %AppData% on the local computer where you run the viewer, in the local computer's registry, or in the PV's directory tree (e.g. on the USB stick from which you run the Portable Viewer)?

Conrad Sallian wrote:
We do our best to provide as flexible licensing as possible. In this specific case, I think yes - you need an operator license.

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.

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.

Another alternative might be to offer competitive upgrade pricing to people moving away from another remote-support solution.

Perhaps you could use Right-Alt-Tab and Left-Alt-Tab.  Obviously (to us English speakers) Left==Local and Right==Remote [grin].

Conrad Sallian wrote:
You can find the Host log in the C:\Program Files\Remote Utilities - Host\Logs folder. Currently the log contains basic information like from where a connection was initiated (IP address) and what connection mode was used as well as information about errors if any.

We are planning to make the log more informative in future versions though.

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.

It would also be a Good Thing if the viewer could import a remote host's logfile into its log.

Or a Raspberry Pi version, that would allow an inexpensive standalone GMS ... you could even sell them yourself!

Add my vote for this ...

It would be a Good Thing if we could update a remote's RU host from the Viewer control panel.

Can you run the MSI installer with the command-line switch "/passive" or do you have to build a 1-click EXE?

Conrad Sallian wrote:
- On the General tab in the Host options, you can enable the  Notification panel  and also select other options - change tray icon view, show balloon hint and play a sound.

It would be a Good Thing if there were an admin-controllable "timeout" on this notification panel in both Agent and Host versions.  I'd love to have this panel appear when I start a remote-control session and have it fade out after a time (30 seconds?).  If the mouse hovers over the Agent or Host tray icon, it could re-appear, again with a timeout.

Or make it minimizable.  Either option would mean it wouldn't be in the way when I'm doing support.

In tests using the temporary remote-support "agent.exe", I have discovered that if I have my remote-support client, after they have downloaded "agent.exe", right-click it and choose "Run as Administrator", I no longer need to have them authorize admin-level "Do you want XXX to make changes to this computer?" prompts or requests for the admin password, I can now do it myself.

For supporting remote home users who are administrators of their own computers, this is really helpful -- all they have to do is click "Yes" after starting Agent as admin.  They can then go back to watching TV or whatever ...

For supporting remote business users who are NOT admins of their own computers, this won't work unless they have an admin password available.  I tend NOT to supply admin passwords to my remote business clients but in this case it is required.  When I do this, I immediately change the admin password that I gave them to authorize "agent.exe" -- that lets me in as admin but keeps them from having an admin password.

Good-bye  [censored] ...