We have attempted to deploy a commercial application that chose to use .Net ClickOnce as the deployment model. Due to network latency issues we would like to deploy the application onto a Windows Server 2008 RDP server as a RemoteApp published application. After working with application we found that we can easily install the application for a single user by running the ClickOnce installer from a full RDP session on the server, however when we attempt to start the application by publishing the deployment startup through a RemoteApp, the found that the application won't start and that no ClickOnce deployment error log file is created. We have confirmed this behavior exists on Server 2008 and Server 2008 R2 but ClickOnce operates correctly when running as a published application on Server 2003 running Citrix Presentation Server 4.5. We found that we could easily duplicate the issue by publishing Internet Explorer as a RemoteApp and attempting to run a ClickOnce sample application available on the Internet. Attempting to find information on this limitation has been difficult. Is this a known issue or limitation with .Net ClickOnce deployment on Server 2008 (and higher) that would prevent ClickOnce from working as RemoteApp?
Duplicating the issue is very easy. Simply publish Internet Explorer in Server 2008 (or 2008 R2 w/SP1) and visit the website below. Attempt to launch the sample ClickOnce application. It will fail to launch and will not generate any information on why it failed. Now logon to the console of the server, open Internet Explorer, and try the operation again. This time it will succeed and you can launch the ClickOnce application. This appears to be a bug in the .Net framework when running a ClickOnce on Server 2008 (and higher) and is only present when running the ClickOnce application as a RemoteApp or as a Citrix published application (on XenApp 5.0 or higher).
Sample Click-Once Sample Application