XP Terminal Services Session Idle Disconnect

I use mstsc to connect from my laptop back to my office desktop. A recent
change in our desktop image is now causing the desktop session to terminate
all processes left running 15 minutes after I disconnect. My intent is to
keep those processes running so I can reconnect to them later. This worked
until the recent change in our standard windows image.

Our windows install folks tell me there is a registry change in
HKLM\System\CurrentControlSet\Control\Terminal
Server\DefaultUserConfiguration that will fix this, but they can't say just
exactly what the change should be. So far I haven't been able to find the
right change to make.

Any pointers to how to keep this idle disconnect from occuring will be
greatly appreciated.

There are group policies that may govern this, ie. idle session timeouts.

http://tinyurl.com/5l3tbt

Additionally look at this spread sheet that maps group policies to registry
settings.

http://www.microsoft.com/downloads/d...DisplayLang=en

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"MP" <MP@discussions.microsoft.com> wrote in message
news39A48D8-E5AF-4E0D-859A-8E53C37827C0@microsoft.com...
>I use mstsc to connect from my laptop back to my office desktop. A recent
> change in our desktop image is now causing the desktop session to
> terminate
> all processes left running 15 minutes after I disconnect. My intent is to
> keep those processes running so I can reconnect to them later. This
> worked
> until the recent change in our standard windows image.
>
> Our windows install folks tell me there is a registry change in
> HKLM\System\CurrentControlSet\Control\Terminal
> Server\DefaultUserConfiguration that will fix this, but they can't say
> just
> exactly what the change should be. So far I haven't been able to find the
> right change to make.
>
> Any pointers to how to keep this idle disconnect from occuring will be
> greatly appreciated.
>

Perhaps I'm missing something, but I don't see how this applies to using
mstsc to RDP into another workstation. This isn't a server running a full
blown copy of Terminal Services. Can you help me understand how the URLs you
provided apply?

"Sooner Al [MVP]" wrote:

> There are group policies that may govern this, ie. idle session timeouts.
>
> http://tinyurl.com/5l3tbt
>
> Additionally look at this spread sheet that maps group policies to registry
> settings.
>
> http://www.microsoft.com/downloads/d...DisplayLang=en
>
> --
>
> Al Jarvi (MS-MVP Windows – Desktop User Experience)
>
> Please post *ALL* questions and replies to the news group for the
> mutual benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
> How to ask a question
> http://support.microsoft.com/KB/555375
>
> "MP" <MP@discussions.microsoft.com> wrote in message
> news39A48D8-E5AF-4E0D-859A-8E53C37827C0@microsoft.com...
> >I use mstsc to connect from my laptop back to my office desktop. A recent
> > change in our desktop image is now causing the desktop session to
> > terminate
> > all processes left running 15 minutes after I disconnect. My intent is to
> > keep those processes running so I can reconnect to them later. This
> > worked
> > until the recent change in our standard windows image.
> >
> > Our windows install folks tell me there is a registry change in
> > HKLM\System\CurrentControlSet\Control\Terminal
> > Server\DefaultUserConfiguration that will fix this, but they can't say
> > just
> > exactly what the change should be. So far I haven't been able to find the
> > right change to make.
> >
> > Any pointers to how to keep this idle disconnect from occuring will be
> > greatly appreciated.
> >
>

Look at the group policies on the workstation your remotely accessing with
RDC.

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"MP" <MP@discussions.microsoft.com> wrote in message
news:11F2B13D-08B3-425D-9579-1E6CAB95C4BE@microsoft.com...
> Perhaps I'm missing something, but I don't see how this applies to using
> mstsc to RDP into another workstation. This isn't a server running a full
> blown copy of Terminal Services. Can you help me understand how the URLs
> you
> provided apply?
>
> "Sooner Al [MVP]" wrote:
>
>> There are group policies that may govern this, ie. idle session timeouts.
>>
>> http://tinyurl.com/5l3tbt
>>
>> Additionally look at this spread sheet that maps group policies to
>> registry
>> settings.
>>
>> http://www.microsoft.com/downloads/d...DisplayLang=en
>>
>> --
>>
>> Al Jarvi (MS-MVP Windows – Desktop User Experience)
>>
>> Please post *ALL* questions and replies to the news group for the
>> mutual benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights...
>> How to ask a question
>> http://support.microsoft.com/KB/555375
>>
>> "MP" <MP@discussions.microsoft.com> wrote in message
>> news39A48D8-E5AF-4E0D-859A-8E53C37827C0@microsoft.com...
>> >I use mstsc to connect from my laptop back to my office desktop. A
>> >recent
>> > change in our desktop image is now causing the desktop session to
>> > terminate
>> > all processes left running 15 minutes after I disconnect. My intent is
>> > to
>> > keep those processes running so I can reconnect to them later. This
>> > worked
>> > until the recent change in our standard windows image.
>> >
>> > Our windows install folks tell me there is a registry change in
>> > HKLM\System\CurrentControlSet\Control\Terminal
>> > Server\DefaultUserConfiguration that will fix this, but they can't say
>> > just
>> > exactly what the change should be. So far I haven't been able to find
>> > the
>> > right change to make.
>> >
>> > Any pointers to how to keep this idle disconnect from occuring will be
>> > greatly appreciated.
>> >
>>