TS Session doens't log off after application close

[Gavin]

I've set an application (FileMaker Pro 6.0) to start when the user logs onto
the terminal server by pointing to the application in the "Start the
following program at logon" as part of Group Policy.

FileMaker starts fine and the user can work - however when they end the
application, instead of logging off, the terminal server session goes to a
grey desktop with no options whatsoever.

How can I make SURE there server will log off after closing the application
(again, in this case FileMaker Pro)?

 

[Vera Noest [MVP]]

You can check in TS Administration which process is still running
in the session when the users exit the program.

As a workaround, you can create a small batch file which starts
the application and logs the user off when finished. Then make
this batch file your starting application. Something like:

start /wait my_app.exe
logoff.exe

 

[Anthony]

Why create a batch file to log people off when they crash
an app? ? All you need to do is :- Open up the users
Propoerties.(you know where that is , cause you set up
his enviroment to start the app upon login!)Click the
sessions tab, set the End Disconnected session at 1
minute,and tick the box When a session limit is reached
or the connection is broken, tick END SESSION. That is as
far as Terminal services can help you. Goodluck

 

[Vera Noest [MVP]]

Anthony,

Gavin explained that the users don't crash the application, and
they don't have disconnected sessions. They normally end the
application, but the connection is not logged off, presumably
because there is still a process running in the users context. The
workaround with the batch file will fix this problem.

 

[Anthony]

Point taken,
however the way i read Gavins problem is that this occurs
when the user Ends the application (note he didnt state ,
the user clicks file / exit, the application) In normal
cases if a single application is launched, no shell is
started. When that application ends the Terminal session
should end and the user is logged off the terminal
server. I have noted from experience that if a user
clicks the "X" exit button of the application ( top
right hand corner) rather than clicking File / Exit, the
symptoms he describes can occur ( the appliacation closes
but the Terminal session remains). Which then leads the
users to disconect from the terminal server because there
is no other way for him to get rid of the blank screen as
he has no desktop options to use. When the user has
disconected in this manner the Terminal server sets the
user as disconnected but maintains his session and if he
reconnects ( thinking that all will be well), he will be
greeted with his previous session ,continually seeing the
empty blue screen . By setting the Terminal server to
automatically End a disconected session after 1 minute ,
the user would then be able to log on again after the
minute is up with a new session. This is my experience in
everyday work and can vouch for this on "ACT" which is a
client database program as is Filemaker and MYOB
accounting software packages. I used to continually reset
user sessions because they would call up and describe a
blank screen , now i just advise them to click the X at
the top right hand corner to disconnect the session and
wait a minute. The phone enquiries became less frequent
as users had a way of resetting their own sessions,and
now no longer occur ( i lie, not nearly as often. i could
be wrong, but then again. . Hey also, thanks for the tip
on restricting users to one session on a previous thread,