Browsium Catalyst 3.0 or later
Browsium Ion 3.0 or later
… with XenApp 5.0, 6.0 and 6.5
When an end user disconnects from a XenApp application that utilizes Ion or Catalyst, the user’s session might not close properly because the Ion and Catalyst processes are holding it open. This knowledge base article provides guidance for configuring a XenApp server so that the Ion and Catalyst processes are automatically closed when a user disconnects from the server.
When publishing an application with XenApp, only the main executable file is specified. However, some applications might spawn additional processes that run in the background and are not closed by the corresponding main executable file. Additional processes might also be created, from scripts that are executed, or from specific registry keys, such as the RunOnceKey:
HKEY_LOCAL_MACHINE\SW\Microsoft\Windows\CurrentVersion\RunOnce
Some processes might create a visible window for added functionality, and others might not.
Because the Explorer.exe Desktop is not running when launching an application in one of these ways, there is no default mechanism in either Presentation Server or Windows to terminate these background processes when a user has exited the main application.
To configure XenApp to close Ion and Catalyst processes when closing a session, add the Ion and Catalyst processes to the Citrix registry key LogoffCheckSysModules.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
For Ion:
Value Name: LogoffCheckSysModules
Type: REG_SZ
String: BrowsiumIonMonitor.exe,BrowsiumIonController.exe
For Catalyst:
Value Name: LogoffCheckSysModules
Type: REG_SZ
String: BrowsiumCatalystMonitor.exe,BrowsiumCatalystController.exe
Note: be sure not to include any spaces between multiple process names.
Posted in: Catalyst Knowledge Base, Ion Knowledge Base,
