Sometimes when you close a XenApp application, the session on the server may not close correctly or remain active, thus creating problems such as :
· Profiles corruption
· Increased servers’ resources usage
· Increased number of disconnected sessions, and so on…
This behavior can be caused by locked files (have a look at this for an example) or by processes that may have been launched during the sessions and that are not correctly closed upon user’s logoff.
For instance, if you publish an instance of Internet Explorer that in turn launches a Java process in order to run a web application, this java process may not be recognized by Citrix as being part of the user’s session, thus ignoring it upon user’s logoff and leaving an active session on the server.
A registry key can be modified on the server in order to instruct XenApp to consider other processes to be part of a user’s session ; the key is :
and the value to configure is : LogoffCheckSysModules
For example, you configure such value like the following if you want XenApp to recognize the two processes “Java.exe” and “Javaw.exe” :
I experienced this on XenApp 5 and Presentation Server 4 and the solution works correctly. I never faced this on XenApp 6.5.
For more information about this : http://support.citrix.com/article/CTX891671