Try setting this initially to 10,000 milliseconds and then increase up to 30,000.
To make the application launch succeed, you need to change the value of the WSCReconnectMode key from 3 to 0 in one of the following: That’s because the Citrix receiver is configured by default to reconnect all open sessions upon launch. When you attempt to launch a published application from a published desktop, that action may disconnect the session of the published desktop. Application Launch Attempts in a Published Desktop Get Disconnected If the name of the executable in question is there, create a backup of the registry key and then remove the executable’s name from the key. The value of this registry key should not contain the executable for the application the user is attempting to launch. This is found in the registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI One of the places you’ll want to check is the value of LogoffCheckSysModules. When published applications don’t launch and the user doesn’t see any error message, then admins don’t see any entry that stands out in the Event Log of your Citrix server. Misconfigured LogoffCheckSysModules Registry Value in HKLM Citrix Receiver not Launching Applications
#OSU CITRIX RECEIVER WINDOWS#
Many solutions involve editing the Windows Registry-a high-risk operation that, if done wrong, can have serious consequences. For instance, if a user’s Citrix Receiver is not launching applications, you need to consider a number of factors.
What might seem like a simple problem in the Citrix Receiver (renamed to Citrix Workspace App) can turn out to be very hard to troubleshoot. A typical Citrix environment can be complex.
0 kommentar(er)
