Skip past navigation linksSecure Global Desktop 4.40 Administration Guide > Applications, Documents, and Application Servers > An Application Session Does Not End When the User Exits an Application

An Application Session Does Not End When the User Exits an Application

In the SGD Administration Console, select the application and click the Launch tab. Check the Session Termination attribute. If the Session Ends When attribute text box is disabled, the session ends when there are no visible windows.

Are Processes Still Running That Cause the Windows Session Not to Exit?

When running an application on a Microsoft Windows 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 that contains a comma-separated list of exe binaries that the Sun Secure Global Desktop Enhancement Module can 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 might 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.

Related Topics