Hi!

I am testing RDS 2019 with RemoteApp, and I have problems with startup splash screens. Each splash screen creates a button on the client’s taskbar and does not disappear from desktop and taskbar after the appearance of the main window. For example, I run three RemoteApp and I have three splash screens and three program windows on my desktop. And even if I close these windows, the splash screens will still remain on desktop and cannot be closed. This happens only in RemoteApp and does not occur with a remote desktop mode. I tried to recreate an RDS farm again, but it does not help.

This does not happen with all programs (having splash screen), but with many. At the same time, there were no such problems at RDS 2012R2/2016. 

As RDCB and RDSH used Windows Server 2019 with latest cumulative update (2019-01). As clients used Windows 10 1709/1809 with same update.

Hello there,

Here is the setup. I have a user who is working remotely. She uses remote desktop for one of her database-heavy applications. Unfortunately this application has trouble printing to redirected printers, and can only print to shared or local printers. This is per the company that provides our tech support for the application (NCR CounterPoint), so we have a local USB printer installed on her local computer. It is shared from the local computer and then installed on her profile on the remote desktop server.

She connects back to the office over a VPN. The remote desktop server is located back at the office. Her internet connection is fairly fast and reliable. Average ping time from my PC at the office to her PC at home is about 53ms. I originally suspected the internet connection, but I'm not totally convinced that's that problem. We have plenty of other users set up the same way on the same server, and they don't have this problem.

Through troubleshooting, it's seems that the shared printer can take a few minutes to show up in the Devices and Printers of her profile on the remote desktop server. Other times, it never shows up at all. No matter how long she leaves the session open. I have tried reinstalling the shared printer on her profile on the remote desktop server and sometimes will receive an error message that says something like, "Unable to connect to printer". I will restart the print spooler on both her computer and the remote desktop server, but this doesn't seem to make a difference.

I've even tried making her a local admin on the RDS server and sometimes this will allow me to reinstall the printer. Sometimes I will still get the same error message. I have dug through the event logs of both the server and her computer, but can't find anything that indicates what might be causing this to happen.

I've had her gracefully sign out of the RDS session by going to "Start -> Sign Out", as opposed to just disconnecting it. It doesn't seem to make a difference. She also uses a Remote App for one of her other applications, so I'm not sure if this is conflicting with her RDS session in some way. Again, we have other users set up this way and they seem to be fine.

The main issue is that the shared printer from her local computer installed on the RDS server just doesn't show up sometimes, and then she can't print. When it does show up, it stays there the whole time until she closes the RDS session. The next time she opens it, the printer may or may not appear.

She is using Windows 10 Pro 64-bit. The server is Windows Server Standard 2016 64-bit.

Any ideas?

Thank you!

Can't connect to different 2019 RDS farms from the RD Web Site launched from a server OS. The connection hangs on starting for minutes, before getting a general error that the connection can not be established.

Have this problem from several server OS (2012 R2, 2019), and have tried different browsers. Have not this problem when connecting from a Windows 10 client, so it must be something with the Remote Desktop Connection App on all server OS.

Thank you in advance for any hint or advice.

Franz

We have a remote desktop infrastructure with multiple Brokers and Gateways that redirect connections to a pool of servers. All of the servers are Windows Server 2019. After a user logs off of their session that was connected through the gateway, the rdp client never exits and stays at a black screen.

Is there a solution to this issue?

Thanks

i have a very functional RDS environment.  1 vm running gateway, broker, and licence.  Two vm's running session host servers.  Both the session host servers have NVIDIA Tesla cards directly attached.  I'm trying to shadow the users by right clicking on the connections from server manger.  It displays the RDS client like it's going to connect but it never does.  It does prompt the user if i request it.  If i try it again right away it prompts an error that a shadow session has already begun. 

I've edited the local group policy of the session host server to allow shadowing, and I've check the user permissions in  AD to allow remote control.

IT guy

We have 2 Connection broker server in a HA Environment, suddenly one server stopped working and we are getting the below error when we tried to query in powershell

Get-RDServer : To configure the Remote Desktop management server for a high availability deployment, provide an active
Remote Desktop management server name for the RD Connection Broker server.
At line:1 char:1
+ Get-RDServer
+ ~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDServer

Any Thoughts will be greatly appreciated 

Regards Niroshan Ezra Paulsingh My Blog | http://exchange2010info.wordpress.com/

Hi,

Everyday I have to reboot our RDS on Server 2016 because of failed login attempts for all users. Getting these errors:

An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070057) 

The Windows logon process has unexpectedly terminated. Event 4005, Winlogon

There was an expired certificate error which is resolved. There was also a licensing issue, which is also resolved.

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.

I may finally be out of my depth. (Clients are not on the domain) . Clients = windows 10; servers 2016

My network has its own DNS, and the FQDN of the servers are not within public DNS. remote clients use a public FQDN that matches the IP of the serves. Internal everything is <server>.private.net. outside it is <server>.<company name>.com (the servers are clueless about their public fqdn).

Here is the thing. NLA on and NTLM off. Clients can RDP into the domain controllers! Obviously there are certificate errors, but let's live with that for the moment. However all member servers get is a "this function request is not supported" "this could be due to credssp encryption oracle remediation". ALL SERVERS ARE FULLY PATCHED, 

Lets not forget that... remote clients can connect to the domain controllers. 

Obviously users are not connecting to the domain controllers, its just me with a user account 

We do have a RDP gateway (but I am testing without it to narrow down the problem),

Hi Evryone,

what is difference between quick start and standard deployment on rds Services.

Best regards,

AHL

AHL1988

Hi,

So I have a basic test environment in order to design an RDP solution. I have two former Terminal Servers that both have the Session Host roles installed, one has the Connection Broker role the other has the Web Access role and BOTH have the RD Gateway roles. So basically, my two Session Hosts are also both RD Gateways and one is the broker and the other the Web Access.

I can connect to all of my member servers via RDP happily through the Gateway and when I open the Gateway Manager I can see every connection made. Three connections per session (1 x TCP and 2 X UDP). My issue is there doesn't seem to be any Load Balancing between the two Gateway Servers. Both servers are in a Farm and I have a DNS RR created for the Farm name. Also a collection has been made to include both Session Hosts and DNS records created for the Collection name, in the collection properties I have set Load Balancing to 100 Relative Weight for both servers.

For whatever reason every single connection goes through just one Gateway, no matter how many connections I make the second Gateway server never gets any connections. In the event of restarting or shutting down the active Gateway my live connections migrate across to the still reachable Gateway and any new connections from then on will also be made through the reachable Gateway, even when the unreachable Gateway is back up and running.

Happy that my live sessions migrate to the available Gateway in the event of losing one but can't figure out why the sessions will only be made through one Server and not spread between the two.

Any ideas?

Cheers

Andy

Hi we have a HA env't built for our RDP ENv't

2 RD Connection Brokers

1 Licensing Server

3 RD Web Access Servers

5 RD Session host Servers

2 RD Gateway Servers

we have 3 Collection - Contractors, Employees, Guests

The Env't has been built for a few months the Contractor and Guests is working fine - moderate users maybe 25 on at a time.

The Employee Collection at this time only has about 10 users for Piloting....many of the users at different times of the day get a random black screen and cannot work.

We tried to figure it out, but then gave up and ended up deleting on of the UDP Session Host Servers and redeployed the VM to a different ESXi Host, rebuilt the Session Host and for the past week it has been fine.

I wanted to do a full healthcheck, best practises on the env't as we did not setup this env't - it was built by a consulting firm who no longer is helping.  Any suggestions on how to determine if things are setup right, what could be improved, missing...?

Thanks,

Hello!

I have been struggling with downloading pulished Remote App's from RD Web from external network for couple of days. I'm kind of stuck and our customer is behind my nack... :)

Here follows description of environment and  description how to reproduce error:

Environment:
1. 4 servers each with own RDS Role (Connection Broker, Web Acces, Gateway and RD SH) installed on Windows server Datacenter 2019 
2. All servers have internal nework IP's and are joined to domain
3. In front off RDS there is WAP in DMZ (Public IP nats to WAP servers which are pointing to RD Gateway and Web Access server)
4. ADFS authentication integreted and works fine.

Everything works fine from internal network. (Including download of Remote App published files via Chrome, Firefox,...)

From external network I am able to run RDP without problem. I am able to autenticate to RD Web. But, when I try to download published app from RD Web via Chrome or Firefox or Edge download process i kind of stuck on 7.15 KB. After some time I suppouse some timeout I get error "Unsuccessfull - Network error".

I did some debug'ing through different browsers and it seems to me that Remote App download is stuck on dialog box / pop up which never appears. It is hidden somewhere. Somehow. 

Just to mention that everything works fine from external network when using IE. Our customer refuses to use IE ... :| 

Any help or suggestion on how to resolve this  problem would be appreciated.

Thank you very much in advance.

Regards, 
addy

According to ms docs, windows 2016 server multiuser session has 3 ClientProtocolType:

https://docs.microsoft.com/en-us/windows/win32/api/wtsapi32/ne-wtsapi32-wts_info_class

0 The console session.

1 This value is retained for legacy purposes.

2 The RDP protocol.

But our remote desktop software requires  a custom protocol run on multiuser sessions. Is there any dll or plugin mechanism in windows 2016 server to replace RDP with another user defined protocol?

Hi Guys,

I  have a problem with redirection of local client webcam to Session Hosts in  RDS 2019 Farm.

the farm is composed of:

-2 RD Web Access (HA configured)

-2 RD Connection Broker (HA Configured)

-1 RD Gateway and Licensing

-12 RD Session Host

OS: Windows Server 2019 64Bit 1809

I have already performed these steps:

-GPO "Allow audio and video playback redirection" (enabled)

-GPO "Do not allow supported Plug an Play device redirection" (Disabled)

-GPO "Allow RDP redirection of supported RemoteFX USB devices from this computer" (enabled)

-GPO "Enable RemoteFX encoding for RemoteFX client designed for WIndows Server 2008 R2 SP1" (enabled)

-In the Broker Server i have run in powershell --> Set-RDSessionCollectionConfiguration -CollectionName "CollectionNAME" –CustomRdpProperty “usbdevicestoredirect:s:*”

Hello,

We have a potentially unique use of RDS to broker/load balance the connection to a 30+ physical (not vms) windows 10 machines pool (educational computer lab). The intent is to have individuals interface with the RDS broker, which will connect them to an available Windows 10 machine. What we'd like to avoid, is publishing IP/HOSTNAME of all available computers in the lab and have individuals manual cycle through each until they find availability, or to assign groups to a single machine, as this seems to be an administration nightmare.

Is this possible with RDS, as I've unfortunately not been able to find anybody asking a similar question? Is it as simple as using the redirection function to a VM pool, but pointing it towards a physical machine pool?

Any resources are appreciated, as well as any other methods of achieving the intend connection brokering to available machines.

Thank you,

J

Hi,everyone

   A few day ago, i installed a windows 2K8 R2 as a terminal server ,and specify itself as a terminal licensing server ,but without install any CALs.So erevytime i logged into the terminal , system will pop up a message said that the terminal server's grace period will expired at xxx days. but due to someone unchecked the message , systme can't pop up any message talked about the grace period.

  So can anyone tell me where can i find the remaining grace period  ??