I tried almost everything to get our ClickOnce VB.NET application to work under Terminal Services as RemoteApp. I have a batch file that runs an .application file for an application.
This works fine through an RDP desktop session on a terminal server . However, like TS RemoteApp, well ... not so much.
I get a fast flash command line (batch file) on the client system, and then ... nothing ...
The same goes for the fact that it points to the .application file directly (without using a batch file) or even to copy the publication locally and point to it.
I found technet.microsoft.com a discussion of a similar problem, but there are no permissions in it.
For those who have come across this before and got his job, what do you need to do?
We are currently using RemoteApp for everything else on this server, so I hope to stick with this if possible.
The current workaround is to create and run the MSI installer for the application on our terminal server whenever we publish through OneClick on the network, but sometimes it can be pretty painful and easy to forget to do.
Since the application works fine through Terminal Services when launched in full screen mode, but not during RemoteApp, I don't think this is anything special for terminal server permissions, since ClickOnce requires something that is not available when working as RemoteApp.
source
share