Close program but TS session continues to run

[paulc]

W2K3 TS and XP/W2K clients

I have configured some RDPconnections to the server to automatically run
upon connection. Basically, I don't want the users to have any interaction
with the TS other than running the program. However, the only issue I have
is that if the user closes out of the program too soon (> 2min or so), the
TS session continues to run. When that happens, if they log back into TS
they are presented with a blank screen since, apparently, the TS thinks the
prg is still running when in fact it isn't.
Other than setting the disconnect timeout to a very small number like 1
minute, is there anything else I can do?

 

[Helge Klein]

I do not think Windows has built-in a method for terminating
background processes (these are responsible for the behavior described
by you) upon close of the TS initial program. Although the resolution
does not apply to your situation (because you apparently do not use
Citrix Presentation Server) the following article from the Citrix KB
at least explains what is happening in more detail:

Graceful Logoff from a Published Application May Render the Session in
Active State
http://support.citrix.com/article/CTX891671

I hope this clarifies the situation.

Helge

==================
Please visit my blog:
http://it-from-inside.blogspot.com
==================

On 8 Aug., 20:55, "paulc" <pa...@mmcwm.com> wrote:
> W2K3 TS and XP/W2K clients
>
> I have configured some RDPconnections to the server to automatically run
> upon connection. Basically, I don't want the users to have any interaction
> with the TS other than running the program. However, the only issue I have
> is that if the user closes out of the program too soon (> 2min or so), the
> TS session continues to run. When that happens, if they log back into TS
> they are presented with a blank screen since, apparently, the TS thinks the
> prg is still running when in fact it isn't.
> Other than setting the disconnect timeout to a very small number like 1
> minute, is there anything else I can do?

 

[Mahesh Lotlikar [MS]]

This happens when there is some process running in the session that TS waits
for termination. Is it possible that there are any applications that are
started automatically when user logs on?

Here is what you could do: Start task manager and list the processes running
in the user session where user has closed the program. You could use
"qprocess" for this purpose to list the processes in specific session. Then
please refer to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs

There are some processes listed here. Find out which processes that are
running in the session and not listed in the above registry key. Those are
the processes which TS expects to terminate before it could log the session
off. Either you could stop starting those processes in user sessions
(recommended) or add them to the registry key so that TS can ignore them.

Please let me know what you find.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"paulc" <paulc@mmcwm.com> wrote in message
news:Ogub92e2HHA.484@TK2MSFTNGP06.phx.gbl...
> W2K3 TS and XP/W2K clients
>
> I have configured some RDPconnections to the server to automatically run
> upon connection. Basically, I don't want the users to have any interaction
> with the TS other than running the program. However, the only issue I have
> is that if the user closes out of the program too soon (> 2min or so), the
> TS session continues to run. When that happens, if they log back into TS
> they are presented with a blank screen since, apparently, the TS thinks
> the prg is still running when in fact it isn't.
> Other than setting the disconnect timeout to a very small number like 1
> minute, is there anything else I can do?
>

 

[Helge Klein]

Oops, I must have temporarily forgotten about SysProcs *blush*.

Please excuse me and try the method explained by Mahesh.

Helge

==================
Please visit my blog:
http://it-from-inside.blogspot.com
==================

On 8 Aug., 21:33, "Mahesh Lotlikar [MS]"
<mahe...@online.microsoft.com> wrote:
> This happens when there is some process running in the session that TS waits
> for termination. Is it possible that there are any applications that are
> started automatically when user logs on?
>
> Here is what you could do: Start task manager and list the processes running
> in the user session where user has closed the program. You could use
> "qprocess" for this purpose to list the processes in specific session. Then
> please refer to the following registry key:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs
>
> There are some processes listed here. Find out which processes that are
> running in the session and not listed in the above registry key. Those are
> the processes which TS expects to terminate before it could log the session
> off. Either you could stop starting those processes in user sessions
> (recommended) or add them to the registry key so that TS can ignore them.
>
> Please let me know what you find.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights."paulc" <pa...@mmcwm.com> wrote in message
>
> news:Ogub92e2HHA.484@TK2MSFTNGP06.phx.gbl...
>
> > W2K3 TS and XP/W2K clients
>
> > I have configured some RDPconnections to the server to automatically run
> > upon connection. Basically, I don't want the users to have any interaction
> > with the TS other than running the program. However, the only issue I have
> > is that if the user closes out of the program too soon (> 2min or so), the
> > TS session continues to run. When that happens, if they log back into TS
> > they are presented with a blank screen since, apparently, the TS thinks
> > the prg is still running when in fact it isn't.
> > Other than setting the disconnect timeout to a very small number like 1
> > minute, is there anything else I can do?

 

[Vera Noest [MVP]]

Since the OP explicitly mentions that this happens only when the
user closes the session immediately after starting it, I think that
certificate autoenrollment could also be the culprit:

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

Note that the article specifically mentions SP1, but the KB isn't
listed in the list of fixes that are included in SP2, so it might
apply to SP2 as well.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Helge Klein <Helge.Klein@googlemail.com> wrote on 08 aug 2007 in
microsoft.public.windows.terminal_services:

> Oops, I must have temporarily forgotten about SysProcs *blush*.
>
> Please excuse me and try the method explained by Mahesh.
>
> Helge
>
> ==================
> Please visit my blog:
> http://it-from-inside.blogspot.com
> ==================
>
> On 8 Aug., 21:33, "Mahesh Lotlikar [MS]"
> <mahe...@online.microsoft.com> wrote:
>> This happens when there is some process running in the session
>> that TS waits for termination. Is it possible that there are
>> any applications that are started automatically when user logs
>> on?
>>
>> Here is what you could do: Start task manager and list the
>> processes running in the user session where user has closed the
>> program. You could use "qprocess" for this purpose to list the
>> processes in specific session. Then please refer to the
>> following registry key:
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>> Server\SysProcs
>>
>> There are some processes listed here. Find out which processes
>> that are running in the session and not listed in the above
>> registry key. Those are the processes which TS expects to
>> terminate before it could log the session off. Either you could
>> stop starting those processes in user sessions (recommended) or
>> add them to the registry key so that TS can ignore them.
>>
>> Please let me know what you find.
>>
>> --
>> This posting is provided "AS IS" with no warranties, and
>> confers no rights."paulc" <pa...@mmcwm.com> wrote in message
>>
>> news:Ogub92e2HHA.484@TK2MSFTNGP06.phx.gbl...
>>
>> > W2K3 TS and XP/W2K clients
>>
>> > I have configured some RDPconnections to the server to
>> > automatically run upon connection. Basically, I don't want
>> > the users to have any interaction with the TS other than
>> > running the program. However, the only issue I have is that
>> > if the user closes out of the program too soon (> 2min or
>> > so), the TS session continues to run. When that happens, if
>> > they log back into TS they are presented with a blank screen
>> > since, apparently, the TS thinks the prg is still running
>> > when in fact it isn't. Other than setting the disconnect
>> > timeout to a very small number like 1 minute, is there
>> > anything else I can do?