ad

Great! Thank you very much!

RDP version is set to Latest (not FreeRDP). But it seems that keepAlive option is not helpful in this case.

Here is what I have found:

In the registry at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, create or edit the DWORD value of KeepAliveEnable and set it to 1. This will turn Keep Alives on. This will serve to stabilize the connection by sending 'heartbeat' packets to the client every so often. This will cause an idle connection to be probed every so often just to be sure that the connection is still alive and that the client is still listening on the other side. This will also help prevent disconnects by preventing network devices from killing off sockets that it assumes to be idle. Because terminal services is such a low bandwidth protocol, when a user is idle, no network activity will occur. Some network devices will interpret a connection that is in the idle state for an extended period of time to be a dead connection, and thus will terminate the socket. However, when the user comes out of the idle state, the terminal services client can no longer contact the terminal server because the socket is dead. By turning on Keep Alives, the connection will not appear idle, and therefore the network device will not attempt to terminate the socket.

But we are talking about another case here. If there is some timeout set on RDP server for inactive user's sessions then RDP server will disconnect such session (This policy: Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Session Time Limits).

To prevent it a user must make some mouse moves or any other input. So the solution for this could be periodically sending some mouse move or some "safe" key press to an inactive session.

Thanks, I have already tried that option and it doesn't work for me. I have set it to 300sec, but I'm still get disconnected from RDP session after some time of inactivity (15 mins in my case). I have tried on several different RDP servers (2008 R2, 2012 R2 and 2016).

Windows.

Hi!

Same question here :)

Is it still planned to implement this functionality?