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. :)
Could you please tell me the Windows version and the IE version so that we check it out. We normally keep track of all a/v false positives and quickly contact the vendors asking them to remove false detections.
Note, however, that programs especially browsers can warn about an unsigned file and this is normal. But the signature is not always the only factor - a few months ago Chrome was blocking Remote Utilities downloads on our website, despite the fact that all the files were signed with a brand new digital signature from a respectful provider (DigiCert). So the lack of a digital signature does not necessarily mean that the file is prone to be blocked by browsers or OS.
In the future we are planning to provide the signing to our customers, or make an online MSI configurator that automatically signs the output file.
Don't hesitate to ask me if you have other questions.
Thank you for your message. First, let me tell you that in the near future we plan to introduce the feature that "converts" the Agent to a Host. That will make such scenario easier.
Still, even using the current version, everything can be simplified. Instead of running the Agent, then connecting through it and installing the Host etc. you can prepare a one-click Host installer in the MSI configurator and have the remote user run it. In the MSI configurator enable "Generate ID and send it via email" option to grab the ID of the remote PC.
Note that in many cases the only reason why customers use Agent is that it's a pure attended support tool. However, you can make the Host work as an attended-only tool as well if you need. Just enable the Ask user permission feature in the Host settings.
Idle or offline literally means that the computer is either idle (online and ready to accept connections) or offline (meaning that it's offline or even the Host is not installed at all).
You are probably confusing the idle state with the logged in state. The remote Host can be idle and awaiting your connection but you may not have been connected to it yet. In this case it's a grey monitor and the status is "Idle or offline". Then when you log in to that Host using the Login command, you are "explicitly" connected to that Host in which case the icon turns to a green monitor.