"Does the same thing happen if you log in locally on the computer and then
lock it (instead of remote destop and then disconnect)?"
No. The programs continue to run as advertised.
If I am logged in locally, it will lock after a set number of minutes of
inactivity, but the programs continue to run, as opposed to terminating the
programs. I can then logon and resume my session, no glitches.
I found out there are Group Policy Overrides (GPOs) that may be causing my
problem. I have to get a top-level admin to review these to see if the 'Set
time limit for disconnected sessions' is enabled. If so, we need to disable
the GPO.
I'll let you know...
"blank" wrote:
> =?Utf-8?B?R292dGVjaGll?= wrote in
>
>
> > When I disconnect from a Remote Desktop Connection using the Red X in
> > the top right corner of the screen, the message "This will disconnect
> > your session. Your programs will continue to run while you are
> > disconnected. You can reconnect to this session later by logging on
> > again." I click the "OK' button. 48 seconds later the computer stops
> > the program, and logs off. I know this because I hooked the remote
> > where I could watch it. When I log on again, the remote computer acts
> > as if I am just rebooting by launching the desktop, I get the Windows
> > music, and my startup programs launch. How do I fix this? I'm using
> > XP Pro.
> >
>
> Does the same thing happen if you log in locally on the computer and then
> lock it (instead of remote destop and then disconnect)? If so, might there
> be a policy in effect (or screensaver?) that logs you out automatically
> after locking the workstation - I have seen this done in public computer
> labs at a University, for example.
>
> Does it behave the same when you are logged in locally on the machine
> before you remote desktop to it as when you are not logged in locally
> before you remote desktop to it?
> >> Stay informed about: Remote Desktop Disconnection Issue