Ok i saw this recently and wanted to post the solution to those of you who have this issue.
What is the behavior:
- a published application in seamless mode may present you with a logon screen (this published app could be application1.exe)
- once you logon you are send to the actual program executable you use (this could be application2)
- maybe you are trying to shadow the session to help the user and you do not see the application in the management console for Citrix
In our case the application was GE Centricity EMR, the published application was “logician.exe” (the splash screen apparently) and the actual application was “ML.exe”.
It turns out there is a seamless flag you can set to help with this issue.
JOB OBJECT
Explanation: If a published application was a program that created a new process and then terminated itself, the published application appeared in the management console for MetaFrame XP. However, in a seamless session the application was launched through session sharing, the application appeared in the management console but then disappeared.
By default, the thread that checks the process cares about only the first instance of the launched process. The thread regarded the published application as terminated when the first instance of the process was terminated even if that process created a separate process.
This update provides a way to configure those published applications to use the JOB object so that additional processes created by the initial process are considered as published applications.
For this update to work properly, you need to perform the following steps.
If the command line of the published application is [ApplicationPath], go to the following Registry key and make changes as necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\StartInJobObject
Key Value: [ApplicationPath]
Type: DWORD
Value: 0
For example, if the command line specified for the published application is c:\notepad.cmd, go to the following Registry key and make changes as necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\StartInJobObject
Key Value: c:\notepad.cmd
Type: DWORD
Value: 0
For those applications whose command line is specified in the StartInJobObject key, the published application will not disappear from the Management Console until all of the processes created by the process are terminated.
Basically you create these registry keys for the affected applications in the same place you enter the standard seamless flag settings. These settings will allow the applications that start as one program and launch other processes. The only one you need to create is the application listed in the published application configuration. All this does is allow the application to them display in the management console.
Hope this helps someone…