Thanks for the prompt response - much appreciated.
The original list was just off the top of my head. If I had to place a priority on them it would look like this (with the reasoning for the priority below each entry);
I have added an additional item “ITarian stores a list of pre-approved connection IDs”.
Android, iOS and Mac clients
As a service provider, we cannot enforce what endpoints our destination clients use and more companies are moving to a more diverse landscape (BYOD, etc.).
Having only a Windows client restricts any service delivery from the source client to only Windows destination clients.
Maximum client types = Maximum service delivery = Maximum $$ = Maximum happy clients.
ITarian stores a list of pre-approved connection IDs
Known approved connection IDs could be stored on the destination client to allow for after hours or unattended connections.
Known connection IDs could be stored on the source client in an address book for easier connection to frequent clients.
ITarian installed as a service for unattended logins
There will be times when remote work must be completed outside of normal hours (See point 2 above).
Direct file transfer between source client and destination client (or vice versa) but file transfer can only be initiated by source client
There will be times when tools and utilities need to be executed on the remote connection and they could be copied using an internal file manager.
Auto reconnect for failed connections
Source and destination clients could store the connection credentials and parameters for a short period (60 seconds) after the closure of a session.
Source client could quickly re-establish a connection if it drops out.
Auto disconnect after nominated period of inactivity
Session should be terminated after a source client defined period of inactivity.
Auto disconnect should display a prompt to the source client to allow him to approve disconnection or decline to continue the session.
Redirected printer output
This is not necessarily for a service provider but more for the client themsleves.
If they remote into their own system to run in house apps, they could then get the printed output from the remote system to their local location.
This would only become possible after “pre-approved connection IDs” and “unattended logins” are added.
Source client = Client initiating the remote connection - typically service provider
Destination client = Client requesting the remote connection - typically client (enduser)
Hope this helps,