Users Connecting via RDP to Windows 2019 server unable to return to running session with applications open

MarcoCruz5 1 Reputation point
2020-08-21T19:31:58.447+00:00

Hey there,

I have users RDPing to a Windows 2019 Server.

Users are complaining that they cannot reconnect (by clicking on the X to close out the RDP session) and have their programs still running.

I know Windows 2019 is still pretty new, but I've been trying to find answers and haven't been able to solve this.

Do any of you know about specific RDP settings/configurations that should be enabled or disabled for this?

I'm at a loss.

Thanks y'all

Windows for business Windows Client for IT Pros User experience Remote desktop services and terminal services
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Andy YOU 3,076 Reputation points
    2020-08-24T09:33:21.547+00:00

    HI Usually RD Connection Broker will reconnect the user to the correct RD Session Host server and their interrupted session.

    1. Could you please provide more details about your RDS environment?
      1. which rds server role have you built?
      2. How many Session Hosts and are they in the same collection ?
      3. How many collections have you created in the Connection Broker?
    2. Does this issue happen only to one collection or all the collections?
    3. Have you tried query session command, is there a different session ID when you reconnect?
    4. Is there any event logs that has captured some details regarding this issue? Enable the Analytic and Debug logs Event Viewer first.

    Check on CB server: Applications and Services Logs-> Microsoft-> Windows-> TerminalServices->SessionBroker

    Check on SH server: Applications and Services Logs -> Microsoft -> Windows -> TerminalServices->LocalSessionManage

    RDS server roles: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-roles

    RDP event logs: http://woshub.com/rdp-connection-logs-forensics-windows/

    Reference document/link: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/query-session https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-roles http://woshub.com/rdp-connection-logs-forensics-windows/


  2. Andy YOU 3,076 Reputation points
    2020-08-27T06:29:38.267+00:00

    HI
    1.can you enter below powershell command on issue w2019 server then look if we installed "remote desktop session host" role ?can you also check if you install remote desktop licensing and remote desktop connection broker in this issue w2019 or other member server by using below ps command ?
    Get-WindowsFeature | where name -Like “rds*”

    2.in general,if we not install "remote desktop session host" role on w2019,there will be only 2 concurrent active session for 2 users.so if we want to more than 2 users remote access w2019 concurrently ,we must install "remote desktop session host" role and we also need to install RD licensing role then enroll the RDS cals on RD licensing server. in past, I saw some IT friends didn't install "remote desktop session host "role and "fsinglesessionperuser" registry key to 0 then cause end users can not reconnect to exist session.

    can you check the value for "fsinglesessionperuser" registry key on your issue is 1?by default it should be 1.
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services\
    "fsinglesessionperuser"=dword:00000001
    HKEY_LOCAL_MACHINE\Software\WOW6432note\policies\Microsoft\Windows NT\Terminal Services
    "fsinglesessionperuser"=dword:00000001

    we can enter gpedit.msc in command prompt on issue w2019session host server.
    Go to Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections.
    Set Restrict Remote Desktop Services user to a single Remote Desktop Services session to Enabled.

    0 comments No comments

Your answer

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