Title Page Previous Next Contents | 5. Initial Configuration of 2X ThinClientServer

5. Initial Configuration of 2X ThinClientServer

To complete installation of 2X ThinClientServer

Ensure that JavaScript is enabled on the Web Browser you are using to access the Management Console. If JavaScript is not enabled, functionality of the Management Console will be severely impaired, and it will not be possible to complete the installation.
2XThinClientServer21.jpg
2XThinClientServer22.jpg
To enable JavaScript in Internet Explorer, go to Tools -> Internet Options -> Security tab. Select the Local Intranet icon and click on the “Custom Level...” button. Scroll down to Scripting -> Active Scripting and select the “Enable” option.
2XThinClientServer23.jpg
2XThinClientServer24.jpg
To enable JavaScript in Mozilla Firefox, go to Tools -> Options -> Content tab and select the “Enable JavaScript” option.
2XThinClientServer25.jpg
2XThinClientServer26.jpg
The 2X ThinClientServer is the place where all connection settings are stored. Upon boot-up, thin clients connect to the server and retrieve the settings that will determine how and to which terminal server they will connect.
Settings can be applied to an individual thin client (by MAC address), by username, by group (effectively capturing all the members of the group), or by organizational unit (OU). This gives the administrator maximum flexibility.
The 2X ThinClientServer can be managed from anywhere in the network because the Management Console is web-based.
To load up the 2X ThinClientServer configuration page, simply click on the Configuration link in the 2X ThinClientServer program group on the 2X ThinClientServer machine, or load up a browser from anywhere in the network and enter the IP address or hostname of the 2X ThinClientServer machine together with the port number (980), like the following example:
http://thinserver.2x.com:980
Please note that for a 2X ThinClientServer Management Console to function, it will be necessary to ensure that TCP connections on port 980 to the 2X ThinClientServer can be established.
2XThinClientServer27.jpg
2XThinClientServer28.jpg
2XThinClientServer29.jpg
Screenshot 16: Setting the Administrator credentials for the Management Console.
  1. Type in the username and password for the administrator user who will have the rights to configure 2X ThinClientServer. If you will be using Active Directory to retrieve lists of users, groups, and organisational units, select “Remote Users”. If you will be using local users for the list of users to manage, select “Local Users”. Click on “Create Account” when ready. Make sure that the Active Directory accounts are not expired as this might cause problems when the user tries to connect into his thin client.
Please note that it is NOT possible to change the userlist retrieval method after it has been selected.
For a 2X ThinClientServer to retrieve Active Directory information successfully, it will be necessary to ensure that TCP connections on port 389 to the Active Directory Server can be established.
2XThinClientServer27.jpg
2XThinClientServer30.jpg
2XThinClientServer31.jpg
Screenshot 17: Management Console main information screen
  1. After the account has been created you must log into the ThinClientServer where you will be presented with the Management Console main information screen.
The warning icons in the centre of the page indicate the configuration procedures that must be performed prior to concluding the installation procedure.
2XThinClientServer32.jpg
2XThinClientServer33.jpg
  1. Configuring the Directory Server
If you selected “Local Users” as your User Source in Step 2 above, the Management Console main screen will not prompt you to perform this procedure, and you will be able to successfully configure 2X ThinClientServer without configuring a Directory Server.
2XThinClientServer21.jpg
2XThinClientServer34.jpg
2XThinClientServer35.jpg
Screenshot 18: Configuring the Directory Server.
  1. You can add a Remote Desktop. This desktop can be of type RDP, NX or Citrix ICA. These settings will connect the ThinClientOS directly to that address and provide a full (not published) desktop to the user. If more than one full desktop will be available to the user, such desktop will be accompanied by the 2X desktop with a desktop switcher and dedicated task bar. To start adding Remote Desktops, choose the “Remote Desktops” node under “Desktop Components” in the sidebar.

    2XThinClientServer36.jpg
Screenshot 19: Add the settings for a direct connection to a Terminal Server.
Windows (RDP)*
Linux (NX)**
Citrix (ICA)***
Please note that for a Windows (RDP) Full Desktop Session to run successfully, it will be necessary to ensure that TCP connections on port 3389 to the Windows Terminal Server can be established.
2XThinClientServer27.jpg
2XThinClientServer37.jpg Please note that for a Linux (NX) Session to run successfully, it will be necessary to ensure that TCP connections on port 22 to the 2X TerminalServer can be established.
2XThinClientServer27.jpg
2XThinClientServer38.jpg
Please note that for a Citrix (ICA) Full Desktop Session to run successfully, it will be necessary to ensure that TCP connections on port 1494 to the Citrix Presentation Server can be established.
The “Citrix (ICA)” and “Citrix Published Applications” protocols are only available in the Enterprise Edition.
This connection will bypass the Citrix load balancing and provide direct connectivity to the server. If you wish to use Citrix load balancing configure a new published app.
2XThinClientServer27.jpg
2XThinClientServer39.jpg
You may specify which redirection facilities (sound, disk, and printing) will be available to this protocol.
Click on the “OK” button when ready.
You may select the desired colour depth from the drop down list.
You may select from a number of different resolutions from the drop down list
You may select the desired window manager for the NX protocol type. Select Gnome or KDE.
It will be necessary to repeat this procedure for each terminal server that you wish to support.
In a load-balancing installation of full desktops, you will only be required to set up one full desktop setting, directed at the load balancer. The load balancer will in turn handle session distribution to its member servers.
2XThinClientServer27.jpg
2XThinClientServer40.jpg
  1. Click on “Published Applications” node under “Desktop Connections.
2XThinClientServer41.jpg
Screenshot 20: Add the settings for a direct connection to a Terminal Server.
Windows (RDP)*
Citrix (ICA)**
* Please note that for a Windows (RDP) Published Applications Session to run successfully, it will be necessary to ensure that TCP connections on port 80 to the Windows Terminal Server can be established.
Please note that 2X ApplicationServer MUST be installed on the network to enable 2X (RDP) Published Applications.
2XThinClientServer27.jpg
2XThinClientServer42.jpg
** The “Citrix Published Applications” protocols are only available in the Enterprise Edition.
This connection will use the Citrix load balancing and provide a list of published desktops or applications as provisioned on the Citrix Servers. Please make sure that the NFuse/PNagent addons have been installed correctly on your Citrix Servers.
2XThinClientServer43.jpg
2XThinClientServer44.jpg
You may specify which redirection facilities (sound, disk, and printing) will be available to this protocol.
Click on the “OK” button when ready.
It will be necessary to repeat this procedure for each machine providing a list of applications that you wish to support.
2XThinClientServer27.jpg
2XThinClientServer45.jpg
  1. Next you can add the settings for a customized web browser on the ThinClientOS. This will be added to the desktop and such settings cannot be changed by the user. Make sure that the Thin Client has enough RAM to accommodate the multiple web pages that are displayed since more memory will be required and it depends on the web pages being rendered.
2XThinClientServer46.jpg
Screenshot 21: Add the settings for a local web browser on the ThinClient.
  1. To add a new user profile click on the “User Profiles” node and the main window will show a list of all the existing profiles.
2XThinClientServer47.jpg
Screenshot 22: List of configured profiles.
2XThinClientServer48.jpg
Screenshot 23: Adding a new profile.
2XThinClientServer49.jpg
Screenshot 24: New User Profile Added


If you selected “Local Users” as the user source in the step above, the user interface presented will be as follows:
2XThinClientServer27.jpg
2XThinClientServer50.jpg
2XThinClientServer51.jpg
Screenshot 25: Adding a User Profile with local users.
“Local Users” are stored in the central database of the ThinClientServer. They have got nothing to do with Windows/Linux local user accounts and credentials.
2XThinClientServer27.jpg
2XThinClientServer52.jpg
2XThinClientServer53.jpg
Screenshot 26: Adding a new Local User
2XThinClientServer54.jpg
Screenshot 27: Adding an existing user to a User Profile.
  1. To add a new version of the 2X ThinClientOS click on “ThinClient OS” node under the “System” node from the sidebar. Click on “Upload ThinClientOS Image” to upload a new 2X ThinClientOS.

    2XThinClientServer55.jpg
Screenshot 28: 2X ThinClientOS
2XThinClientServer56.jpg
Screenshot 29: Browse for a 2XThinClientOS file to upload.
Please note that it may take some time to install the file, especially if the 2X ThinClientServer machine is connected to this machine over a slow link. It may be necessary to configure a longer session timeout to allow for this eventuality.
2XThinClientServer27.jpg
2XThinClientServer57.jpg
  1. Return to the Management Console main information screen to ensure that all initial configuration items have been completed successfully. If any part of the configuration was not completed successfully then you will be able to see a notification in the main information screen.
2XThinClientServer58.jpg
Screenshot 30: The Management Console showing configuration status
  1. Once all the initial configuration elements have been completed, you can log out of the Management Console.