When a user inside a published desktop starts a published application, disconnection occurs.
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
Create WSCReconnectModeUser and modify existing registry key WSCReconnectMode in Master Desktop Image or in XenApp Server hosting, the published desktop can change the behavior of the Receiver.
Create the following key :
64-Bit - [HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Citrix\Dazzle]
32-Bit - [HKEY_CURRENT_USER\SOFTWARE\Citrix\Dazzle]
Name: WSCReconnectModeUser
Type: REG_SZ
Value data: 0
Modify the following key from the default value of 3 to zero
64-Bit - [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle]
32-Bit - [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle]
Name: WSCReconnectMode
Type: REG_SZ
Value data: 0
Note: Alternatively, the REG_SZ value WSCReconnectAll can also be set to false if creating a brand new key is not preferred.
The Receiver default behavior is set to the following value:
3 = reconnect on application launch or refresh
When an application is launched within a published desktop it is seen as an open application which generates a disconnection.
Citrix Documentation - WSCReconnect Values and Keys
0 = do not reconnect to any existing sessions
1 = reconnect on application launch
2 = reconnect on application refresh
3 = reconnect on application launch or refresh
4 = reconnect when Receiver interface opens
8 = reconnect on both Windows logon and power resume
11 = combination of both 3 and 8
Note: To test this on a on an already launched published desktop, restart the desktop for the settings to take affect.