Graceful Logoff from a Published Application Renders the Session in Active State

Taken from : http://support.citrix.com/article/ctx891671

Symptoms or Error

Graceful logoffs from a published application launched in a seamless, fixed window, or as an RDP Initial Program, might result in the session not closing and the user being logged off. Sessions can be reset or exited correctly by manually resetting them, or by terminating remnant user processes in Terminal Services Administration, the Management Console, or Access Suite Console.

---

Solution

Complete the following steps:

1. Determine if the application in question and its associated processes correctly exit on a windows workstation outside of a Terminal Services environment.
2. If they do not, then it is possible that this mechanism might not work or it might be necessary to contact the application manufacturer.
3. Add the process file name to the following registry key:
   Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
   Value Name:LogoffCheckSysModules
   Type:REG_SZ
   String:MyAppName.exe

Notes:

• Do not place the executable name of the main published application in this key because this might result in failure to properly launch the published application. There is an issue if the main executable for the specified published application is not terminating correctly.
• Do not place the executable name of a secondary process that has a visible window in this key. This mechanism is designed to exit secondary processes that do not have a visible window, as it is expected that if an application window is visible, then it is intended for the user to see it, and therefore close it themselves.
  The application might not appear to present a visible window or a system tray icon in a seamless session. Run the application in a fixed window, perform the function within the application that spawns the secondary process and minimize the main application window. The spawned window is displayed in the background. An RDP initial application session configured on the RDP listener exhibits the same behavior. If a customer uses a logoff script, the logoff script could be used to check for the spawned process and terminate the process. Ideally, the application should close all child process that it spawns.
• Enter the list of executable names with a comma and NO spaces between them, for example:
  App1.exe,app2.exe,app3.exe