Administrator Guide
2. Connection with TS gateway congured in unsupported OS (e.g. Windows Server 2008 R2), it uses TS gateway II and the logs
are displayed as shown in the following screenshot:
3. When remote connection with TS gateway III closed: There are no additional logs displayed in the Event Log tab.
Supporting RDP H.264 AVC444
RDP uses the ITU-T H.264 graphics compression (codec), also known as MPEG-4 AVC (Advanced Video Coding). In RDP 10,
AVC/H.264 supports the full-screen AVC 444 mode. By default, this mode is enabled on thin clients for Windows 10 and Windows
2016 remote sessions.
As a pre-requisite, navigate to Group Policy Editor (gpedit.msc) in Computer Conguration → Administrative Templates →
Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment, and
enable the following policies:
• Prioritize H.264/AVC 444 Graphics mode for Remote Desktop connections
• Congure H.264/AVC hardware encoding for Remote Desktop connections
The original H.264 codec only transfers YUV420 frames. However, some chroma data from sampled YUV444 frames is discarded.
The feature that allows the lost chroma data of a frame is transferred using the same method as applied to the sampled YUV420
data. This improves the image qualities with many articial sharp edges, and mounts of regular color boundaries, such as texts.
Therefore, the image quality can be compressed using the same H.264 technology by using the same set of software or hardware,
instead of using a dierent codec. This results in more scalability on system work load and network bandwidth occupation.
NOTE: In ThinOS v8.5, the RDP 8.1 session uses the original H.264 codec.
For more information about Remote Desktop Protocol (RDP)10 AVC/H.264 improvements in Windows 10 and Windows Server 2016,
see cloudblogs.microsoft.com/enterprisemobility/2016/01/11/remote-desktop-protocol-rdp-10-avch-264-improvements-in-
windows-10-and-windows-server-2016-technical-preview.
Using Microsoft WebSocket
Microsoft WebSocket provides a mechanism for fast, secure two-way communication between a client and a server over the web
using HTTP(S).
The WebSocket protocol enables two-way communication between the browser-based applications and the servers that does not
rely on the multiple HTTP connections. The protocol consists of a handshake followed by basic message framing, layered over
110