Hello,
In Windows Azure Í installed Windows 2012 R2 RDS server (vm type small) and configured remotefx via GPO. Everything looks normal, both in eventviewer (no errors) on the RDS server and on my Win7 SP1 client in the taskbar the connection info icon shows that the connection is ok.
However, in the eventviewer after a number of succesfull events id 258 'The connection is not using advanced RemoteFX RemoteApp graphics' is logged. As said, no error is logged, see the events below. Is remotefx not supported in Azure? If not, is this on the roadmap? If it is supported, what am I doing wrong?
Thanks for your answer,
Ronald Hovens
Level Date and Time Source Event ID Task Category
Information 1/6/2014 9:19:26 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel PNPDR has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:26 AM 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: 0.
Information 1/6/2014 9:19:26 AM 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: 0.
Information 1/6/2014 9:19:26 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:26 AM 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: 0.
Information 1/6/2014 9:19:26 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:23 AM 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: 0.
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel AUDIO_PLAYBACK_DVC has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel rdpdr has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 258 RemoteFX module The connection is not using advanced RemoteFX RemoteApp graphics
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 168 RemoteFX module The resolution requested by the client: Monitor 0: (1280, 1024), origin: (0, 0).
Information 1/6/2014 9:19:23 AM 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: 0.
Information 1/6/2014 9:19:23 AM 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:
0.
Information 1/6/2014 9:19:23 AM 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:
0.
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 162 RemoteFX module The client supports version 0x80004 of the RDP graphics protocol, client mode: 0, H264 enabled: 0
Information 1/6/2014 9:19:23 AM 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: 0.
Information 1/6/2014 9:19:23 AM 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: 0.
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 135 RemoteFX module The multi-transport connection finished for tunnel: 1, its transport type set to TCP: Reason Code: 3 (No UDP Packets Received).
Information 1/6/2014 9:19:23 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 135 RemoteFX module The multi-transport connection finished for tunnel: 3, its transport type set to TCP: Reason Code: 3 (No UDP Packets Received).
Information 1/6/2014 9:19:22 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 169 RemoteFX module The client operating system type is (1, 3).
Information 1/6/2014 9:19:22 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 165 RemoteFX module RemoteFX Encoding for RemoteFX Clients designed for Windows Server 2008 R2 SP1 is enabled and a compatible session was created.
Information 1/6/2014 9:19:22 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel rdpinpt has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:22 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 33 RemoteFX module Remote Desktop Protocol will use the RemoteFX guest mode module to connect to the client computer.
Information 1/6/2014 9:19:22 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel rdpgrfx has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:21 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 66 RemoteFX module The connection RDP-Tcp#1 was assigned to session 2
Information 1/6/2014 9:19:20 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 130 RemoteFX module The server has initiated a multi-transport request to the client, for tunnel: 3.
Information 1/6/2014 9:19:20 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 130 RemoteFX module The server has initiated a multi-transport request to the client, for tunnel: 1.
Information 1/6/2014 9:19:20 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 100 RemoteFX module The server has confirmed that the client's multi-transport capability.
Information 1/6/2014 9:19:20 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 98 RemoteFX module A TCP connection has been successfully established.
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel rdpcmd has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 132 RemoteFX module A channel rdplic has been connected between the server and the client using transport tunnel: 0.
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 133 RemoteFX module The following network characteristics have been detected for tunnel 8; Link latency : 11 milliseconds and Bandwidth: 21880 kbps.
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 141 RemoteFX module PerfCounter session started with instance ID 1
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 65 RemoteFX module Connection RDP-Tcp#1 created
Information 1/6/2014 9:19:19 AM Microsoft-Windows-RemoteDesktopServices-RdpCoreTS 131 RemoteFX module The server accepted a new TCP connection from client [fe80::b01f:6518:6711:6ce0%41]:49222.