Hey all,
Am hoping you can help with this query.
I have published an old 32-bit application using RemoteApp on Server 2012 R2. We're currently in UAT so the RD setup is fairly simple; 1 server handles the Connection Broker, Gateway and RD Web roles, 1 server is a Session Host where the application is installed, and I have a separate licence server.
Everything runs fine. Application fires up, users can login and test. All good.
The issue is exiting. Once the user completely exits the application, the session disconnects but the published application's exe is still running in memory, so if the user tries to connect again the application thinks it is already running and the user gets a message saying as much. As a workaround I set the disconnected session timeout to be 5 mins (with customer agreement) so that the max they have to wait to get back in again is 5 mins. Oddly, if there is only one session on the session host server, the application exits cleanly. This only seems to be an issue with 2 or more users (which for Production would obvs be a bigger issue).
The servers are housed in our datacentre and as such are not overly hit with GPOs. I can't see anything that would force the exe to stay in memory from a GPO perspective. Process and File monitor didn't reveal any issues as far as I can tell.
Any information of help would be gladly welcomed.
Thanks all,
Dave.





