User Tools

Site Tools


virtualization:2x:2x_ras

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
virtualization:2x:2x_ras [2016/10/06 14:04]
gcooper
— (current)
Line 1: Line 1:
-====== 2X RAS – Remote Application Server ====== 
- 
-See also **[[virtualization:2x:2x_thin_client_server|2X ThinClient Server]]** 
- 
-See also **[[virtualization:2x:2x_web_portal|2X Remote Application Server Web Portal]]** 
- 
-**Client Downloads**: http://www.2x.com/rdp-client/downloadlinks/ 
- 
-**Server Downloads**: http://2x.com/downloads/ras/2xappserver.msi 
- 
-**2XOS Downoads**: http://www.2x.com/os/downloadlinks 
- 
-**2X RAS Upgrade Procedure**: http://kb.parallels.com/en/123005 
- 
-===== 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) 
-        * Under User Interfaces and Infrastructure 
-  - Configure specified License Server and License Type in Group Policy 
-     * Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing 
-  - 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 
- 
-  - 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/ 
- 
-:!: These are bare minimum ports that must be opened for a single-server installation supporting PXE clients. 
- 
-|TCP |80, 443, 3389                    | 
-|UDP |67, 69, 3389, 4011, 20000, 20009 | 
- 
-===== 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 Client Gateway and HTML5 Gateway ===== 
- 
-{{ :virtualization:2x:2x_connection_properties.png?350|2X Connection Properties}} 
- 
-http://www.2x.com/support/ras-documentation/manual/add-2x-secure-client-gateway/ 
- 
-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 
- 
-===== 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 
- 
-===== 2XOS PXE Boot ===== 
- 
-See also **[[virtualization:2x:2x_thin_client_server|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 
- 
-===== 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. 
- 
-Choose 2X Universal Printing Technology in Connection Properties of 2X Client or Policy on 2X RAS if printing is locked down.  If selecting Specific Only for Redirect printers: Add printer name of local printer on client. 
- 
-===== 2X File Association for Published Applications ===== 
- 
-If you want to open a file on a local computer with a published application via file association it must be configured first. 
- 
-http://www.2x.com/support/ras-documentation/manual/manage-publish-app/ 
- 
-Then set the file association of the appropriate extension to 2X Kickoff on the PC. 
- 
-Also, all drives that the files to be opened reside on need to be included in drive redirection in the RDS session. 
- 
- 
- 
-{{ :virtualization:2x:2x_mail_settings.png?525|2X Mail Settings}} 
- 
-===== E-Mail Notifications ===== 
- 
-**2X RAS Console -> Administration -> Mailbox Setup** 
  
virtualization/2x/2x_ras.1475784246.txt.gz · Last modified: 2016/10/06 14:04 by gcooper