See also 2X ThinClient Server

See also 2X Remote Application Server Web Portal

Client Downloads: http://www.2x.com/rdp-client/downloadlinks/

Server Downloads: http://www.2x.com/ras/downloadlinks/

2XOS Downoads: http://www.2x.com/os/downloadlinks

1. Web Portal
2. Desktop by Thinclient
   • URL Redirect
   • Media Player Redirect
   • MIME Type
3. Universal Printing
   • Multi Function Printers
   • Zebra Printer
4. Universal Scanning
5. Thin Clients
   • Old Thin Clients (PXE boot)
   • New Thin Clients (Local OS)
   • Old PC retask
6. VLAN JW (VPLS?)
7. Traffic Shaping, IP Priority (VoIP)
8. Configuration Locking Software
   • 2X Thinshell
   • 3rd Party solution?
9. How is User Profile Data dealt with in 2X
10. Does 2X have Remote Management

http://www.2x.com

http://www.2x.com/support/ras-documentation/

Quick Configuration Guide: http://www.2x.com/support/ras/setup/

1. If the 2X RAS will also be a terminal server, install these first:
   • Role-based Installation
     • Remote Desktop Services (role)
       • Session Host service
       • Remote Desktop Licensing service
         • Perhaps on domain controller
     • Desktop Experience (feature)
       • Under User Interfaces and Infrastructure
2. Configure specified License Server and License Type in Group Policy
   • Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
3. Configure Domain Users to login to DC via RDS in Group Policy
   • Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Allow log on through Remote Desktop Services

1. Install 2X RAS
2. Add a terminal server
   • Use IP addresses unless the hostname is fully resolveable
3. Publish a Desktop
4. Publish an application

http://www.2x.com/firewall-requirements-2x-remote-application-server/

http://www.2x.com/configuring-the-windows-server-2008-r2-firewall-to-open-ports-for-2x-solutions/

These are bare minimum ports that must be opened for a single-server installation supporting PXE clients.

You need a minimal but functional RDS server before it will work with 2X as a terminal server.

Add Domain Users to the allowed RDS users list:

Right-click Computer → Properties → Remote Desktop → Select Users

http://www.2x.com/support/ras/html5-gateway/

2X RAS Console → Farm → Gateways → Properties → SSL/TLS

• Enable
• Create a Self-Signed Certificate

2X RAS Console → Farm → Gateways → Properties → HTML 5

• Enable
• https://servername/2XHTML5Gateway

http://2x.helpserve.com/knowledgebase/article/View/41/0/which-connection-mode-should-i-use-with-2x-applicationserver-xg

2X Client connects to a 2X Gateway over port 80 or port 443 (SSL) then negotiates a direct RDP connection to the Terminal Server.

• Best performance for multimedia

The 2X Client connects to a 2X Gateway over port 80 or port 443 (SSL) which negotiates an RDP connection to the Terminal Server. The RDP traffic is tunneled over the HTTP/HTTPS connection.

• Easier to get through firewalls
• Potentially more secure
• Not as good for multimedia

See also 2X ThinClient Server

2X RAS Console → Client Manager → Thin Client Groups → Properties

• Boot Method → Network Boot
• Regional → Set Time Zone and Language
• Input Devices → Keyboard and Layout
• Shadowing → Enable VNC Service
• Shadowing → Enable Interact with Desktop
• RDP Defaults → 2X Connection Mode → Direct
• RDP Defaults → Bandwidth → High Speed Broadband

You must have RDP 8.0 or higher protocol on the Windows Workstation to get the benefits of remote FX.

Windows 7 and Higher supports RDP 8 Protocols.

Enable and disable the following options with gpedit.msc on all terminal servers in your farm:

Local Computer Policy → Computer Configurations → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment → RemoteFX for windows Server 2008 R2

• Enable all three settings

Local Computer Policy → Computer Configurations → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment

Under Remote Session Environment, enable and disable the following adjusting as necessary:

2X Universal printing is automatically installed when the Agents for Terminal Server, VDI Guest and Remote PC are installed. With 2X Universal Printing specific printer drivers are not necessary on the server.

You must login to the session from the terminal with the local printer installed for the local printer to show up in the session. If you take over a disconnected session the local printers will not show

2X RAS Console → Administration → Mailbox Setup