Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » virtualization » 2x » 2x_application_server
Trace:
virtualization:2x:2x_application_server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
virtualization:2x:2x_application_server [2015/01/21 10:32]
gcooper 		— (current)
Line 1: Line 1:
-====== 2X RAS – Remote Application Server ====== 
  
-See also **[[virtualization:2x:2x_thin_client_server|2X ThinClient Server]]** 
- 
-http://www.2x.com/solutions/2XSolutionsguide.pdf 
- 
-===== Items that need Evaluation ===== 
- 
-  - Web Portal 
-  - Desktop by Thinclient 
-    * URL Redirect 
-    * Media Player Redirect 
-    * MIME Type 
-  - Universal Printing 
-    * Multi Function Printers 
-    * Zebra Printer 
-  - Universal Scanning 
-  - Thin Clients 
-    * Old Thin Clients (PXE boot) 
-    * New Thin Clients (Local OS) 
-    * Old PC retask 
-  - VLAN JW (VPLS?) 
-  - Traffic Shaping, IP Priority (VoIP) 
-  - Configuration Locking Software 
-    * 2X Thinshell 
-    * 3rd Party solution? 
-  - How is User Profile Data dealt with in 2X 
-  - Does 2X have Remote Management 
- 
-http://www.2x.com 
- 
-http://www.2x.com/support/ras-documentation/ 
- 
-===== Installation ===== 
- 
-**Quick Configuration Guide**: http://www.2x.com/support/ras/setup/ 
- 
-{{ :virtualization:2x:remote_desktop_role_services.png|Remote Desktop Role Services}} 
- 
-  - 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) 
-  - Install 2X RAS 
-  - Add a terminal server 
-    * Use IP addresses unless the hostname is fully resolveable 
-  - Publish a Desktop 
-  - Publish an application 
- 
-===== Firewall ===== 
- 
-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/ 
- 
-|TCP |80, 443, 3389  | 
-|UDP |3389           | 
- 
-===== Remote Desktop Services ===== 
- 
-:!: 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** 
- 
-===== Secure Gateway (SSL) and HTML5 Gateway ===== 
- 
-http://www.2x.com/support/ras/html5-gateway/ 
- 
-**2X Console -> Farm -> Gateways -> Properties -> SSL/TLS** 
- 
-  * Enable 
-  * Create a Self-Signed Certificate 
- 
-**2X Console -> Farm -> Gateways -> Properties -> HTML 5** 
- 
-  * Enable 
- 
-===== Connection Modes ===== 
- 
-http://2x.helpserve.com/knowledgebase/article/View/41/0/which-connection-mode-should-i-use-with-2x-applicationserver-xg 
- 
-==== Direct ==== 
- 
-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 
- 
-==== Gateway ==== 
- 
-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 
- 
-===== Cloud Portal ===== 
- 
-http://www.2x.com/support/ras/cloud-portal/ 
- 
-The Cloud Portal is a web interface to the 2X RAS system published resources. 
- 
-:!: Do not install the 2X RAS Portal on an Active Directory machine. 
- 
-You will need: 
- 
-  * A Windows server 
-  * Microsoft .NET Framework II/III 
-  * ASP.NET role 
-  * IIS6 or IIS7 
-  * Existing 2X Farm 
- 
-===== RemoteFX ===== 
- 
-==== Windows Server 2012 ==== 
- 
-:!: 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 
- 
-{{ :virtualization:2x:remotefx_for_windows_server_2008_r2.png |RemoteFX for windows Server 2008 R2 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: 
- 
-{{ :virtualization:2x:remote_session_environment.png |Remote Session Environment}} 
- 
-=====2X Universal Printing===== 
- 
-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 
virtualization/2x/2x_application_server.1421861553.txt.gz · Last modified: 2015/01/21 10:32 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki