The company that I am consulting with has an issue with an in-house developed application that they are trying to publish to clients via RemoteApp from a Windows 2008 R2 server. The app has a Java front end and talks to a back end SQL database. The application should behave as follows:
In the main application window a button is clicked to bring up a data set. In that windows another button is clicked to bring up a selection window. Once a selection is made a button is clicked and the selection window disappears and a progress dialog box pops up. The progress box eventually disappears leaving you back at the data set screen which can then be closed.
The problem is when running via RemoteApp as soon as the progress box finishes and disappears, focus is not returned to the other window to allow closing it. At this point also on the Terminal Server the javaw process starts chewing through 80 - 90%% CPU (although looking at the threads it is msvcrt.exe causing the CPU usage). The only way to close the app is to terminate the process or log off the session.
This behaviour only happens when running as a RemoteApp. If it is run in a full Remote Desktop session the issue does not occur. The problem behavior happens with all versions of the RDC on WinXP SP3, Vista and 7.
The only thing we have found does sort of work is calling runonce /AlternateShellStartup from the logon script. In this case the app will then work normally from the older RDC clients on Win XP and Vista (but still not from any of the latest RDC clients)! On a related note publishing the same app via Citrix fails when using old v9.15/9.20 Citrix clients but works successfully with newer Citrix clients.
So in my mind the issue seems to lie with something the latest RDC client is or isn't doing that is affecting the msvcrt.exe thread on the server. Are there any patches or updates to the client coming up or does anyone know of any other tweaks that may help this focus/client issue?
Thanks,
Aaron