When a published application such as Explorer is started, it closes instantly.
Microsoft does not recommend using Explorer.exe as a published application. Because, the published Explorer.exe application runs as a separate process with a restricted access to the desktop.
The method of copying and renaming the Explorer.exe for example, Explorer2.exe is a widely used method. It is not recommended or supported by the Citrix Development Team. The session becomes unresponsive or slow when starting several instances of the renamed Explorer2.exe. These issues are the result of internal Explorer.exe dependencies that cannot be resolved without rewriting a large parts of the operating system kernel.
When a Windows Explorer is published, it must be similar to publishing a hosted application shortcut to C:WindowsExplorer.exe with a parameter of the drive letter, for example, “C:Windowsexplorer.exe” P: in Command line and P: in Working directory.
To resolve the issue, create a DWORD (32-bit) setting called LogoffCheckerStartupDelayInSeconds with value 10 in the following location:
Create and import a registry file to fix the issue. Copy the following text into a text file and save the file with a .reg extension:
Windows Registry Editor Version 5.00
When publishing the seamless explorer.exe application on XenApp 6.5 the session initially begins to connect as expected and after loading the dialog box disappears and the explorer application fails to appear. Initially in the Delivery Services console the application is shown as loading / connecting, later shows as disconnected and finally the session disappears.
Install the hotfix XA650W2K8R2X64025 (http://support.citrix.com/article/CTX132912)
Use the following registry key to configure the time-out:
Specifying a value of less than 10000 reverts to 10000 because 10 seconds is the minimum override.
Note, you can either use LogoffCheckerStartupDelayInSeconds or ApplicationLaunchWaitTimeoutMS
When the published Explorer is not visible in AppCenter Console as a workaround we could create and publish a batch file that calls Explorer.exe as below:
This would launch a CMD window and then launch the Explorer.exe process. However the CMD window process remains running and acts as a base for the published application instance in the console. So the CMD window is visible to the user and waits to be terminated