Configuring 2X
ThinClientServer
Log into 2X
ThinClientServer
Screenshot 26: The Administrator login page for the
Management Console.
- Type
in the username and password for the administrator who will have the rights to
configure 2X ThinClientServer. Note that each change applied to 2X
ThinClientServer will be logged in the
“Auditing”
node.
Screenshot 27: Management Console main information
screen
- After
logging into 2X ThinClientServer 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, 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.
- 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 28: Configuring the Directory Server.
- 1.1. Domain
Name: Enter the domain name containing the users which will need to be
assigned thin client logon rights.
- 1.2. 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.
- 1.3. Password:
Enter a password needed by the Active Directory to authenticate the user
specified above.
- 1.4. Primary
AD Controller: Enter the fully-qualified domain name (or the IP address)
of an Active Directory server.
- 1.5. Backup
AD Controller: 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.
- 1.1. 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.
- 1.2. Click
“OK” when ready.
Desktop Components
Remote Desktops
- You
can add a Remote Desktop connection. This desktop can be of type RDP, NX or
Citrix ICA. These settings will connect the 2X 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 taskbar. To start adding
Remote Desktops, choose the “Remote Desktops” node under
“Desktop Components” in the
sidebar.
Screenshot
29: Add the settings for a direct connection to a Terminal Server.
- 1.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.
- 1.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.
If
you use Citrix (ICA) you can enable a River Cipher encryption for added
security.


- 1.3. Enter
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.
- 1.4. Enable
SSL to encrypt the data that is being passed for communication. Specify the
speed of your bandwidth that you will use to connect to your remote desktops.
Compression allows you to compress the information used for RDP connections.
Enable “Auto Reconnect” if you would like to automatically reconnect
to your remote desktop if a connection is lost.
- 1.5. Specify
the “Redirection
Settings”
You
may specify which redirection facilities (sound, disk, printing, serial ports
and smart card) will be available to this protocol.
- 1.6. 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.
If you have multiple monitors,
you can span the Remote Desktop across all the monitors.
- 1.7. If
you use the NX protocol to connect to an NX server, you can use a custom DSA key
to authenticate users connecting to the NX
server.
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.
Published Applications
- Click
on “Published Applications” node under “Desktop Connections to
deliver published applications to the 2X ThinClientOS
users.
Screenshot 30:
Add the settings for published applications.
- 1.1. Enter
a name for the source of your published applications and/or desktops. This name
will not be seen in the 2X ThinClientOS.
- 1.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.
** 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 add-ons have been installed correctly on your Citrix
Servers.


- 1.3. Select
the “Connection Mode” and the version of the 2X ApplicationServer
you are running.
- 1.4. You
can choose to filter the published items that are displayed to the user. You can
display the published applications, published desktops or both.
- 1.5. 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.
- 1.6. If
you specify the ICA (Published Applications) protocol type you can choose to use
“HTTPS” if it is required by your Citrix Administrator.
- 1.7. Select
the bandwidth available on you network connection.
- 1.8. Compression
allows you to compress the information used for RDP connections.
- 1.9. Enable
“Multimedia Acceleration” to allow the client to carry out some
processing when playing multimedia items. Depending on your hardware, this could
improve performance.
- 1.10. Specify
the Redirection
Settings
You may
specify which redirection facilities (sound, printer, disk, serial ports and
smart cards) will be available to this protocol.
It
will be necessary to repeat this procedure for each machine providing a list of
applications that you wish to support.
- 1.11. Enable
“Use Primary Monitor” to open the published application in the
primary monitor when multiple displays are available.
- 1.12. If
you are going to use a proxy server for the published application, you must
select the type of proxy server that will be used. Enter the proxy server
address and the proxy port number. Enable “Proxy requires
authentication” if the proxy server requires authentication to be used.
Note that the user’s 2X credentials used for 2X ThinClientOS will be used
to authenticate with the proxy server.
Local Web Browser
- Next
you can add the settings for a customized web browser on the 2X 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 31:
Add the settings for a local web browser on the thin client.
- 1.1. Enter
a name for the web browser. This name will be used on the 2X
desktop.
- 1.2. Set
the default homepage for the browser.
- 1.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.
- 1.4. Select
if you want to add support for Java applets.
- 1.5. Select
if you want to enable the Media Player inside the browser.
- 1.6. Select
if the browser will be loaded in full screen or not.
- 1.7. 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.
- 1.8. To
delete a bookmark simply click on the delete icon next to the bookmark or press
“Delete” from your
keyboard.
- 1.9. If
you require the use of a proxy server enter the appropriate settings inside each
text field.
- 1.10. Note
the formatting of wild cards to omit addresses to be passed to the proxy
server.
- 1.11. Click
on “OK” when
finished.
VMware View
- A
connection to a VMware View desktop can be added to a 2X ThinClientOS desktop.
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
VMware View connections, choose the “VMware View” node under
“Desktop Components” in the
sidebar.
Screenshot
32: Add the settings for a VMware View connection.
- 1.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 desktop
he/she will be connecting to.
- 1.2. Enter
the server addresses and “Port
Number”. The
“Primary Address” may be a hostname or an IP address. The default
port number is automatically set – this value may be customized if
necessary.
- 1.3. Enable
SSL to encrypt the data that is being passed for communication. Specify the
speed of your bandwidth that you will use to connect to VMware View. Compression
allows you to compress the information used.
- 1.4. Specify
the “Redirection
Settings”
You
may specify which redirection facilities (sound, disk, printing, serial ports
and smart card) will be available to this protocol.
- 1.5. Specify
the “Display”
Settings.
You may
select the desired colour depth from the drop down list.
Enable
“Fullscreen” to run the connection in fullscreen.
If you have multiple monitors,
you can span the Remote Desktop across all the monitors.
VNC
- A
connection to a VNC desktop can be added to a 2X ThinClientOS desktop. These
settings will connect the 2X 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 VNC connections, choose
the “VNC” node under “Desktop Components” in the
sidebar.
Screenshot
33: Add the settings for a VNC connection.
- 1.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 desktop
he/she will be connecting to.
- 1.2. Enter
the server addresses and “Port Number” The “Primary
Address” may be a hostname or an IP address. The default port number is
automatically set – this value may be customized if necessary.
- 1.3. Enabled
“Shared” to allow different users to simultaneously connect to the
same desktop.
- 1.4. Enable
“View Only” to only allow viewing access to the users. This means
that users would not be able to interact with the connected desktop but only
view it.
- 1.5. Enable
“Authenticate” if the user requires a username and password to
connect to the desktop.
- 1.6. Specify
the speed of your bandwidth that you will use to connect to VMware View.
- 1.7. Specify
the “Display”
Settings.
You may
select the desired colour depth from the drop down list.
Enable
“Fullscreen” to run the connection in fullscreen.
If you have multiple monitors,
you can span the Remote Desktop across all the monitors.
User
Profiles
- 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.
- 1.1. Click
the “New Profile”
icon.
Screenshot 34: List of configured profiles.
- 1.2. A
new form will load which contains the different sections needed for you to add a
new
profile.
Screenshot 35: Adding a new profile.
- 1.2.1. Start
by giving the user profile a unique name that can be used to quickly identify
the different profiles in the list.
- 1.2.2. Select
which users listed, from the Active Directory, will be included in the profile
by selecting the user and checking their respective
checkbox.
- 1.2.3. You
can now select which remote desktops, published applications and local web
browsers will be available to the users.
- 1.2.4. You
can add applications such as Skype and a PDF Reader to be accessible by the
users on the 2X ThinClientOS
- 1.2.5. 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 36: New User
Profile Added
If
you selected “Local Users” as the user source, the user interface
presented will be as follows:
Screenshot 37: Adding a User Profile with local
users.
“Local
Users” are stored in the central database of the 2X ThinClientServer. They
have got nothing to do with Windows/Linux local user accounts and
credentials.
- 1.3. To
add a new user select 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 38: Adding a new
Local User
- 1.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 39: Adding an existing user to a User
Profile.
2X ThinClientOS
- To
add a new version of the 2X ThinClientOS click on “ThinClientOS”
node under the “System” node from the sidebar. Click on
“Install ThinClientOS Image” to upload a new 2X ThinClientOS. After
an image is uploaded you can use the “Set as Default” button to
update the default settings for the OS. Thin clients using a specific OS and not
the default settings will not be
affected.

Screenshot
40: Default 2X ThinClientOS displayed in bold
Screenshot
41: 2X ThinClientOS
- 2.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. Note that a link is provided to download the
latest 2X ThinClientOS from http://www.2x.com
Screenshot 42: Browse for a 2X ThinClientOS 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.