Administrator Guide

• Dependence 2—VOR is dynamic. So the enablement/disablement of VOR dynamically changes during the change in
the video resolution (enlarge/shrink).
• Dependence 3—H.264 enablement is decided at the beginning of connection, depending on the maximum resolution
available for the session.
If H.264-AVC444 is enabled, VOR is not used in Microsoft broker 2016, and Windows 10/2016 sessions without the RemoteFX GPU. If you
disable H.264-AVC444, VOR is used.
In RDP session (RDP 8.1 and later), VOR, H.264, and H.264-AVC444 are enabled by default. To disable these parameters, use the INI
parameter—
SessionConfig-RDP EnalbeGFX=yes EnableVOR=no EnableRDPh264=no.
When you connect to an RDP session in Windows 8.1 or Windows 10 with RemoteFX GPU adapter, H.264-AVC444 is used irrespective of
the H.264-AVC444 group policy configurations. If you disable the H.264 feature by using the INI parameter, the VOR codec is used in RDP
sessions. However, graphic-related issues are observed in RDP sessions. The VOR codec is not used when you disable H.264 using the INI
parameter.
TS Gateway in Microsoft Broker
User scenario:
1. Log in to Microsoft Broker with TS Gateway configured.
2. Launch a published collection.
TS Gateway connection is established.
The following table lists the TS Gateway versions supported by Windows Server.
Table 21. Supported TS Gateway versions
Server operating system TS Gateway II TS Gateway III WebSocket
Windows 2008 R2 Support Not support Not Support
Windows 2012 R2 Support Support Not Support
Windows 2016 Support Support Support
• In TS Gateway II or III connection, the setup uses a two half-duplex communication between Terminal Server (TS) Gateway server and
thin client.
• In the WebSocket connection, the session connection setup uses a duplex communication between TS Gateway and thin client
• TS Gateway II and TS Gateway III are downward compatible with Windows Server 2016, that means, if the WebSocket connection
fails or the TS Gateway server or thin client version does not support WebSocket, then TS Gateway II or TS Gateway III is used.
NOTE:
• WebSocket connection log is hidden and not displayed in the Event Log tab. If you want to view the WebSocket
connection log, go to Troubleshooting > Capture and enable Persistent for the export event log.
• From the ThinOS v8.6 release onwards, the WebSocket feature is disabled by default. To enable WebSocket, deploy
the following INI parameter:
Sessionconfig=RDP TSGWWebSock=yes.
Connect to RDP session using UDP with TS Gateway
To connect to a Remote Desktop Session using User Datagram Protocol (UDP) with TS Gateway, do the following:
1. Deploy the following INI parameter to the thin client:
SessionConfig=RDP TSGWUDP=yes.
2. Enable Terminal Services Gateway (TSGW) for the applications and desktops from the Microsoft RDS broker server.
3. On the ThinOS client, start a Remote Desktop Session using the RDS connection broker.
4. Connect to the published desktop.
On the ThinOS desktop, an event log is displayed in the System Information window.
Configuring the connection brokers
93