I have a LOB application deployed on Server 2008 R2 as a remote app. The program has a process where it calls MS word and opens a document to merge data then print the document.
Everytime we run the process that is supposed to launch MS Word and merge the document it “hangs”. But I can see that winword has started in the background for the user. It seems that the RemoteAPP session is not able to call winword and interact with it.
Do I have to go back to a traditional terminal services where the user connected to a “desktop” session or is there a setting that I have missed that will allow winword to be called into an active session for a different remoteAPP?