cdubois We are looking at a customer initiated client for a future release or a version of our unattended that the client can enable/disable by clicking an app on their desktop or from the task tray. Each executable created is linked to a specific session, so one thing that is possible today would be to deploy the executable but not delete those sessions after your done. If these session exists your customer could always rerun the executable and reconnect. Another option would be the batch file or scripting other users have used to turn on/off our unattended connections to basically serve the same purpose:

http://forum.screenconne...ttended-connections.aspx

Jeff, we have many clients in the health care field as well as municipalities, their security levels are low and they do not have administrator privileges on the machine, this solution is not suitable for us, but thank you for the suggestion.

Concerning the deployment of differents versions, we already deploy our solution to our customers using "web update". It's not a big thing for us to deploy a support tool within our application. But I understand your point of view Bigdessert.