Remote Desktop Related Question

[Rev. Michael L. Burns]

I am using remote desktop between my notebook and my desktop and all seems
to be working ok. However, as it is designed, when a RD session is
established, say from my notebook to the desktop in my office, the office
computer switches to the user logon screen to keep anyone else from using it
while in a RD session. After the RD session is terminated, the logon screen
remains.

Is there some type of work around so that when I end the session that the
remote computer (my desktop in this case) will log back in to where it was
before being accessed from the other computer (my notebook for instance)?

I thought I saw something like this mentioned somewhere but for the life of
me, I can't remember where, nor can I find it.

Michael

 

[Shenan Stanley]

I am using remote desktop between my notebook and my desktop and
all seems to be working ok. However, as it is designed, when a RD
session is established, say from my notebook to the desktop in my
office, the office computer switches to the user logon screen to
keep anyone else from using it while in a RD session. After the RD
session is terminated, the logon screen remains.

Is there some type of work around so that when I end the session
that the remote computer (my desktop in this case) will log back in
to where it was before being accessed from the other computer (my
notebook for instance)?
I thought I saw something like this mentioned somewhere but for the
life of me, I can't remember where, nor can I find it.

If you were logged into the remote machine locally (with the screen
unlocked) before you remoted into it and you logged in remotely as the same
user as was logged in locally - you can *push* the session back to the
console instead of just disconnecting...

Start button --> RUN --> tscon 0 /dest:console --> OK

Given your user has the rights to do this and you WERE logged in as that
user before LOCALLY witht he screen unlocked... That should push the
session view back to the local console on the machine.

 

[Guest]

If you were logged into the remote machine locally (with the screen
unlocked) before you remoted into it and you logged in remotely as the same
user as was logged in locally - you can *push* the session back to the
console instead of just disconnecting...

Start button --> RUN --> tscon 0 /dest:console --> OK

Given your user has the rights to do this and you WERE logged in as that
user before LOCALLY witht he screen unlocked... That should push the
session view back to the local console on the machine.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way



Is there any way to make it do this automatically?

 

[Shenan Stanley]

If you were logged into the remote machine locally (with the screen
unlocked) before you remoted into it and you logged in remotely as
the same user as was logged in locally - you can *push* the session
back to the console instead of just disconnecting...

Start button --> RUN --> tscon 0 /dest:console --> OK

Given your user has the rights to do this and you WERE logged in as
that user before LOCALLY witht he screen unlocked... That should
push the session view back to the local console on the machine.

Is there any way to make it do this automatically?

Not that I know of beyond having an automatic logon and the last thing you
do is reboot the remote machine - not just disconnect.

I guess you could write a simple batch script and place it on the remote
desktop 'desktop' and double-click on it when you wish to disconnect... Is
that automatic enough? (When the console gets pushed back - it DOES
disconnect your remote session.)