We have a situation at work, where we have several computers that all
automatically login on boot as a certain user. What we would like to do is
use Remote Desktop to connect as that same user, then when the person who
remotely connects disconnects their session, the console will be logged in as
the user. This can be accomplished if the user runs the following command to
disconnect "tscon o /dest:console", but I can't rely on the users to always
do this. Is there a way to do something similar to that command when the
WM_WTSSESSION_CHANGED message with REMOTE_DISCONNECT comes across? I've tried
several ways, but haven't been successful.

The other idea I had was to make the script the only way the person could
disconnect. I can remove the "Disconnect" button from the start menu on the
server, but the user can still press the X on the Remote Desktop client,
anyone know of a way to disable this easily?

Thanks!

slide

> We have a situation at work, where we have several computers that all
> automatically login on boot as a certain user. What we would like to do is
> use Remote Desktop to connect as that same user, then when the person who
> remotely connects disconnects their session, the console will be logged in
as
> the user. This can be accomplished if the user runs the following command
to
> disconnect "tscon o /dest:console", but I can't rely on the users to
always
> do this. Is there a way to do something similar to that command when the
> WM_WTSSESSION_CHANGED message with REMOTE_DISCONNECT comes across? I've
tried
> several ways, but haven't been successful.
>
> The other idea I had was to make the script the only way the person could
> disconnect. I can remove the "Disconnect" button from the start menu on
the
> server, but the user can still press the X on the Remote Desktop client,
> anyone know of a way to disable this easily?

Not, AFAIK. But you can set "Set time limit for disconnected sessions" to "1
min" policy.

>
> Not, AFAIK. But you can set "Set time limit for disconnected sessions" to "1
> min" policy.
>


The issue with that is it causes a logoff to happen, all I want to have
happen is a switch back to the "console" instead of the remote session.