hello, i have setup rds 2016 server and was noticing that some of the user sessions are stuck in "disconnected" status for a long time. where do i get to set this policy to end these type of sessions after 24 hours?

Hi to all,

In my environment I have a Windows server 2016 that acts as license manager for some other windows 2016 server and some windows 2019 servers.

The problem is that the Terminal Server Licensing Service keeps failing: sometimes it takes a few days for the services, sometimes it happens after an hour.

When that happens, whenever a user tries to login to one of the TS served by the license manager, he receives messages that says " Remote desktop license Issue:  There is a problem with your Remote Desktop license, and you session will be disconnected in 60 minutes. Contact your administrator to fix this problem".

That's the error I see in the event viewer:

Faulting application name: svchost.exe_TermServLicensing, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: lserver.dll, version: 10.0.14393.1378, time stamp: 0x594a188d
Exception code: 0xc0000005
Fault offset: 0x000000000002cb8d
Faulting process id: 0x20f0
Faulting application start time: 0x01d4edf0d90921c1
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\lserver.dll
Report Id: 175b3cbc-338c-43d5-a965-e82d5740b18b
Faulting package full name:
Faulting package-relative application ID:

Can anybody lend me a hand with this?

Thanks in advance

When users attempt to print to their local printer via RDWEB, nothing prints out.  If you log into the Server, manually log them off in the Remote Desktop Services Collection portal, and then rename their local printer to a different name, they can print again.  However, this cycle repeats and I have to keep renaming the local printers in order for them to print.  Anyone have any clue as to how to remedy this?

Frustrated in NY

Hello,

mstsc provides an option to connect to an existing session on remote machine. Does the Remote Desktop ActiveX Control also support this?

Thanks in Advance.

 Best,

Sumit

2 Windows Server 2012 Standard domain controllers

2 RDS Servers running Windows Server 2012 R2

We also have 2 Broker Servers and 2 Gateway Servers

From time to time we are running into an issue where the AD account logs in to Windows fine...but when it comes to our RDS login screen...some user accounts have issue where they login...see the published apps...click on one....the connection begins to handshake...then after a few moments we get:

The User Profile Service service failed the sign-in.

User profile cannot be loaded



Can anyone help me to troubleshoot, please?

I can give any more info that is required. There is a file server where their home directories are stored and on the same server...there are roaming profile folders

The RDS servers load balance...sometimes a user would go on to one...then another session they might be on another.

On the users directory of the RDS servers...the particular user account that is getting this issue...we don't see a user account folder for them...it doesn't get created...it just gets...failed the sign-in?

Hi,

I have 5 Remote Desktop Session Hosts with 14 GB RAM each.

Every day in every RDSH connected 10-12 users 

I have configure a policy to sign out all the users after 4 hours idle to keep it clean after working hours.

My problem is that after 15 days all Remote Desktop Session Host Servers use 6-7 GB RAM without any connection.

For example i can see that keeps 7 GB RAM when connect at night which i am the only in Remote Desktop Session Host Server.

I can't figure out which programm or service use so much RAM.

Can someone help me ?

We have a 3 node Windows 2016 RDSH farm with UPD and user redirected folders enabled. After much trial and error we also managed to customise the start menu, exported it to an .xml and redirect all users start menu to this file. This seemed to workfor a few weeks but we are now seeing issues with the pinned tiles disappearing. 9/10 times the pinned tiles do not show but strangley on the odd occasion they do display correctly. There is no obvious pattern to this. It can be for any user on any RDSH server. We have tried deleting a users UPD and redirected appdata but the issue still occurs. We cannot see any errors within the RDSH event logs for this either.

We've seen and tried several methods for configuring start menus for Win10/Win2016. We would like to define a manditory start menu for all users. Is the a simple, tried and tested way of doing this in Win2016 with UPD and user redirected folders enabled?

I have recently deployed a 2016 RDS server farm. This is being used to publish remote apps to users via RDWeb.

Now, for some strange reason there are 3 seperate applications that I have deployed (All 3 being https URL's via Internet Explorer) which simply log the users off 20 seconds after the app has been launched. No errors are generated inside the Session host at all, simply a user logoff event.

This session host server is responsible for publishing several other applications and this particular issue does not present itself anywhere else. Also to note is that if an existing session exists for that user, then they are able to run the HTTPS published apps without any issues and their session is maintained.

Please help, I am bashing my head in with this one!

I am looking to uncheck the Smart Cards box in Remote Desktop Connections Local Resources > Devices and resources > More... area.

I attempted this by disabling this in GPO under Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection/Do not allow smart card device redirection   however this seems to be a separate setting.

I need this fix to be able to be used in a enterprise environment, not a one off computer.

Hello! I'm currently testing RDP for Windows Server 2019 for later deployment purposes and I am running into an odd problem. On machines that are Hyper-V machines I RDP into if I minimize them and wait a few minutes then restore the window I get a blank screen (color of the desktop). It stays this way for about 5-10 minutes then it recovers. This behavior does not happen on the HyperV host machine.

My environment:

- All Windows 2019 Servers. 1 host, 3 virtualized. All Virtualized servers exhibit the same issue.

- Everything is updated with patches.

- I'm connecting from a Windows 10 machine. Command line returns Version: Microsoft Windows [Version 10.0.17763.379]. winver: 1809 (17763.379)

What I have tried (singularly):

- Disabling UDP using GPO.

- Disabling RemoteFX using GPO.

- A few other Googled results.

Still the problem occurs. I haven't even tested RDS yet and can't possibly roll that out to clients until this is resolved. I have attached a screenshot of what the RDP session looks like after I restore it from the Start Menu bar. 

I would attach a screenshot but looks like I can't with this forum.

Rob Holmes

Hi everyone,

I`m either complitly blinde or dumb, but i can`t find any way to delete certs from deployment properties -> certificates to make them all "not configured" again. May be some one can helps me with that?

Hi Everyone,

I have been working on a problem with our single RDS server for a while now and hope some of u are able to help me out. (just remote app, no desktop sessions)

Alot of users are reporting that their sessions are getting stuck/frozen and need to reopen the application from the RDweb/RDP file to continue working. I saw that once a user experienced this i could take over the session with shadowing and permission could be given from the user while the session is frozen. So i'm guessing it has to be something about the graphics? There is no black screen however. Just a still image of the last frame. If i take over i can move it around and do stuf but stil not visible to the user.

The problem usually starts when they lock their workstation and come back from a short break 5/15 minutes later. Unlocking the workplace would then show the stuck session. Idle times and disconnection times are not to worry about. All above 6+ hours.

I could post lots of logs. But if u would like to see any in specific i would post them.

Specifications:

• Windows server 2016 with latest updates from March. (KB4489889) & (KB4485447)
• All roles are on one server. Broker, Gateway, Session host, RDWEB
• Licening is on another server. And shows no problems with diagnoser. (Just to be sure)
• Clients work on windows 10 1803. RDP version is: 10.5 using HP thin clients.
• 80+ users in terminal.
• It's a fysical server with enough space, memmory and CPU. Speed 10gb.
• The problem usualy happens once a day er person. Good weeks show only once a few days

Hello,

We've search several solutions over the network but in our enviroment nothing helps.

in the company we have a problem with freezing RDS Hosts. Usually looks like:

- Someone is calling to us end tell that some software is crashed and he cannot run it again / Cannot logout/login.

At First we thought that is a software problem (very often we saw that excel has 100% cpu), we've update office 365.

at the Begining of the creash we see error in event log:

"A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect."

Usually it stars with UmRdpService but we recieve it in several another services.

What's more we found strange behavior during this problem - we see that number of active sessions is going down... but total session are growing very fast (example we have 20 sessions on the host, total session ~30, during our crash we have 5 active session but 100 total sessions).

During this crash we usually cannot log into domain accounts, very often we cannot log in local account.

We tried to reset services, disable priter redirection, try to update OS system with Office 365 - no luck.

What's more in the event log we have many errors like:

-20499 "Remote Desktop Services has taken too long to load the user configuration from server \\XXXXXXXXXXXX for user XXXXX

-1152 "Failed to create KVP sessions string. Error Code 0x8007007A"

Hello,

We have configured a Remote Services setup on Windows Server 2016.

On Server01 we have installed Remote Desktop Gateway Server, Remote Desktop Connection Broker.

We have created 10 Session Host Servers. Out of these we have created 2 session collections - each having 2 servers. These are:

SU1 - ServerA + Server B

SU2 - ServerC + ServerD

We want simple load balancing between 2 servers within each unit (SU1 and SU2) so that half of the users will get connected to Server A and half to Server B.

This same configuration was working fine in Windows 2012. But is not working now. Are there any changes from 2012 to 2016 - which we are missing upon?

Thanks,

Rahul Jain

Hi all,

has anyone used the VirtualizeLoopbackAdresses configuration on RDS?

We are currently facing a problem with a SAP/Genesys integration that run on loopback address.

1 user works, multiple users not.

The application bind itself to 127.0.0.1 but we need a different looback address per session.

Any help is very appreciated.

Thanks.

Faq.ini

Dear Support , 

i would like to ask how to resolve the problem with event id 56 and Source name call " TermDD ? 

this is the Terminal server in OS 2008 R2 . 

it was keep prompt the error The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

the situation is remote desktop not function when try to access from client. 

Server restart 1 time after 12 hours will getting this error again. 

thank you 

ray 

Recently, I try hard to  install  sp1 on my server. Its OS is Windows Server 2008 R2, last night, I finally installed the SP1 on server, unfortunatelly, I lost the RDP when the server is restarted after configing service pack.  Could you provide some suggestions to me? Thank you.

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.

We have around 15~ Remote Desktop Session Host servers of varying versions (2012 R2, 2016 and 2019) which are experiencing freezing and flickering issues with "Not Responding" appearing in the top bar and the program being unresponsive when switching between tabs. Other symptoms include screen flickering and, when in Task Manager, the tabs sometimes disappear until you roll the mouse over them. These issues started appearing after the weekend of 23rd March 2019 (23/03/19).

I have been scouring forums looking for other people with the same issue but can't find anyone with similar symptoms except someone called Chris_UKDE and his questions haven't been answered either.

At first, we thought that this was caused by a Windows Update but we have been through all of the updates and cannot find any consistent update or lack of update across the servers that seems to have caused the problem. We thought it might have been KB4489889 but after uninstalling this, the problem still remains.

We have opened a case with Microsoft and we are waiting for them to analyse some logs that they gathered on Friday and they have advised various registry fixes and disabling hardware acceleration but none of these have worked. I am taking to the forums to see if anyone else is a. having any luck with their diagnosis and b. having these issues at all(!) and c. if we manage to fix it, to share it with you so you don't have to experience the same pain we have.

The issue does NOT appear to happen in Safe Mode BUT when running a Selective Startup from MSConfig, these issues still happen, eluding that it's still a Microsoft element causing the problem. We are mainly seeing the problems in Microsoft Office programs but we do get a few issues in other Microsoft programs, such as Internet Explorer/Task Manager and also Chrome.

Most of the servers are running on VMWare ESXi 6.0-6.5 but we do have one native Windows Server with the problem. We have tried updating/uninstalling VMWare tools but this does not seem to fix anything. We also thought this might have been related to the video driver, so we booted the server with "Base Video" options in MSConfig but this still didn't fix the problems.

I am hoping that there are others in the same position as me, looking for an answer but having no forum to discuss it on, hence this post. Any advice greatly appreciated.

Lewis

Hi,

I tried to install Microsoft Office 2019 in the Windows server 2012 and it says that the operating system has to be upgraded to Windows 10. I have Office 365 running in the same server, but, this error only happens for Office 2019.

Just wanted to know if the Office 2019 just works on Windows 10 and not in any other platforms. Also is there any other alternative that could make this work?

Thanks,