Hi Timothy,
This is an awesome product. I work with a set of test machines (6-10) and instead of RDP'ing into it individually, this is working out great for me.

I have a small feature request:
Since there is an option to "connect to console", would it make sense to add another feature (either in the connection properties or an additional button next to the disconnect button) to "disconnect and return to console"?

Reason for requesting this feature:
Based on how the test machines are setup, I need to connect to these machines' console. This I can do easily by using the feature "Connect to console" in the connection properties.

However, I cannot just disconnect from these machines else the screen will get locked. I need to give the control back to the console else my tests won't run. To work around this problem, I have created a shortcut on the desktop of each machine named "remote disconnect" with the command: "%windir%\system32\tscon.exe 0 /dest:console". Instead of disconnecting the connection, I use this shortcut to hand over control back to the console.

Thanks again.

Anand

When you connect to a non-console session, I know of no programatic way to "send" that session to the console from the client computer (where RD Tabs is running). The script you wrote using tscon.exe in your interactive admin session might be the only way. However, if you connect to the console session using the "connect to console" checkbox, it will still be at the console when you disconnect.

Vista and Server 2008 remote desktop solves your problem. They no longer has an interactive session 0 console, so all sessions (remote and local) work from the same pool of sessions. If you disconnect from the console on a computer, you can later reattach it automatically using remote desktop; and vice versa.

Thanks for your response.

When I "connect to console" using RDP / RD Tabs, this works as you say it does. However, on disconnecting the session, the remote machine's screen gets locked which causes problems for me. To prevent this from happening in my environment, I use tscon the way I mentioned instead of just disconnecting the RDP / RD Tabs session.

VNC does not lock the screen when I disconnect from the remote machine. So maybe when RD Tabs supports VNC, this problem will be moot anyway 🙂.

Could I suggest another feature(s):
> Ability to run / execute a user script / program on connect.
> Ability to run / execute a user script / program on disconnect.

Do you think it will add value?

Thanks.

Regards,

Anand

I'll have to check into the API. I know there are ways to assign scripts via GPO, but I'm not sure if it's available in the RDP API.

As for leaving the console unlocked and exposed after disconnection, I understand now what you are asking and I am positive there is no (easy) way I can add that feature using RDP. If VNC allows it, then yes when additional protocols are added to RD Tabs in the future that will certainly help you! I understand it is a requirement for you, but for most people that's undesirable behavior because it leaves the remote computer unlocked and open to attack at the console if it is not physically secured well.