Differences

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

--- virtualization:ras:ras_thin_client_server [2017/01/25 11:06]
gcooper
+++ — (current)
@@ Line 1: / Line 1: @@
-====== 2X ThinClient Server ======
-See also **[[virtualization:ras:ras_application_server|Parallels RAS – Remote Application Server]]**
-:!: This functionality is no longer available separately.  It is included in the installation of 2X RAS.
-:!: This functionality was **dropped after 2X RAS v12**.
-===== Enable PXE Boot Server =====
-It is necessary to enable the PXE Boot Server.
-  - In the 2X Remote Application Server Console, click on **Farm** icon
-  - Under Farm click on **Gateways**
-    * Gateway must be in **Normal** mode to support thin clients
-  - Right click on the current gateway and choose **Properties**
-  - Click the **Network** tab
-  - Under **Thin Client Network Boot Support**, tick the box to enable that option
-  - Enable **DHCP Proxy** (Port 67)
-  - Click **OK** and then the **Apply** button
-:!: Any time you make a change click the Apply button if it is lit up!  You may NOT be prompted to do so when necessary!
-===== Firewall =====
-You need to open a few ports to support PXE boot thin clients (single server configuration):
-|UDP |67, 69, 3389, 4011, 20000, 20009|
-===== Add a Thin Client to PXE Boot =====
-This will boot a Thin Client/PC to the 2X OS
-  - Configure the PC/Thin Client to PXE boot (Boot to LAN) in BIOS
-  - Boot to PXE. The device may auto add.  If not continue with #3
-  - Note the MAC Address displayed during boot IE 74-D4-35-E5-67-9A
-  - In the 2X Remote Application Server Console Click on "Client Manager" icon
-  - Click the + (add) button
-  - Enter the MAC Address, click Next
-  - Enter descriptive Hostname or leave at default TC-(MAC Address)
-  - If you have a group configured for this device select that group
-  - If Boot Method is other than "Network Boot" change to "Network Boot", click Next
-  - Use defaults on other screens if the group is configured or untick Use Group settings and configure
-  - Click Finish and then the Apply button
-===== Define Video for proper operation =====
-If the default auto detection does not work for video you can force drivers and settings.  Note the video chipset manufacturer of the device.
-  - In the Client Manager section right click the device to be configure and select Properties
-  - Click the Hardware Tab, Untick Use Group Settings, Advanced Button, Force Display Settings Button
-  - Tick "Force Display Settings" box, Select the chipset manufacturer from the Video Card Driver drop box
-  - Set the resolution to the native resolution of the monitor
-  - Click OK, OK, OK
-  - Click the Apply button
-:!: If video is not acceptable try other possible options of manufacturer if available.  If all else fails try ''VESA'' as the driver.
-===== Manage/Shadow/Power Control of Thin Clients =====
-  - Configure the Thin Client so that WOL (Wake On LAN) is enabled
-  - In the 2X Remote Application Server Console click Client Manager
-  - Right click Thin Client to be managed
-  - Scroll to the right and click the "Shadowing" tab.
-  - Tick box for "Enable VNC Service"
-  - Click OK, click Apply
-:!: Highlight terminal to shadow and then click the Shadow button.
-===== Configure Terminal to boot directly to RDP login =====
-  - In 2X Remote application Server Console click Client Manager, Thin Client Groups Tab
-  - Click the + button to add a Group
-  - Give the Group and descriptive name
-  - You must modify the MAC filter to be different than the default ??-??-??-??-??-??
-  - Set other options for the group
-  - On the Remote Desktop tab, enable RDP and configure the server address
-  - On the Kiosk tab Enable Kiosk Mode and choose Kiosk Type RDP
-:!: The Terminal will boot to the 2X login and pass credentials to the RDP client logging into RDS.

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools