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.
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.
To
enable JavaScript in Mozilla Firefox, go to Tools -> Options -> Content
tab and select the “Enable JavaScript” option.
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:
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.
Screenshot 16: Setting the Administrator credentials for
the Management Console.
- 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.
Screenshot 17: Management Console main information
screen
- 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.
- 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.
- 3.1. Click
on the “Directory” node under “User Profiles” from the
sidebar. This will show existing Directories. If you would like to create a new
Directory click on “New
Directory”.
Screenshot 18: Configuring the Directory Server.
- 3.2. Domain
Name: Enter the domain name containing the users which will need to be
assigned thin client logon rights.
- 3.3. Host:
Enter the fully-qualified domain name (or alternatively the IP address) of an
Active Directory server.
- 3.4. Host
Mirror: Should the primary Active Directory server fail, a mirror can be
specified that contains the same user information and can be used in such
situations.
- 3.5. Username:
Enter a username residing within the selected domain which has
read access to the directory. It is
recommended to create a separate user for 2X ThinClientServer with a password
that never expires. No data will be written to the Active Directory. The
username should be in the format user@domain.com.
- 3.6. Base
DN: The Base DN connection string will automatically be displayed. If you
are familiar with LDAP and Active Directory, you can edit this string to filter
out results you don't need. A default Base DN is suggested when you type in your
domain name. This should let you browse all your Active Directory for
users.
- 3.7. Password:
Enter a password needed by the Active Directory to authenticate the user
specified above.
- 3.8. Click
“OK” when
ready.
- 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.

Screenshot
19: Add the settings for a direct connection to a Terminal Server.
- 4.1. Enter
a name for the desktop. If more than one item is available to the user, the name
will be used on the 2X desktop so that the user can identify which Terminal
Server he/she will be connecting to.
- 4.2. Select
the protocol type from the drop down
list:
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.
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.
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.
- 4.3. Select
the server addresses and “Port Number” The “Primary
Address” may be a hostname or an IP address. The default port number is
automatically set when the protocol type is selected – this value may be
customized if necessary. The “Secondary Address” can be added to
provide redundancy to a secondary NIC card or Terminal Server. This address will
be used if the user selects “Reconnect” after the session has been
disconnected.
- 4.4. Specify
the “Redirection
Settings”
You
may specify which redirection facilities (sound, disk, and printing) will be
available to this protocol.
Click on the “OK”
button when ready.
- 4.5. Specify
the “Display
Settings”
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.
- Click
on “Published Applications” node under “Desktop
Connections.
Screenshot 20:
Add the settings for a direct connection to a Terminal Server.
- 5.1. Enter
a name for the source of your published applications and/or desktops. This name
will not be seen in the ThinClientOS.
- 5.2. Select
the protocol
type
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.
** 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.
- 5.3. Select
the server address and “Port Number”. The “Primary
Address” may be a hostname or an IP address. The default port number is
automatically set when the protocol type is selected – this value may be
customized if necessary. The “Secondary Address” can be added to
provide redundancy to a secondary NIC card or Terminal Server.
- 5.4. If
you specify the ICA (Published Applications) protocol type you can choose to use
“HTTPS” if it is required by your Citrix Administrator.
- 5.5. Specify
the Redirection
Settings
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.
- 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.
Screenshot 21:
Add the settings for a local web browser on the ThinClient.
- 6.1. Enter
a name for the web browser. This name will be used on the 2X
desktop.
- 6.2. Set
the default homepage for the browser.
- 6.3. Select
if you want to add Flash support and which version. Each plug-in will require
more memory and local storage on the ThinClientOS.
- 6.4. Select
if you want to add support for Java applets.
- 6.5. Select
if the browser will be loaded in full screen or not.
- 6.6. To
add bookmarks to the browser simply type in a “Name” for the site
(example: 2X Software) and its “URL” (example:
http://www.2x.com). Then click on “Add
Bookmark” to add the site.
- 6.7. To
delete a bookmark simply click on the delete icon next to the bookmark or press
“Delete” from your
keyboard.
- 6.8. If
you require the use of a proxy server enter the appropriate settings inside each
text field.
- 6.9. Note
the formatting of wild cards to omit addresses to be passed to the proxy
server.
- 6.10. Click
on “OK” when
finished.
- 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.
- 7.1. Click
the “New Profile”
icon.
Screenshot 22: List of configured profiles.
- 7.2. A
new form will load which contains the different sections needed for you to add a
new profile
Screenshot 23: Adding a new profile.
- 7.2.1. Start
by giving the user profile a unique name that can be used to quickly identify
the different profiles in the list.
- 7.2.2. Select
which users listed, from the Active Directory, will be included in the profile
by selecting the user(s) and clicking “Add”. The users will
immediately be visible in the list box on the right. You can remove a user(s) at
any time by clicking on
“Remove”.
- 7.2.3. You
can now select which remote desktops, published applications and local web
browsers will be available to the users.
- 7.2.4. To
add the new User Profile click on “OK” and you will be redirected to
the main User Profiles page where you will be able to see the new User Profile
added.
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:
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.
- 7.3. To
add a new user simply inside the Directory in which the user will be added and
click on ”New User”. Then enter the username, the full name and
check the Profile box where you want the user to
join.
Screenshot 26: Adding a new
Local User
- 7.4. To
add a user to a local profile go to User page from “User Profiles”
> “Directory” > your
directory and check the box where you want the user to
join.
Screenshot 27: Adding an existing user to a User
Profile.
- 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.

Screenshot
28: 2X ThinClientOS
- 8.1. Click
the “Browse...” button to locate and select the file downloaded.
Click on “OK” to install the new image. Once the file is uploaded
successfully it will show up as a new item in the “ThinClientOS”
section of the Management Console.
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.
- 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.
Screenshot 30: The Management Console showing configuration
status
- Once
all the initial configuration elements have been completed, you can log out of
the Management
Console.