Terminal server loading new session when connection lost
in [Windows Servers]
|
Prev: expiring password change on windows 2003 domain with Windows 7.
Next: expiring password change on windows 2003 domain with Windows 7
From: Juraj on 16 Mar 2010 18:56 Hi everyone, I'm having a trouble recently with our terminal server (w2k3 server SE). I have setup in main GPO logging off after 2 hours of inactive session and it works on SBS server 2k3 like a charm but not on this one. When the connection is lost users get kicked out and when they log back on the have a brand new session. Has there been any change for example "security" update by MS or TS has special settings? I have that it worked before for TS as well. Just happening recently and drives my nuts as I can't make any changes on router because users lost the session and need to start all over again. Frustrating for them as well as for me. Thanks for any ideas.
From: Matija Kapraljevic [Revenger] on 17 Mar 2010 13:15
On Tue, 16 Mar 2010 15:56:06 -0700 (PDT), Juraj wrote: > Hi everyone, > > I'm having a trouble recently with our terminal server (w2k3 server > SE). I have setup in main GPO logging off after 2 hours of inactive > session and it works on SBS server 2k3 like a charm but not on this > one. When the connection is lost users get kicked out and when they > log back on the have a brand new session. Take a look at group policy settings under Computer Configuration > Administrative Templates > Windows Components > Terminal Services There are two options that might be interesting to you: Keep-alive connections and Automatic reconnection -- Pozdrav =========== |