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.
No, you do not have to register RUS. It's a free program and the licensing costs are not affected by whether you use the RUS or not.
The message you received means that you need to register the remote Host, i.e the software itself. In the upcoming 6.1 update though we will remove Host registration - i.e. the Host will become a "free floating" module. Instead, you will only have to register the Viewer, which is more intuitive for users.