![]() Not recommended (tweaking Registry Editor) Source: answer. On server : Local Group Policy Editor → Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections → Select RDP transport protocols → Enabled → Use only TCP On client: Local Group Policy Editor → Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Connection Client → Turn Off UDP On Client → Enabled Three ways to implement (probably mutually compatible, but probably only need to do one): Switching to TCP-only does seem a bit more laggy, but the lag is more ordered (which is strangely nicer than the erratic lag) and I've yet to encounter an indefinite hang. RDP seems to behave a lot better with TCP than UDP. Reducing RDP session settings, avoiding audio, and avoiding video seem to help.įull-ish work-around: Disable UDP. Partial work-around: Reduce network strain. A direct local connection may be relatively reliable. Partial work-around: Improve network connectivity. However, TCP-only coupled with trying to improve network connectivity or/and reducing load (such as video and audio) seems to greatly reduce the incident rate. For example, I've had RDP completely freeze even in TCP-only mode. My guess is that the RDP protocol has lost some of its resilience to packets getting lost or out-of-order. Seems to occur primarily when using the UDP protocol under load. No error messages seen client window can be closed and restarted normally. ![]() Other times the RDP session seems to hang indefinitely. Sometimes the RDP session recovers, resuming normal function. Client window is responsive, but the content within it is essentially a static image. To have it run on login, place it in the Startup group atĬ:\Users\USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.RDP session updates oddly, distorting audio and video. ![]() You may stop the script by right-click on the green H icon in the This script was tested on a Windows 10 computer with RDP to a Windows 10 VM.įor some unknown reason, AutoHotkey is unable to re-minimize the RDP windowĪnd re-activate the previously active window, so RDP stays active.Īfter installing AutoHotKey, put the above text in a. TrayTip, Found RDP session, %this_title%, 2, 17ĬontrolSend, ,, ahk_id %this_id% WinGetTitle, this_title, ahk_id %this_id% WinGet, id, List, Remote Desktop Connection RDP window to be the active window and will send an Enter key input. Windows by title, and for each it will set the The script checks every 10 minutes (600000 milliseconds) forĬomputer inactivity. Remote machine (physical hardware, not VM): Win10 Enterprise 1909 There must be some way, some hack, some tool, something that actually works. I simply want to keep my RD session alive until I intentionally disconnect it. mousejiggler.exe (both on my local PC and on the remote PC at the same time).caffeine.exe (both on my local PC and on the remote PC at the same time).How do I keep an RDP session alive from the client side?.I have tried the following, without success: Your Remote Desktop Services session ended because the remote computer Here is the message I receive when my session is forcibly closed by the powers that be, after only 30 minutes of not being actively inside the remote PC via RDP doing something: I am unable to change that duration, I don't have permissions, and my IT people will not change it. This RDP session auto-closes in a very short time of no activity, probably 30 minutes or something. My workstation is Windows 10, and I regularly RDP into another Windows 10 machine, 20 miles away, over a VPN. Yes, I know this question has been asked before, but all the solutions I have read and tried do not work in a locked-down environment in which the domain-level settings are tightly controlled, and even machine-level group policies are partially locked down.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |