Issue with Remote Desktop sessions as i cannot reconnect to previous sessions and users face unexpected behavior

Scott Lee 20 Reputation points
2026-10-19T17:03:09.3633333+00:00

Hello, I urgently need assistance troubleshooting our enterprise Remote Desktop session hosts.

I have noticed users repeatedly failing to restore their active work environments. My session policies were applied across the company domain, and our active connection limits are no longer behaving as intended.

I have verified multiple disconnected sessions, but all reconnection attempts fail or spin up a new temporary desktop. I have important corporate operations and daily business tasks depending on these systems.

I understand that the host server must properly enforce session states and profile disks. Could you please tell me whether there is any specific diagnostic procedure available to inspect session policies, disconnected-session limits, and user profile initialization, or connect me with someone who can review my remaining troubleshooting options?

Windows for business | Windows Server | User experience | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-19T17:03:28.2133333+00:00

    Use this diagnostic path for the reported RDS behavior:

    1. Distinguish lock vs disconnect vs new-session reconnect behavior.
      • A disconnected RDS session usually closes the RDP window with an error message, while the session continues on the server.
      • If disconnects happen without a consistent timing pattern, investigate network issues rather than configuration.
    2. Check whether session time limits are forcing disconnects.
      • Review these settings in the RDS deployment on the server managing the deployment: Collection > Properties tasks > Session.
      • Review Group Policy at: Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits.
      • Relevant registry locations:
        • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
        • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
        • HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Terminal Services
      • MaxIdleTime and MaxConnectionTime are REG_DWORD values and are expressed in milliseconds.
      • Policy precedence matters:
        • Policies override default configurations.
        • Computer policies override user policies.
      • After changing these settings, users must reconnect or sign out/sign in.
    3. If users cannot reconnect to the same session and are being placed into a new session, enable keep-alives.
      • Configure Configure keep-alive connection interval in: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
      • The keep-alive interval determines how often, in minutes, the server checks session state.
    4. Recheck RD Session Host security settings if reconnects still create a new session.
      • In Group Policy, review: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
      • On the RD Session Host server:
        1. Open Remote Desktop Session Host Configuration.
        2. Under Connections, right-click the connection and select Properties.
        3. On General, review Security layer.
        4. Review Encryption level.
    5. Verify connection limits if active connection limits are not behaving as intended.
      • Confirm Remote Desktop is enabled in System > Remote settings > Remote Desktop.
      • Review the Group Policy setting: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Limit number of connections
      • On the RD Session Host server, also review Remote Desktop Session Host Configuration > Connections > Properties > Network Adapter > Maximum connections.
      • If Maximum connections is dimmed, the Group Policy setting is applied.
      • For administration-only use, Remote Desktop supports two concurrent remote connections by default. More than two administrative or multiple user connections require the RD Session Host role and appropriate RDS CALs.
    6. For deeper diagnostics, collect data while reproducing the issue.
      • Microsoft provides a diagnostic collection procedure using TSS.
      • Run from an elevated PowerShell prompt: 
             .\TSS.ps1 -Scenario UEX_RDSsrv -start  -UEX_Logon
      • This is the documented next step when the standard checks do not resolve unexpected session locks or disconnections.

    The provided material does not include a procedure for inspecting user profile initialization or profile disks specifically. It does provide a supported procedure for inspecting session time-limit policies, reconnect behavior, connection limits, and collecting diagnostics for escalation.

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

    Was this answer helpful?

  2. HLBui 15,190 Reputation points Independent Advisor
    2026-10-19T18:12:24.1833333+00:00

    Hi Scott Lee

    Based on what you're describing that the session host is not successfully reconnecting users to their existing disconnected sessions, or that user profile technologies such as FSLogix profile containers are not mounting correctly during logon. In environments like this, I would typically start by reviewing the active Group Policy settings that control session time limits, disconnected session handling, and reconnection behavior, as a misconfigured policy can cause the platform to launch a new session instead of reconnecting to the original one.

    I'd also checking the TerminalServices and Remote Desktop Services event logs in Event Viewer, along with any FSLogix operational logs if profile containers are being used. These logs usually provide valuable clues regarding session state transitions, profile initialization failures, authentication issues, or profile disk attachment problems. Another useful step is to compare the disconnected session state reported on the host with the actual user session information returned by tools such as query user and qwinsta, which can help identify orphaned or inaccessible sessions.

    If FSLogix is deployed, verify that the profile container paths are reachable, VHD/VHDX files are not locked, and that profile attachment is succeeding during sign-in. I would also review any recently applied GPO changes, especially those related to session limits, idle session policies, and "Restrict Remote Desktop Services users to a single Remote Desktop Services session."

    At this stage, a structured review of Group Policy Results (GPResult), RDS event logs, and profile container logs would be the most effective diagnostic approach before escalating further. These data points usually help isolate whether the issue is policy-related, profile-related, or tied to the session host infrastructure itself.

    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.