Diconnecting to quickly when idle

Johnson, Deb 0 Reputation points
2026-03-25T17:33:10.09+00:00

how to increase time so my desktop does not disconnect so quickly....I go back and forth between remote and home screen and lose my desktop in minutes and have to log in again

Windows for business | Windows Server | User experience | Remote desktop clients
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 43,075 Reputation points Independent Advisor
    2026-03-28T08:48:30.36+00:00

    Hi Johnson, Deb,

    How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

    VP

    Was this answer helpful?

    0 comments
  2. VPHAN 43,075 Reputation points Independent Advisor
    2026-03-25T18:07:12.2133333+00:00

    Hi Johnson, Deb,

    Since you are working on a company computer and do not have administrative rights, directly modifying the local group policy using the gpedit.msc command is unfortunately not an option for you. The session timeouts you are experiencing are being actively enforced by your organization's network administrators to secure idle connections and manage server resources.

    The specific settings causing your rapid disconnects are dictated by domain-level policies that write to your computer's registry, specifically at the HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services path. The values for MaxDisconnectionTime and MaxIdleTime are locked down by your IT department. Because you lack the necessary permissions, any local modifications you try to apply will be blocked by the system or immediately overwritten the next time your computer syncs with the corporate network.

    The most effective way to resolve this is to submit a formal request to your IT helpdesk to have your Remote Desktop session limits extended. You should explain that your daily workflow requires frequent switching back and forth between your local desktop and the remote session, and the current aggressive idle timeout is actively disrupting your productivity. Your IT administrators have the proper authority to adjust the active but idle session policies on the server side or assign a customized policy for your specific user account.

    Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VP

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-03-25T17:33:22.4566667+00:00

    To keep the Remote Desktop session from disconnecting so quickly when idle, increase or remove the session time limits on the server (or via policy), and ensure the idle timeout values are not set too low.

    Use one of these approaches (typically done on the remote/server side):

    1. Configure RDS session time limits via Group Policy
      1. On the remote computer or domain controller, open gpedit.msc (local) or gpmc.msc (domain).
      2. Go to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Session Time Limits.
      3. Configure these policies as needed:
        • Set time limit for active but idle Remote Desktop Services sessions → set to a higher value or to Never.
        • Set time limit for active Remote Desktop Services sessions (if used) → increase or set appropriately.
        • Set time limit for disconnected sessions → increase if sessions are being dropped too quickly after disconnect.
      4. Run gpupdate /force or reboot to apply.
    2. Adjust session limits in the RDS Collection (RDS deployments)
      1. On the server that manages the RDS deployment (usually the Remote Desktop Connection Broker), open Server Manager → Remote Desktop Services.
      2. Select the Collection that hosts the session.
      3. Under Properties tasks, open Session.
      4. Increase the values for idle and active session limits, or disable them if appropriate.
      5. These settings update the registry under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp (for example, MaxIdleTime and MaxConnectionTime).
    3. For Windows 10/11 clients managed via MDM/Intune
      • Use the TS_SESSIONS_Disconnected_Timeout_1 policy (ADMX_TerminalServer CSP) to control how long disconnected sessions remain active. Set a longer timeout or Never if disconnected sessions are ending too quickly.

    If disconnects are irregular (not at a consistent time interval), they may be due to network issues rather than these timeout settings.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.