I am currently experiencing an issue with an install of Server 2012 and trying to provide a pooled windows 7 desktop that is operating in a kiosk mode (to be used by members of the public). The solution has a bit of software that controls the user logon and sits in front of the windows logon. The user enters a pin number and this software will then log into windows with a standard account and then log them out when their sessions expires.
This solution works great if I connect directly to the virtual machine I can connect and leave it there for hours with no interaction and the software waits. However when I connect it through the connection broker if I leave it without any user input from the keyboard or mouse the session disconnects after approximately 6 minuets. If I log into the software the solution works perfectly.
In the session broker logs I see my session come in and get directed to my VM and then when the timeout occurs (6mins) I see the following event logged
Event Log : TerminalServices-SessionBroker
Event ID: 819
Description:
This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.
Does anyone know if their is a setting for the connection broker to change this timeout that is programmed somewhere?
