Secure Global Desktop Administration Guide > Applications, documents and hosts > A session doesn't end when the user exits the application
Using Object Manager, or from the command line, choose the appropriate Session Ends When setting for the application object.
If the Session Ends When attribute text box is disabled, the session ends when there are no visible windows.
When running an application on a Windows 2000/2003 Terminal Server, closing the application does not always result in the session closing. This is because the Sun Secure Global Desktop Enhancement Module for Windows is still running.
The solution is to configure the Sun Secure Global Desktop Enhancement Module to ignore
certain system processes so that it closes.
To do this, edit the System processes
value for the HKEY_LOCAL_MACHINE\Software\Tarantella\Enhancement Module for Windows
key in the registry on the application server. This value is a string which
is a comma separated list of exe binaries which the Sun Secure Global Desktop Enhancement Module should ignore.
You must amend this value by listing the processes that were running when the session failed to close.
To do this, open Task Manager (while you have a session that has failed to close) and click the
Processes tab. Make a list of all the exe processes that are running. Do not include
the following processes:
If you are running a single application session, you may find that the session
still does not exit even after editing the System processes
registry setting.
To force the session to exit, amend the Logoff application sessions
setting for the HKEY_LOCAL_MACHINE\Software\Tarantella\Enhancement Module for Windows
key and change the DWORD value to 1
.
Copyright © 1997-2006 Sun Microsystems, Inc. All rights reserved.