2008 Terminal Server - client end locking after 10 min of inactivi

[ITFiveO]

Question 1 - In 2008 Terminal Server, we are publishing an application. When
the client runs the application all is well until they have 10 minutes of
inactivity. Then the terminal server session will lock to a sign-in screen.
How do I get rid of this? I know the default setting on 2008 for the
console is to lock in 600 seconds (10 minutes). If I change this registry
setting for the console, will it change it for my published application
sessions also?

Question 2 - Same scenario as above, except wait even longer for the client
machine to go to screen saver mode. When this happens the and we unlock the
client machine, the terminal session (published application) is still there,
it is just locked up and does not respond. I have looked at the Terminal
Manager on the sever when this happens. It still shows an active session,
but no traffic on the session. Any suggestions?

 

[Jeff Pitsch]

Re: 2008 Terminal Server - client end locking after 10 min of inactivi

The first can easily be configured with Group Policy. Screen savers are
controlled by user policies.

As for the second, are you sure you're unlocking the session and not simply
the workstation?

Jeff Pitsch
Microsoft MVP - Terminal Services

"ITFiveO" <ITFiveO@discussions.microsoft.com> wrote in message
news:67A464DF-1574-4A7B-AD93-6AEA269AFA81@microsoft.com...
> Question 1 - In 2008 Terminal Server, we are publishing an application.
> When
> the client runs the application all is well until they have 10 minutes of
> inactivity. Then the terminal server session will lock to a sign-in
> screen.
> How do I get rid of this? I know the default setting on 2008 for the
> console is to lock in 600 seconds (10 minutes). If I change this registry
> setting for the console, will it change it for my published application
> sessions also?
>
> Question 2 - Same scenario as above, except wait even longer for the
> client
> machine to go to screen saver mode. When this happens the and we unlock
> the
> client machine, the terminal session (published application) is still
> there,
> it is just locked up and does not respond. I have looked at the Terminal
> Manager on the sever when this happens. It still shows an active session,
> but no traffic on the session. Any suggestions?

 

[ITFiveO]

Re: 2008 Terminal Server - client end locking after 10 min of inac

Re: 2008 Terminal Server - client end locking after 10 min of inac

Yes, we are unlocking the workstation, then trying to get to the published
application which still shows up on the task bar. However we can not get it
to restore or maximize to even be able to show us a login screen to the
terminal session.

"Jeff Pitsch" wrote:

> The first can easily be configured with Group Policy. Screen savers are
> controlled by user policies.
>
> As for the second, are you sure you're unlocking the session and not simply
> the workstation?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "ITFiveO" <ITFiveO@discussions.microsoft.com> wrote in message
> news:67A464DF-1574-4A7B-AD93-6AEA269AFA81@microsoft.com...
> > Question 1 - In 2008 Terminal Server, we are publishing an application.
> > When
> > the client runs the application all is well until they have 10 minutes of
> > inactivity. Then the terminal server session will lock to a sign-in
> > screen.
> > How do I get rid of this? I know the default setting on 2008 for the
> > console is to lock in 600 seconds (10 minutes). If I change this registry
> > setting for the console, will it change it for my published application
> > sessions also?
> >
> > Question 2 - Same scenario as above, except wait even longer for the
> > client
> > machine to go to screen saver mode. When this happens the and we unlock
> > the
> > client machine, the terminal session (published application) is still
> > there,
> > it is just locked up and does not respond. I have looked at the Terminal
> > Manager on the sever when this happens. It still shows an active session,
> > but no traffic on the session. Any suggestions?
>
>
>