I am an application developer who often has to provide on-demand remote support to my clients' users, who run my application locally on their machines.
For that, they start a customized RU Agent that I bundle with my application for easy access.
My clients are small companies without dedicated IT departments. They use external IT service providers to manage their hard and software. These IT service providers also install remote access software on the client machines, typically a "Host" service that they can always access even without user interaction.
In the past I used the product of a competitor, but since more and more of my clients have the "Host" of that other product installed and IT-Admins often hide the password from users and don't allow them to terminate the Host, a user is not able to grant me access to the running Host, nor can he start an Agent (of that competitor product), because that is blocked by the Host.
Now, as long as no IT-Admin of any of my clients is using RU Host, I am good to go with my RU Agent.
But that could change at any time when they also decide to switch to RU.
Therefore it would be great if there was a way allow Host + Agent to co-exist on a machine for a scenario like mine.
