none
RDS 2016 - RemoteFX killing connections RRS feed

  • Question

  • We have a new Windows 2016 server, hosted under VMWare ESXi 6.5u1.  The host does not have a 3d accelerator, and none is presented to Windows 2016.  The host also has a Windows 2012 R2 RDS server, which functions flawlessly.

    After installing the RDS role in 2016 and configuring a couple RemoteApps, I have noticed a sporadic issue where the client will be unable to connect.  The client receives the following error message:

    "Because of a protocol error (code: 0x112f), the remote session will be disconnected. Please try connecting to the remote computer again."

    While the server's Operational log of RemoteDesktopServices-RdpCoreTS shows what follows.  This log was cleared just prior to a failed connection, and includes all the messages from connection to disconnection.

    Level,Date and Time,Source,Event ID,Task Category
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,103,RemoteFX module,The disconnect reason is 0
    Error,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,227,RemoteFX module,'Failed to get property Disconnect Reason' in CUMRDPConnection::Close at 2212 err=[0x80070057]
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: GetServerAutoReconnectInfo
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: GetServerAutoReconnectInfo
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: DisconnectNotify
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Geometry::v08.01 has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::DisplayControl has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel cliprdr has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rail_ri has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rail_wi has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rail has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdpsnd has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdpdr has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Geometry::v08.01 has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Video::Data::v08.01 has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Video::Control::v08.01 has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel ECHO has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Graphics has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Frame_Buffer::Control::v08.01 has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdpgrfx has been closed between the server and the client on transport tunnel: 0.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel PNPDR has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: SetErrorInfo(0x0)
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: PreDisconnect(0)
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,228,RemoteFX module,"Disconnect trace:CUMRDPConnection Disconnect trace:'calling spGfxPlugin->PreDisconnect()' in CUMRDPConnection::PreDisconnect at 4477 err=[0x0], Error code:0x0"
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdplic has been closed between the server and the client on transport tunnel: 0.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdpcmd has been closed between the server and the client on transport tunnel: 0.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel rdpinpt has been closed between the server and the client on transport tunnel: 0.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,145,RemoteFX module,"During this connection, server has not sent data or graphics update for 0 seconds (Idle1: 0, Idle2: 0)."
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,102,RemoteFX module,The server has terminated main RDP connection with the client.
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: OnDisconnected(server initiated)
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,143,RemoteFX module,"TCP socket WRITE operation failed, error 1236"
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,142,RemoteFX module,"TCP socket READ operation failed, error 1236"
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,97,RemoteFX module,The RDP protocol component WD detected an error (303) in the protocol stream and the client was disconnected.
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,226,RemoteFX module,RDP_GFX: An error was encountered when transitioning from PipeStateError in response to PipeEventOnError (error code 0x80004005).
    Warning,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,226,RemoteFX module,RDP_GFX: An error was encountered when transitioning from PipeStateEncoding in response to PipeEventOnProtocolClosedFailed (error code 0x80004005).
    Information,12/1/2017 1:01:11 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:01:00 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:01:00 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:01:00 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rail has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:54 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel cliprdr has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::DisplayControl has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Error,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,227,RemoteFX module,'Failed CreateVirtualChannel call on this Connections Stack' in CUMRDPConnection::CreateVirtualChannel at 2349 err=[0xd0000001]
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Input has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Input has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel URBDRC has been closed between the server and the client on transport tunnel: 1.
    Error,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,227,RemoteFX module,'Failed CreateVirtualChannel call on this Connections Stack' in CUMRDPConnection::CreateVirtualChannel at 2349 err=[0xd0000001]
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Geometry::v08.01 has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel URBDRC has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel PNPDR has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: LogonNotify(SessionId=4)
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,"Interface method called: SendLogonErrorInfoToClient(WinlogonStatus: 0x4, ClientError: 0xfffffffe)"
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel AUDIO_PLAYBACK_DVC has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel AUDIO_PLAYBACK_LOSSY_DVC has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel AUDIO_PLAYBACK_LOSSY_DVC has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel AUDIO_PLAYBACK_DVC has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rdpdr has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,257,RemoteFX module,The connection is using advanced RemoteFX RemoteApp graphics.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,148,RemoteFX module,Channel Microsoft::Windows::RDS::Telemetry has been closed between the server and the client on transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,68,RemoteFX module,"TMT: ConnectionName=RDP-Tcp#3, PromptForCredentials=0, PromptForCredentialsDone=0, GfxChannelOpened=1406, FirstGraphicsReceived=1625 [ms]"
    Error,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,227,RemoteFX module,'Failed GetConnectionProperty' in CUMRDPConnection::QueryProperty at 2735 err=[0x80004001]
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,166,RemoteFX module,The RemoteFX Adaptive Graphics internal configuration changed to optimize for the minimum use of network bandwidth. Server: P21WEB
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,168,RemoteFX module,"The resolution requested by the client: Monitor 2: (1680, 1050), origin: (1680, 0). Server: P21WEB"
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,168,RemoteFX module,"The resolution requested by the client: Monitor 1: (1680, 1050), origin: (0, 0). Server: P21WEB"
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,168,RemoteFX module,"The resolution requested by the client: Monitor 0: (2048, 1152), origin: (3360, 0). Server: P21WEB"
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Geometry::v08.01 has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Video::Data::v08.01 has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Video::Control::v08.01 has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: ConnectNotify(SessionId=4)
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,162,RemoteFX module,"The client supports version 0xA0200 of the RDP graphics protocol, client mode: 0, AVC available: 0, Initial profile: 2. Server: P21WEB"
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Graphics has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel Microsoft::Windows::RDS::Telemetry has been connected between the server and the client using transport tunnel: 1.
    Information,12/1/2017 1:00:53 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,135,RemoteFX module,"The multi-transport connection finished for tunnel: 1, its transport type set to UDP."
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: OnReady
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: OnConnected
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,169,RemoteFX module,"The client operating system type is (1, 3).  Server: P21WEB"
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,135,RemoteFX module,"The multi-transport connection finished for tunnel: 1, its transport type set to UDP."
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rdpinpt has been connected between the server and the client using transport tunnel: 0.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rdpgrfx has been connected between the server and the client using transport tunnel: 0.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,33,RemoteFX module,Remote Desktop Protocol will use the RemoteFX guest mode module to connect to the client computer.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,66,RemoteFX module,The connection RDP-Tcp#3 was assigned to session 4
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: PreCreate
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,131,RemoteFX module,The server accepted a new UDP connection from client [192.168.10.50]:58399.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,229,RemoteFX module,'Cid[3] UDP connection received SYN with data. ISN[1239185757] MTU: U[1232] D[1232] SynEX[1] Version[2] Prefered[2]' in CRdpUdpConnection::OnDataAvailable at 753 err=[0x0]
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: AuthenticateClientToSession
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,130,RemoteFX module,"The server has initiated a multi-transport request to the client, for tunnel: 1."
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,135,RemoteFX module,"The multi-transport connection finished for tunnel: 3, its transport type set to TCP: Reason Code: 2 (Forced by Server Configuration)."
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,100,RemoteFX module,The server has confirmed that the client's multi-transport capability.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,98,RemoteFX module,A TCP connection has been successfully established.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: ProtocolComplete
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: SendClientLicense
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: GetSecurityFilterCreds
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,104,RemoteFX module,Client timezone is [-7] hour from UTC; 
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: AcceptConnection
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: OnStartLicensing
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rdpcmd has been connected between the server and the client using transport tunnel: 0.
    Information,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,132,RemoteFX module,A channel rdplic has been connected between the server and the client using transport tunnel: 0.
    Warning,12/1/2017 1:00:52 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,101,RemoteFX module,The network characteristics detection function has been disabled because of Reason Code: 2(Server Configuration)..
    Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,141,RemoteFX module,PerfCounter session started with instance ID 3
    Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: SendPolicyData
    Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,72,RemoteFX module,Interface method called: PrepareForAccept
    Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,65,RemoteFX module,Connection RDP-Tcp#3 created 
    Information,12/1/2017 1:00:51 PM,Microsoft-Windows-RemoteDesktopServices-RdpCoreTS,131,RemoteFX module,The server accepted a new TCP connection from client 192.168.10.50:57884.
    

    It looks like RemoteFX fails to set things up correctly, before eventually giving up and killing the session.

    I've already tried using GPO to disable RemoteFX.  Seems like Microsoft has decided to ignore its own policy settings.

    Anyone out there have any ideas?  

    Thanks in advance.

    Friday, December 1, 2017 8:23 PM

Answers

  • Problem solved.  I was correct -- it was RemoteFX.

    I had first tried disabling it via GPO.

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

    Select network detection on the server: Enabled, Turn off Connect Time Detect and Continuous Network Detect

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

    Enable RemoteFX encoding for RemoteFX clients desined for Windows Server 2008 R2 SP1:  Disabled

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > RemoteFX for Windows Server 2008 R2

    Configure RemoteFX: Disabled

    Optimize visual experience when using RemoteFX: Disabled

    Optimize visual experience for Remote Desktop Service Sessions: Enabled, text

    I rebooted after changing each of the above.  None of these settings made any difference.

    But the logs continued to show RemoteFX bombing out.

    I went digging in the registry, and found this:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

    DWORD:  fEnableRemoteFXAdvancedRemoteApp:  0x00000001 (1)

    According to the the internet this value enables RemoteFX for RemoteApps.  And it was defaulted to enabled.  Bingo!  I set it to 0, restarted, and all problems are solved.  The logs now show RemoteFX being disabled when the RemoteApps launch.

    So, lesson learned on RDS 2016.  For some bone-headed reason, Microsoft defaults to using RemoteFX and ignores GPO concerning RemoteFX when it comes to RemoteApps.


    • Edited by ltwally1 Monday, December 4, 2017 12:41 PM
    • Marked as answer by ltwally1 Monday, December 4, 2017 12:41 PM
    Monday, December 4, 2017 12:40 PM

All replies

  • Hi,

    Please verify whether the GP setting is applied by running command below as administrator:

    GPresult /h C:GPresult1.html

    Do different client systems and user accounts face the same issue? Please try to find a pattern regarding how and when the issue would occur to better analyze the issue.

    In addition, I suggest lower the resolution on clients and fully patch Windows systems to test.

    If possible, please try reboot the RDS server to see whether the issue persists.

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 4, 2017 3:07 AM
    Moderator
  • Problem solved.  I was correct -- it was RemoteFX.

    I had first tried disabling it via GPO.

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

    Select network detection on the server: Enabled, Turn off Connect Time Detect and Continuous Network Detect

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

    Enable RemoteFX encoding for RemoteFX clients desined for Windows Server 2008 R2 SP1:  Disabled

    gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > RemoteFX for Windows Server 2008 R2

    Configure RemoteFX: Disabled

    Optimize visual experience when using RemoteFX: Disabled

    Optimize visual experience for Remote Desktop Service Sessions: Enabled, text

    I rebooted after changing each of the above.  None of these settings made any difference.

    But the logs continued to show RemoteFX bombing out.

    I went digging in the registry, and found this:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

    DWORD:  fEnableRemoteFXAdvancedRemoteApp:  0x00000001 (1)

    According to the the internet this value enables RemoteFX for RemoteApps.  And it was defaulted to enabled.  Bingo!  I set it to 0, restarted, and all problems are solved.  The logs now show RemoteFX being disabled when the RemoteApps launch.

    So, lesson learned on RDS 2016.  For some bone-headed reason, Microsoft defaults to using RemoteFX and ignores GPO concerning RemoteFX when it comes to RemoteApps.


    • Edited by ltwally1 Monday, December 4, 2017 12:41 PM
    • Marked as answer by ltwally1 Monday, December 4, 2017 12:41 PM
    Monday, December 4, 2017 12:40 PM
  • Hi,

    I´m facing the same issue with no other changes to W2012 RDS server for long time except Windows updates, when we restart the server connections works for some period and then stops with the msg:

    "Because of a protocol error (code: 0x112f), the remote session will be disconnected. Please try connecting to the remote computer again."

    I'll check if changing the value to '0' on the reg key cited (below) can help us and ping back here:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

    * Even TeamViewer to this server is impossible.


    • Edited by 9073241516 Sunday, October 21, 2018 12:00 PM .
    Sunday, October 21, 2018 11:59 AM
  • On the customer's server, I didn't found this value 'fEnableRemoteFXAdvancedRemoteApp' but we realize pending Windows updates and also '0' free disk space.

    After restart, wait for updates finish and also delete '%windir%\softwaredistribution\download' contents (more than 700mb), seems to be fixed again.


    • Edited by 9073241516 Sunday, October 21, 2018 6:39 PM .
    Sunday, October 21, 2018 6:38 PM
  • I have similar error , but server not have virtual role.

    Before error messages:

    The server accepted a new TCP connection from client 10.16.168.6:52609.

    Connection RDP-Tcp#0 created

    and after it a error:

    EventId 226

    RDP_TCP: An error was encountered when

    transitioning from StatePreparingX224CC

    in response to Event_ERROR_SendingX224CC (error code 0x0).

    from source  RemoteFX module

    and not possible connect by RDP

    have any ideas?

    Monday, April 15, 2019 3:30 PM
  • Actually you don't need to manually edit the registry value: 

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

    DWORD:  fEnableRemoteFXAdvancedRemoteApp:  0x00000001 (1)

    The value above is mapping below configuration in Group policy:

    Computer Configuration /Policies / Administrative Templates /Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment 

    Set the Use Advanced RemoteFX graphics for RemoteApp to disabled.

    In this way the configuration can be deployed easily.

     


    • Edited by FrankFu85 Friday, May 15, 2020 2:04 AM
    Friday, May 15, 2020 2:03 AM