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

How to enable Schannel event logging in IIS

Enable logging

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Start Registry Editor. To do this, click Start, click Run, type regedt32, and then click OK.

Locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL

On the Edit menu, click Add Value, and then add the following registry value:
Value Name: EventLogging
Data Type: REG_DWORD

Note After you add this property, you must give it a value.
See the table in the "Logging options" section to obtain the appropriate value for the kind of events that you want to log.

Exit Registry Editor and restart the computer.
Logging does not take effect until after you restart the computer

Logging options

The default value for Schannel event logging is 0x0000 which means that no Schannel events are logged.
Additionally, you can log multiple events by specifying the hexadecimal value that equates to the logging options that you want. For example, to log error messages (0x0001) and warnings (0x0002), set the value to 0x0003.
Value Description
0x0000 Do not log
0x0001 Log error messages
0x0002 Log warnings
0x0004 Log informational and success events

Applies to

Microsoft Internet Information Services 8.0
Microsoft Internet Information Services 7.5
Microsoft Internet Information Services 7.0
Microsoft Internet Information Services 6.0
Microsoft Internet Information Services 5.1
Microsoft Internet Information Services 5.0
Microsoft Internet Information Server 4.0