Re: Terminal Services Idle Timeout
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Thu, 7 Apr 2005 16:30:28 -0400
Are the users getting the popup message that
says:
Idle timer expired : Session has been idle over its time limit.
It will be disconnected in 2 minutes.
Press any key now to continue session.
If so then the idle timeout is set somewhere else.
Session timeouts can be set:
On the Connection object
Start-->Run-->tscc.msc-->right-click RDP-Tcp-->Properties-->Sessions tab
On the User object
Active Directory Users & Comp-->right-click the user-->Properties-->Sessions tab
On the Group Policy object
Edit the GPO-->User-->Admin-->Win Comp-->Term Serv-->Sessions
And
Edit the GPO-->Comp-->Admin-->Win Comp-->Term Serv-->Sessions
The users may not have noticed the popup window, so
check the event log for Application Popup entries.
Thanks.
-TP
"jimr" <jimr@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2BBA60E0-DA43-47FE-97B6-F17E0E0D9DDF@xxxxxxxxxxxxxxxx
>I have a customer that has server 2003 with terminal services . They have 3
> win98 machines running the latest remote desktop client. After about 10 min
> of idle time, the session quits, then they have to restart it. I s there any
> way to make the timeout longer. I tried setting both the timeout policies on
> the server to two days, and also the edit the registry KeepAliveEnable to
> DWORD value of 1. Any suggestions would help.
>
> Thanks,
> Jim
.
- References:
- Terminal Services Idle Timeout
- From: jimr
- Terminal Services Idle Timeout
- Prev by Date: RE: Terminal Server - Software wont run on users' desktop
- Next by Date: Re: Web access to TS
- Previous by thread: Terminal Services Idle Timeout
- Index(es):
Relevant Pages
|