RDS Problem reconnecting to a session

Theo123 1 Reputation point
2021-11-10T09:00:45.097+00:00

Hello,

I am having a problem on my RDS farm (Windows Server 2019) :

After a session is locked, manually by the user or automatically by GPO, when the user tries to reconnect and enters their password, his session does not open and the screen freezes. There is the usual login page, with the logo and the name of the user, but there is no loading circle with the message "Welcome". See the screenshot below.

148059-pb-rds03-copie.png

The problem is encountered by a large number of users with no correlation between their hardware, whether through connections with thin clients or hard clients. The problem appears every day but not at set times.

The RDS farm was installed recently and this problem appeared quite soon after the farm was put into production.
The problem appears on both the RemoteDesktop collection and the RemoteApp collection.

The scenario of the problem :

On the Broker, before the user tries to reconnect, the session appears in Disconnected status.
When the user tries to reconnect and the screen freezes, the session appears in Active status.

From the Broker server, a right click -> Disconnect on the user has no effect.
To unblock the user, the "Windows Logon User Interface Host" process (LogonUI.exe) for the session concerned must be terminated manually. Then, the session is unblocked and the connection to the session works perfectly. The user reconnects to his session and retrieve the documents and applications he had opened, and he reconnects to the same session server.

In the event viewer on the session server, the following errors appear when the user tries to reconnect and screen freeze :

Disconnect trace: CUMRDPConnection Disconnect trace: 'calling spGfxPlugin-> PreDisconnect ()' in CUMRDPConnection :: PreDisconnect at 4595 err = [0x80004004], Error code: 0x80004004

The network characteristics detection function has been disabled due to Reason Code: 2 (Server Configuration).

'Failed GetConnectionProperty' in CUMRDPConnection :: QueryProperty at 2884 err = [0x80004001]

The network characteristics detection function has been disabled due to Reason Code: 1 (Client not supported) ..

'Failed CreateVirtualChannel call on this Connections Stack' in CUMRDPConnection :: CreateVirtualChannel at 2498 err = [0xffffffff]

RDP_SEC: An error occurred while transitioning from FStatePassthrough in response to FEventCheckAndCompleteReadsFailed (error code 0x8007139F).

I have taken the following actions but it still does not work :

-Added registry keys on all session servers:

-HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ SysProcs : csrss.exe = 0
-HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ SysProcs : winlogon.exe = 0
-HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ WinStations : fEnableRemoteFXAdvancedRemoteApp = 0
-HKLM \ SOFTWARE \ Microsoft \ Terminal Server Client : UseURCP = 0
-HKLM \ SOFTWARE \ Policies \ Microsoft \ Windows NT \ Terminal Services : VisualExperiencePolicy = 2

-Farm servers, computers updated with the latest Windows KB.

Thank you in advance for your help.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,252 questions
0 comments No comments
{count} votes

13 answers

Sort by: Most helpful
  1. Milo Sheppard 0 Reputation points
    2023-02-13T11:05:40.4866667+00:00

    Just a quick add to say we're experiencing this issue with W11 multi-session 22H2 in Azure Virtual Desktop.

    User will attempt to log in, get a black screen as their session never logged off and the only way to get it to clear is to manually end the 'Windows Logon User Interface Host' (LogonUI.exe) process.

    0 comments No comments

  2. Richard Hällström 0 Reputation points
    2023-03-14T13:53:06.07+00:00

    On our 2022 servers we experienced black screen with inactive RDP connections.

    This was somewhat related to NetID causing problem with interactive logon timeouts we had setup.

    What we did was setting 2 GPO's to the following settings as a work around until we have a newer NetID to test with to see if the problem remains.

    Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options

    Interactive logon: Machine inactivity limit: 0 seconds

    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits

    Set time limit for active but idle Remote Desktop Services sessions: Enabled

    Idle session limit: Never

    0 comments No comments

  3. CK_MK 10 Reputation points
    2023-04-12T14:31:08.68+00:00
    0 comments No comments