So if I use the portable viewer and the "agent" for spontaneous remote support sessions it will count against the 10 key license...
The rule of thumb is - in your Viewer you can have as many connection records (entries in the address book) as your license permits regardless of whether it's portable or installable Viewer. In case of the free license it's 10 records.
In other words I have only 10 sessions available to me to make spontaneous remote support connection with the 10 key license ...
Not exactly. I think I need to give you an example:
Suppose you have a physical address book with names and phone numbers of different people. You can call these people and chat with them at any time without any limitations.
However, your address book can only hold 10 records. In order to add one more record to that address book you need to remove one of the existing records to make available space.
It doesn't really matter whether you spontaneously call those people (think "Agent") or call them on a regular basis (think "Host"). Also, it doesn't matter whether you call them all at once or one at a time - the only thing that matters is how many records your address book can hold. If you no longer contact a certain person, you can remove their record and add a new one instead.
Thank you for your question, Dominic. And thank you, Bobby, for your answer.
Generally, what Bobby said was correct. I can only add that in the upcoming release 6.1 the Host module registration will become unnecessary. From then on the Host (and Agent for that matter) will be a "free-floating" module. Instead, you'll need to apply your license key in the Viewer.
For the "per remote PC" license type the Viewer will simply count the number of records in your address book and compare that number with the number allowed by your license key. If it's a free license key, the allowed number is 10.
In other words, if you registered your Viewer with a free license key, the total number of records (or "connections" as well call them) in all your address books combined can be 10 or less. I say address books, plural, because Viewer now allows adding multiple address books, not just one as it used to do.
So it won't matter what remote module you use on the remote side - Host or Agent - and there will be no more such awkward thing as "registering the Agent". We hope that this shift will make it easier for our customers to use the program and to buy it :)
3. It's a bug then. The pointer must be visible. What android version and device do you have? Also - did you connect to systems other than Win 2012?
4. I agree. But implementing a full-fledged online account would be a big task for us that would distract us from actually improving other aspects of the program itself. So we decided to make a small step forward and first implement "local" sync (via RU server that is). However, we have online account on our road map.
5. We'll check it out. Thanks!
It's great to hear that you'll be working on more connection modes and features in the future. The currently implemented connection modes work well so far in my testing of the windows client. It has worked great on Windows 7, 8.1, server 2012, and Hyper-V virtual machines.
Any settings that you can find in the Agent/Host can be altered on the MSI configuration step. At the last step of the configuration process http://www.remoteutilities.com/support/tutorials/configuring-agent.php you need to select "Specify new settings for Host" radiobutton and click Finish. This will launch a Host/Agent settings window that looks almost exactly like the vanilla Host settings window. Uncheck the IPv6 there and then close the settings window - the configured Agent will be created.
Another question is that why you couldn't access the Agent using that option on. Are you sure that was the reason? If so, we'll need to test that , perhaps it's a bug we didn't know about.
1. Yes, that's a known problem. Immediately after we release the next mobile update with the hottest fixes, we'll start implementing address book in the mobile version.
2. This is caused by the lack of address book. Essentially, when there is a full-fledged address book where each record has its own properties (like on the desktop version), this issue will be no more.
3. Please, elaborate on this issue. You mean, you do not see the remote mouse pointer? Or you do not see any mouse pointer at all.
5. Do you mean the mobile client or the desktop client?
6. We'll be adding more connection modes to the mobile client in the future.
7. Yes. See p.6.
For example, say an admin went to lunch, and during lunch the exchange information store service decided to hang - leaving the users he supports without email. It would be almost impossible to restart that service from the android software, due to the difficulty of no mouse, and lack of tools. If a service manager were implemented, that admin could have just connected to the server with Remote Utilities android, hit the services button, and find the service needed to restart, followed by selecting restart from a drop-down box next to the service rather than having to return to work mid-lunch.
This makes perfect sense. Thank you for the valuable feedback.