Thank you for your suggestion. Very soon we will be significantly improving the address book in the mobile client and make it look very differently and much closer to how it looks like in the desktop client. That's why it doesn't make sense to make little improvements now, provided that there's going to be a big revamp soon anyway.
Currently on viewer 126.96.36.199 trying to push out a 188.8.131.52 MSI.
This looks like a version mismatch. The Viewer checks the Host's installer version against its own version before the update.
It is highly recommended that you first upgrade the Viewer to the most recent version (184.108.40.206) and then upgrade your Hosts to the same version. Having different versions of Viewer and Host can result in unpredictable behavior and issues hard to diagnose.
Thank you for the kind words. Yes, we do our best to update the mobile version as soon as possible to fix the iOS 8 issue. Meanwhile, if you are using iOS 9, the app should be working ok. Please, let us know if you have any issues.
I see what you mean. But signing the modified installers with a signature will only be possible after we provide an online configurator. Until then, we cannot provide such a feature because it can be easily tampered with and our signature may be compromised.
For me personally, I don't care. Remote users, however, are not as willing to do this because if Windows says it is dangerous, then they question it.
If you are telling users to install something on their PC, then they trust you. You can simply tell them that this is a standard Windows warning and that they don't have to worry. Then ask them to accept file download/installation, whatever is the case.
But as I said, we will be making Agent/Host more flexible in the future, namely provide the option to convert Agent into Host.
Are there any downsides to this legacy capture mode?
Not at all. As the name implies, this option was added for compatibility with other Windows capturing mechanisms. This is a simplified explanation though, so to say. Most users only care about the end result, which in this case is triggered by a single check box. All that is needed. :)