RE: Auto logoff problem

This should only happen when you start the application and exit it
more or less immediately, not when you have been working in the app
for several minutes. Is that the case for you?

Here's the reason and a workaround:

901196 - A remote session does not end immediately on a computer
that is running Windows Server 2003 Service Pack 1
http://support.microsoft.com/?kbid=901196

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?RXJpYzMy?= <Eric32@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
08 apr 2009 in microsoft.public.windows.terminal_services:

Update:

I found an article online that said this behaviour is normal
with 2003 and that it takes one minute for the session to end.
Sure enough I tried this and waited the one minute and voila!
It logged off.

Quesiton now is can this be changed or manipulated so it doesn't
take one minute?

"Eric32" wrote:

We're running an old Windows 2000 TS that we're in the process
of replacing.

On the old server we have it setup so when a user logs in an
application automatically loads and that's all they ever see
during their session. When they exit the program it
automatically logs them off of the session. This is setup
inside of the Terminal Services Configuration on the server
itself (the "Run initial program specified by user profiles and
Remote Desktop Connection or Terminal Services client" option).
We also have a separate account setup for each user
specifically for this server and within that account we have it
setup to "Start the following program at logon".

This was setup several years ago by a different admin and I
never changed it to use Group Policy.

Now we're having a problem with the new server (running Windows
Server 2003). We have it setup the same way. When the user
logs in the application loads fine but when they exit the
application their session is never logged off -- it just gives
them a blank blue screen.

Can anyone think of a reason why this is happening? I may
ultimately just set it up to use GP but I'm curious to know why
the logoff isn't working.
.

Relevant Pages

  • Re: Restricting TS USers
    ... The 1 minute delay happens only when you exit the application ... 901196 - A remote session does not end immediately on a computer ... MCSE, CCEA, Microsoft MVP - Terminal Server ... terminate properly when interactive users log off. ...
    (microsoft.public.windows.terminal_services)
  • RE: Auto logoff problem
    ... Vera, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... with 2003 and that it takes one minute for the session to end. ... This is setup ...
    (microsoft.public.windows.terminal_services)
  • RE: Auto logoff problem
    ... On the old server we have it setup so when a user logs in an application ... automatically loads and that's all they ever see during their session. ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote desktop issues
    ... There are five processes running after we exit the application: ... > MCSE, CCEA, Microsoft MVP - Terminal Server ... >> When we exit the application on the 2000 server the session ... >> Tim Marvin ...
    (microsoft.public.win2000.termserv.apps)
  • Re: php sessions problem - wrong logic maybe
    ... However, if u have closed the browser, the link to that session will no longer exist, so there is no way to re access the session. ... PHP will automatically destroy a session after a set amount of time, the default varies dependant on your server settings, mine is set to 20 minutes, so there is no need for you to catch out of date sessions! ... Also when I logoff (wchich destroys session and goes back to login screen) everything works fine. ...
    (comp.lang.php)