We have OpenGL application working on a server computer.  If later we connect via RDP to this server, OpenGL application continues to function without any problems. Obviously RDP just transfers image from server to remote computer.

If we start the same OpenGL application on the same server from RDP session, it runs OpenGL not on server but on the remote computer. Application crashes on operations that require OpenGL 2.0 or higher.

Is there any way to force RDP to run OpenGL code always on server no matter how it was started, directly on server or from remote computer?

I've set up a HA Connection Broker cluster, and in order to get the web gateway working again, I need to set up a new RAP policy that specifies the RD Broker RR Address, but every time I try, when I click 'Add' in 'User Groups' (And anywhere else in the MMC, it seems), the MMC crashes with the following output:

Problem signature:
  Problem Event Name:    BEX64
  Application Name:    mmc.exe
  Application Version:    6.3.9600.17415
  Application Timestamp:    54504e26
  Fault Module Name:    clr.dll
  Fault Module Version:    4.6.1055.0
  Fault Module Timestamp:    563c12de
  Exception Offset:    00000000002fdbd8
  Exception Code:    c0000409
  Exception Data:    0000000000000002
  OS Version:    6.3.9600.2.0.0.400.8
  Locale ID:    1033
  Additional Information 1:    96f9
  Additional Information 2:    96f9c5010a52aa0dfa6dd4f9281ffe93
  Additional Information 3:    7b9b
  Additional Information 4:    7b9b3ea08d2dac897bb696ccf51055a9

As far as I can tell from searching, it seems to be .NET that's crashing, but I haven't found any solutions.All three servers (Web Gateway and both Connection Brokers) are fully patched.

has anyone else sen this and/or have any ideas how to either fix it or maybe some kind of workaround?

Where is the Remote Desktop Session Host Configuration tool in Server 2012 ?

This is an MMC snap-in found on earlier servers, even if RDS is not installed.  In Server 2012, even if the Remote Desktop Session Host role is installed, this tool is still not available.

I'm looking for the Server 2012 tool to adjust security settings like TLS authentication, High encryption level, choice of TLS certificate, NLA, etc.

Thanks!

Hi.

We are rolling out RDS 2019 in our environment. We've got a lot of complaints about the DPI settings not being able to set in the session anymore like in 2008R2, but it has to be done on the local client, which is really cumbersome. However, when done so, we still have some applications with issues.

Now, for most of them I can fix it by setting the compatibility settings:



On a Server 2019 test machine, when set to Application, the application actually shows up fine. On RDS2019 though, it doesn't. I've been working on this for a while, until I installed a machine from scratch, do one step of our installation script at a time, and see where it started failing. It turn out as soon as we enable the RDS role, the DPI settings don't have any effect anymore, and the app is all blurry.

When I remove the RDS role, they start working again. Would anyone know how to fix this?

Windows Server 2019, Russian version, clean installation, licensed, activated, in the workgroup.

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.

Hi

I am trying to run a PowerShell command to add an application from a network share onto my Remote Desktop Server 2016. When I run the command, it shows the following:

New-RDRemoteApp : A Remote Desktop Services deployment does not exist on SR1RDS002.ad.collinsco.com. This operation
can be performed after creating a deployment. For information about creating a deployment, run "Get-Help
New-RDVirtualDesktopDeployment" or "Get-Help New-RDSessionDeployment".
At line:1 char:1
+ New-RDRemoteApp -CollectionName RD_APPS_1 -DisplayName BankLink -File ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDRemoteApp

The Remote Desktop Server is running and I have staff currently using the applications on it therefore do not understand why this is happening.

This is very frustrating as I have two applications that run from a Network share that I need to have published.

Can anyone please help me with this issue? Thanks

Hello readers,

We have a server 2012R2 environment with 2 RDS servers and a Connection Broker.

When I try to export the Startdesktop (Export-StartLayout -Path "C:\Beheer\start_new.xml") -Path ", i get instead of a xml file an output in non readable format like:

LMXL@  H  ÷^*xœÍ—oOAÆç£ßòç@H¬    \cªÅh«}ÁÃš"RÀj5ýîýÍs'FÛØÚX —Û›™ÝyfgwvnÛFÖ³+Û©}¶Ä¦–³oúÎìÜ.῱
+ñæìÈv­¥þ†íØ6zçh^#3Ç´ËŽlNoJ›jA_ba¢Þœ1#4sÖ€3YÌxg8u‹­j¼¦V€jÒ,”Äy5¸5Qmž2½ªô*ÐmÚ‚ý°.㻕•Ûع²{•ÇúؾÈ÷ð6C=³¯è8îÄŠšç&ûºf ×W(±æ›1—qÙæ¼j    gÈ\MÛc Ub÷ªLÏ©¼-yÕ„n`¯È¨¼Z¯{•Îí{òfŒ½´À;‡šg‘[ŽwûðOÝï½<²{cÚ9^Ü0b„|š­¿Çf¨=7ÒYÒˆ½=ÕNHV¸6'ŠÑ€þ5Üt%fìÅ9œÉ/¸®¡Ð¾G^†ióÉ™û»ø;ľCñáßµ÷´;dLžØ~âÍ ÙêVõ1ÆŽ}´¶Ç·cïÖ£cŠh÷ÖßýPB½g5×å>7Mƒuô•<âYÊ;2t¤›+D»Í<žË Ù]ÒÆÊïžÉC$=—–Ð- õ[­´åwÏ
}ì8zßW®Ï‹jÝÐ-æé>â=Œ8„SÆBþÍ«ç»Ë-]ž6õBg¢û  Æ.½>6&šc@?ÎÆϾu@3²ïò¯¯¬™®ÈêvaCµÄ¥½ÕœÉâ6 »CÚĪßùuµûHZPvßêé-ïÕJ ß+˜²v…˫쓪öÃr<|>2sÅb¾†‘yí“w¦
*§úe¨jåBÞ¤5ptiM;Î*¬®bÛÔ¨2Ÿc-ÏBÜ<yÉ«êÏÿ9ÏÅ5Q\ÏU`F¯Š{ªÍÓ\qªsëÕÚqVÇ;ÿ8»åï³éºž³6c–¶bšF¿ªÓåõu¨ëv(KZ×éóÜwGË1ÚË:g/÷ÐsD‹·
æ8û7(gžOJòµ­ÿ…’(÷¯˜ý9„ðªø­±‡Ep–@ãWSÞT²ÿ¥@hZò+B¡(ÞE÷·®*Ò¯íáÓ;nsñ§›öžþ1ï˜ÙOüáe

When I ran the cmd, there was no error message.

A few years ago, the StartLayout was exported succesfully.

What I have tried so far:

- tried the export on different servers (RDS and non-RDS)

- tried the export with a different (domain) admin account

- tried the export with optie "-as bin"

I found only one other reference to this issue online, but unfortunately no solution: https://social.technet.microsoft.com/Forums/en-US/71e76f2a-2b40-466a-8046-fa191babfb9a/how-to-hide-additions-applications-from-windows-81-using-group-policy-server-win2k8-r2?forum=w8itprogeneral

Anyone an idea how to fix this?

Hi All,

I am trying to check if we can change the default expiration days (60 days) for the RDS licenses issued. Right now we use "Windows Server 2016 -RDS Per User CAL" and we could see some old users who are not exclusively using the RDS application. I want to check if there is way to reduce the expiration days to 7 or 10 days so that we can avoid the license shortage. I also want to check if there is way to get monitoring if the license usage reached 90% or more.

Thanks in advance! 

I'm having problems with one Username, I get this error in Event Viewer:

Windows could not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you log off. Windows could not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrators group must be the owner of the folder.

1. The profile path exists: \\ts-srv\Profiles$\Username

2. The folder Username.V2 exists too.

3. The user has Full access Username folder.

What I did once is gave full rigths to Administrators for the Username.V2 folder, I wanted to see something and I did not have access so I've change the permission.

How to fix this issue ?

Thank you.

Hello Team,

I have the below issue:

Here is my RDS environment:

I have only one server 2012 R2 standard with the below roles installed 

• RD connection broker,
• RDSH,
• RD Licensing and
• RD web access

I have published few remote apps and I was able to access them using RD web feed till yesterday. 

Example :https://contoso.com/RDWeb/Feed/webfeed.aspx

I do have installed the SSL certificate on my server and provided the same to RD web. 

But today while I use the same url to access the remote apps I get the below error message 

"The remote computer cannot be authenticated due to problems with its security certificate. security certificate problems might indicate an attempt to fool you or intercept any data you send to the remote computer"

Error code - 0x80072f8f,0x20

Now I can only access the remote apps through RD web access ( https://FQDN/RDWeb)

Please help me in fixing this issue. 

Any help would be much appreciated.

Thanks

SM

When try to connect from public network to RDS 2016 environment web page is loaded, but when try to connect on RDP clinet, it will ask for credentials and after that it will connect to remote machine. Error shows as " your computer can't connect to the remote computer because remote desktop gateway server is temporarily unavailable"

When checking on error log found that even id 312 on gateway server

The user "abc@xyz.com", on client computer "xx.xx.xx.xx:2985", has initiated an outbound connection. This connection may not be authenticated yet.

I tried the registry key fix recommended for 2012 server (HKLM\SYSTEM\CurrentControlSet\Control\Lsa) and (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core) but no joy. It did not work for 2016 server. Please help.

I'm having an issue on a single RDS 2016 server at the moment where the start menu doesn't open.  

I've gone though lots of steps including sfc /scannow  (No errors)   DISM with all the options (No Errors)

I've cleared the Registry in firewall policy\restricted services\configurable\system.

I believe the issue is that I don't have any applications registered in the get-appxpackage at all, it just comes back blanks where as on working machines I get a list of about 15.

I've tried to install the packages by hand using variations of 

Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml -Verbose 

This returns the following;

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.
An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
NOTE: For additional information, look for [ActivityId] 5597e571-c93a-001c-e6eb-97553ac9d401 in the Event Log or use the command line Get-AppxLog -ActivityID
5597e571-c93a-001c-e6eb-97553ac9d401
At line:1 char:1
+ Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemAp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Windows\Syst...ppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

If I then use Get-AppxLog -ActivityID5597e571-c93a-001c-e6eb-97553ac9d401

Time                      ID           Message
----                      --           -------
20/02/2019 17:22:29       301          The calling process is powershell.exe
20/02/2019 17:22:29       603          Started deployment Register operation on a package with main parameter: AppxManifest.xml and Options: 0. See
                                       http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       10002        Creating Resiliency File
                                       C:\ProgramData\Microsoft\Windows\AppRepository\75f29027-c919-4974-89c9-f53bb4413b5f_S-1-5-21-1787921346-3847137862-2124306101-500_1.rslc for
                                       Register Operation on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy.
20/02/2019 17:22:29       607          Deployment Register operation on package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy has been de-queued and is running
                                       for user FISRDS1\Administrator.
20/02/2019 17:22:29       613          Adding uri to the list of Uris: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml.
20/02/2019 17:22:29       447          GetFullyQualifiedReference from the String Resource Map for package full name:
                                       Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy and reference string: Microsoft Corporation failed.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10000        About to service package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to disabled returned
                                       with 0x80070490.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       827          Capability parsing started for the package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy
20/02/2019 17:22:29       5252         An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       306          error 0x800705AA: While processing the request, the system failed to register the windows.stateExtension extension due to the following error:
                                       Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       316          error 0x800705AA: Cannot register the request because the following error was encountered during the registration of the windows.stateExtension
                                       extension: Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       5252         An internal error occurred with error 0x80070002. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       331          error 0x80070002: While reverting the request, the system failed to de-register the windows.stateExtension extension due to the following
                                       error: The system cannot find the file specified.
                                       .
20/02/2019 17:22:29       300          error 0x80073CF6: Cannot register the Microsoft.Windows.Cortana_cw5n1h2txyewy package due to the following error: Package could not be
                                       registered.
                                       .
20/02/2019 17:22:29       605          The last successful state reached was ResolvedDeferredRegistrations. Failure occurred before reaching the next state RegistrationChanged. hr:
                                       0x80073CF6
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10001        Finished servicing package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to enabled returned
                                       with 0x0.
20/02/2019 17:22:29       401          Deployment Register operation with target volume C: on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy from:
                                       (AppxManifest.xml)  failed with error 0x80073CF6. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       404          AppX Deployment operation failed for package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy with error 0x80073CF6. The
                                       specific error text for this failure is: An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160
                                       for help diagnosing app deployment issues.

I can't seem to get the system to re-register those applications!

Open to any suggestions?  (Please no, have you restarted the server!)

This happens on all users including local admin and new accounts.  Happens in Safe and Clean Boot.

Thanks.

Hello guys,

I'm building a new RDS farm on Windows Server 2016. 2 servers with connection broker, gateway, web server and licensing role (ha mode) installed and 4 session hosts - all on WS2016Standard.

I wanted to customize the Start menu on the session hosts for each user - For Windows Server 2016 there isn't much guidance to be found, so i assumed the articles from Jeanie Decker on https://technet.microsoft.com/en-us/itpro/windows/manage/customize-and-export-start-layout about customizing, exporting en re-deploying the Start menu on the session hosts with GPO's for Windows 10. ADMX files are imported in AD GPO store.

I created a Start menu with a test user, exported with Export-StartLayout, put it in a share and tested if the test user had access to the share and file: all tests ok. Created the GPO, tested the GPO with gpresult /r, and the GPO is applied: all ok.

The customized Start menu is not applied however. I've noticed that the User Config GPO states:

There are no errors in Event Log - Administrative Events, Application and/or System logs regarding applying or failing this. A gpresult /v gives me this output:

Anyone has any ideas why this is not applying? Or any other way to troubleshoot this issue further?

I have a new RDS deployment.

We have made the Broker HA.

Attempting to add the second Connection Broker, the role was installed but it reported that it failed, not much else of any use just failure.

As it turns out the Broker role was installed, but not as part of the HA configuration, and it now shows as part of RDS as a connection broker.

Attempting to remove the roles from the RDS deployment (Server Manager) fails responding that it is not part of the deployment.

Question is now how can I force the remove of the server from the deployment scenario sand start again?

I found this, https://support.microsoft.com/en-us/help/2925854/cannot-remove-an-rd-host-from-an-rds-deploymentwhich is of no help as MS want you to call them and I can't exactly do that..

so to sum up: I have an RDS deployment with two brokers, one is in HA mode talking to SQL, adding the second failed but still installed the role but not in HA mode. RDS will not allow me to remove the failed (2nd) server.

Can you offer up some suggestions regarding the following System log events? We are seeing these errors frequently on the Windows Server 2012 R2 server which is hosting the Remote Desktop license server.

1. Are these warnings and errors concerning and require action to correct? If so what steps?

2. What end user experience symptoms (other than the posted messages to System log) would we expect to see?

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          4/29/2019 11:12:28 AM
Event ID:      4105
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
The Remote Desktop license server cannot update the license attributes for user "useraccountname" in the Active Directory Domain "mydomain.com". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "mydomain.com".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: 0x80070005

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          4/30/2019 5:51:17 AM
Event ID:      44
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
The following general database error has occurred: "ESE error -1003 JET_errInvalidParameter, Invalid API parameter."

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          5/1/2019 11:46:41 AM
Event ID:      4106
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
CAL reporting: Windows Server 2012 : RDS Per User CAL - Installed: 850, Issued: 881

In addition, I can confirm that, per instructions in event 4105, the license server is not a domain controller and the computer account is a member of the built-in "Terminal Server License Servers" group.

A similar question TechNetForumTopic, TechNetForumQuestion, SysAdminTipBlog, and MsITprosBlog refers to a solution involving old accounts for long-term employees who are appearing in event 4105. I have validated that many of them are old enough that they likely existed back when this domain was at the 2003 functional level (it is now at the 2012 level). However, these users are not reporting any symptoms, so the event 4105 seems to not cause any downside other than logging the event. (Which goes back to my original questions, what symptom effect should we be seeing?)

Thanks in advance for your assistance.