I am running Server 2012 and my Clients are launching an RemoteApp from the Work Resources RD Web Access page in IE. Everything is working fine in this regard.
The problem is this. The first time the users launch the RemoteApp the printer maps in about 6 seconds which is good. If they close the RemoteApp and then Reopen it within the next 2-3 hours it take about 1 minute and 6 seconds for the printer to map. After 2-3 Hours of being disconnected it goes back to mapping in 6 seconds.
The "RemoteApp Session Logoff Delay" in Group Policy is set to "Immediately".
That being said if I logon using a regular RDP connection to a Remote Desktop and Logoff in the normal fashion then re-launch the same RDP Connection, the printer maps in the normal 6 seconds.
If I force "Log off" a RemoteApp RD Session through the Server Manager Connections window and then log them back on immediately after, the printer maps in the normal 6 Seconds.
I have checked both the Active Sessions in Server Manager and the Printer Management Window to make sure the RD Web Sessions and its associated printer have disconnected but there is something hanging around in the background when an RD Web Session RemoteApp is closed that Server 2012 sees as still active. In short when the users closes the RD Web RemoteApp it is not doing a complete Logoff of the session for more than 2 hours.
I have checked every setting in GP I can think of but can't find anything other than the "RemoteApp Session Logoff Delay" that indicates it would change this behavior. Please advise if I have missed a setting or I have found an actual bug that requires an update to correct.
I'm a patient person but for a cashier to have to stand in front a paying customer waiting for a printer to map so they can have their receipt, an extra minute can be a long uncomfortable time.