Terminal Server Timeout...

Windows Server 2008

We need to run an application under a disconnected user session (it cannot
run as a service). The user logs in, starts the application, then
disconnects. After approximately 10 minutes, the session times out and
automatically terminates the user's session. I've already modified group
policy and set the timeouts to never, but the timeout still occurs. How can
we accomplish this? Thanx.

 

Hi,

The timeouts are still being set in another place. Check
Terminal Services Configuration, Sessions tab of User
properties in AD, local group policy (gpedit.msc on TS),
any other GPOs that may apply.

Timeout changes will not affect a session that is currently
logged on.

Thanks.

-TP

Steven Sinclair wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Windows Server 2008
>
> We need to run an application under a disconnected user session (it
> cannot run as a service). The user logs in, starts the application,
> then disconnects. After approximately 10 minutes, the session times
> out and automatically terminates the user's session. I've already
> modified group policy and set the timeouts to never, but the timeout
> still occurs. How can we accomplish this? Thanx.<!--colorc--><!--/colorc-->

 

Yes, I checked the Terminal Service Configuration > Sessions tab and it is
set to "Never." In addition, there are no other GPOs that haven't already
been changed to "Never." I'm really at a loss as to what must be controlling
this. As I mentioned, the user logs in, starts the app, then disconnects (not
log off), but after 10 minutes, the user's session is killed. Thanx again.


"TP" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
>
> The timeouts are still being set in another place. Check
> Terminal Services Configuration, Sessions tab of User
> properties in AD, local group policy (gpedit.msc on TS),
> any other GPOs that may apply.
>
> Timeout changes will not affect a session that is currently
> logged on.
>
> Thanks.
>
> -TP
>
> Steven Sinclair wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Windows Server 2008
> >
> > We need to run an application under a disconnected user session (it
> > cannot run as a service). The user logs in, starts the application,
> > then disconnects. After approximately 10 minutes, the session times
> > out and automatically terminates the user's session. I've already
> > modified group policy and set the timeouts to never, but the timeout
> > still occurs. How can we accomplish this? Thanx.<!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

Hi,

Did you check the Sessions tab on the User's Properties
like I mentioned? Right-click on the user account and
choose Properties, then the Sessions tab.

Have you run Resultant Set of Policy (rsop.msc)?

Thanks.

-TP

Steven Sinclair wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Yes, I checked the Terminal Service Configuration > Sessions tab and
> it is set to "Never." In addition, there are no other GPOs that
> haven't already been changed to "Never." I'm really at a loss as to
> what must be controlling this. As I mentioned, the user logs in,
> starts the app, then disconnects (not log off), but after 10 minutes,
> the user's session is killed. Thanx again.
> <!--colorc--><!--/colorc-->

 

Yes, here are the settings:

End a disconnected session: Never
Active session limit: Never
Idle session limit: Never
When a session limit is reached or connection is broken: Disconnect from
session
Allow reconnection: From any client

Thanx again.


"TP" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
>
> Did you check the Sessions tab on the User's Properties
> like I mentioned? Right-click on the user account and
> choose Properties, then the Sessions tab.
>
> Have you run Resultant Set of Policy (rsop.msc)?
>
> Thanks.
>
> -TP
>
> Steven Sinclair wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Yes, I checked the Terminal Service Configuration > Sessions tab and
> > it is set to "Never." In addition, there are no other GPOs that
> > haven't already been changed to "Never." I'm really at a loss as to
> > what must be controlling this. As I mentioned, the user logs in,
> > starts the app, then disconnects (not log off), but after 10 minutes,
> > the user's session is killed. Thanx again.
> > <!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

Any further ideas? Everything is set properly, but still the sessions are
automatically terminated after 10 minutes. Thanx.



"TP" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
>
> Did you check the Sessions tab on the User's Properties
> like I mentioned? Right-click on the user account and
> choose Properties, then the Sessions tab.
>
> Have you run Resultant Set of Policy (rsop.msc)?
>
> Thanks.
>
> -TP
>
> Steven Sinclair wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Yes, I checked the Terminal Service Configuration > Sessions tab and
> > it is set to "Never." In addition, there are no other GPOs that
> > haven't already been changed to "Never." I'm really at a loss as to
> > what must be controlling this. As I mentioned, the user logs in,
> > starts the app, then disconnects (not log off), but after 10 minutes,
> > the user's session is killed. Thanx again.
> > <!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

If you try a different user, a user with admin rights or rdp to another
machine in the same OU, do they timeout too?

"Steven Sinclair" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Any further ideas? Everything is set properly, but still the sessions are
> automatically terminated after 10 minutes. Thanx.
>
>
>
> "TP" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi,
> >
> > Did you check the Sessions tab on the User's Properties
> > like I mentioned? Right-click on the user account and
> > choose Properties, then the Sessions tab.
> >
> > Have you run Resultant Set of Policy (rsop.msc)?
> >
> > Thanks.
> >
> > -TP
> >
> > Steven Sinclair wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Yes, I checked the Terminal Service Configuration > Sessions tab and
> > > it is set to "Never." In addition, there are no other GPOs that
> > > haven't already been changed to "Never." I'm really at a loss as to
> > > what must be controlling this. As I mentioned, the user logs in,
> > > starts the app, then disconnects (not log off), but after 10 minutes,
> > > the user's session is killed. Thanx again.
> > > <!--colorc--><!--/colorc-->
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Yes. All users are treated equally. Doesn't matter which user logs in to run
the app...ten minutes after they disconnect, their session is killed. Thanx.



"prmolina" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> If you try a different user, a user with admin rights or rdp to another
> machine in the same OU, do they timeout too?
>
> "Steven Sinclair" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Any further ideas? Everything is set properly, but still the sessions are
> > automatically terminated after 10 minutes. Thanx.
> >
> >
> >
> > "TP" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi,
> > >
> > > Did you check the Sessions tab on the User's Properties
> > > like I mentioned? Right-click on the user account and
> > > choose Properties, then the Sessions tab.
> > >
> > > Have you run Resultant Set of Policy (rsop.msc)?
> > >
> > > Thanks.
> > >
> > > -TP
> > >
> > > Steven Sinclair wrote:
> > > > Yes, I checked the Terminal Service Configuration > Sessions tab and
> > > > it is set to "Never." In addition, there are no other GPOs that
> > > > haven't already been changed to "Never." I'm really at a loss as to
> > > > what must be controlling this. As I mentioned, the user logs in,
> > > > starts the app, then disconnects (not log off), but after 10 minutes,
> > > > the user's session is killed. Thanx again.
> > > >
> > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Hi,

I asked you two questions. I assume your yes answer is
to the first one.

Have you run Resultant Set of Policy (rsop.msc)? I would
first run rsop.msc as an admin so that you can see any
Computer config settings that may apply, then run it as the
individual user account.

Unless there is a new bug in 2008 the timeout is being
set in one of the normal places. From your description
so far my guess would be it is being set via Group
Policy.

Group Policy TS Session timeouts can be set under
Computer Configuration and User Configuration. That
means there are *two* places to check for each GPO
that may apply.

I would suggest you go through your GPOs and set
the TS timeouts to "Not Configured" instead of Never.

When editing a GPO use the filtering option to "Only show
configured policy settings". That way you will only see
the items that are actually configured.

Below are the places the timeouts can be set:

1. Terminal Services Configuration
2. Local Group Policy (open gpedit.msc on the TS to edit),
remember timeouts can be set under Computer and/or User
3. User Properties in Active Directory Users and Computers,
if not part of a domain then local User Properties
4. Domain-based Group Policies--there can be one or more
of these, remember timeouts can be set under Computer
and/or User
5. DefaultUserConfiguration key in the registry--most people
are not aware of this so it is not likely to be set here.

Thanks.

-TP

Steven Sinclair wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Yes, here are the settings:
>
> End a disconnected session: Never
> Active session limit: Never
> Idle session limit: Never
> When a session limit is reached or connection is broken: Disconnect
> from session
> Allow reconnection: From any client
>
> Thanx again.<!--colorc--><!--/colorc-->

 

Anyone?

Thanx.



"prmolina" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> If you try a different user, a user with admin rights or rdp to another
> machine in the same OU, do they timeout too?
>
> "Steven Sinclair" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Any further ideas? Everything is set properly, but still the sessions are
> > automatically terminated after 10 minutes. Thanx.
> >
> >
> >
> > "TP" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi,
> > >
> > > Did you check the Sessions tab on the User's Properties
> > > like I mentioned? Right-click on the user account and
> > > choose Properties, then the Sessions tab.
> > >
> > > Have you run Resultant Set of Policy (rsop.msc)?
> > >
> > > Thanks.
> > >
> > > -TP
> > >
> > > Steven Sinclair wrote:
> > > > Yes, I checked the Terminal Service Configuration > Sessions tab and
> > > > it is set to "Never." In addition, there are no other GPOs that
> > > > haven't already been changed to "Never." I'm really at a loss as to
> > > > what must be controlling this. As I mentioned, the user logs in,
> > > > starts the app, then disconnects (not log off), but after 10 minutes,
> > > > the user's session is killed. Thanx again.
> > > >
> > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Anyone have a solution out there in never-never land?

Thanx.

 

Have you troubleshooted your Group Policy settings
using Resultant Set of Policy (rsop.msc)?

Have you run gpupdate /force on your TS?

Since you checked Terminal Services Configuration as
well as the User's Properties, the most likely thing left
is Group Policy. Just because you edited the Group
Policy and set it to Never does not mean the policy is
being applied to the server properly. Sometimes GP
settings do not get applied so you need to troubleshoot.

I have been using the timeout settings on many servers
for many years and have yet to see a case when they
are not honored. What I have seen is cases where
the settings are set in an unexpected place or the GP
settings were not being applied as expected. It is
possible you have discovered a new bug in 2008, but
I have not heard of anyone else complaining of this
so far.

Another thing you can try is to force the setting to be
re-written by setting it to something else (like 2 days),
applying, then setting it back to Never.

Thanks.

-TP

Steven Sinclair wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Anyone have a solution out there in never-never land?
>
> Thanx.<!--colorc--><!--/colorc-->

 

Can you also please confirm any apps/processes running on your TS server
does not log off disconnected sessions?

Thanks
Soo Kuan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"TP" <tperson.knowspamn@mailandnews.com> wrote in message
news:%239JXylZJKHA.3708@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Have you troubleshooted your Group Policy settings using Resultant Set of
> Policy (rsop.msc)?
>
> Have you run gpupdate /force on your TS?
>
> Since you checked Terminal Services Configuration as well as the User's
> Properties, the most likely thing left is Group Policy. Just because you
> edited the Group Policy and set it to Never does not mean the policy is
> being applied to the server properly. Sometimes GP settings do not get
> applied so you need to troubleshoot.
>
> I have been using the timeout settings on many servers for many years and
> have yet to see a case when they are not honored. What I have seen is
> cases where the settings are set in an unexpected place or the GP settings
> were not being applied as expected. It is possible you have discovered a
> new bug in 2008, but I have not heard of anyone else complaining of this
> so far.
>
> Another thing you can try is to force the setting to be re-written by
> setting it to something else (like 2 days), applying, then setting it back
> to Never.
>
> Thanks.
>
> -TP
>
> Steven Sinclair wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
>> Anyone have a solution out there in never-never land?
>>
>> Thanx. <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->