Frequently Asked Questions and YouTube Demos
- Where are the instruction manuals for TLXOS & the ThinLinX Management Software (TMS)?
Download the TMS manual here
Download the TLXOS manual here
- How do I install the 60 Day Free Trial of TLXOS?
The TLXOS installers available from the ThinLinX Download page include a 60 Day Free Trial which is built into the Installer. During the installation the installer automatically connects to the ThinLinX License Server to Register the Free Trial. To do this you must be connected to the Internet and NOT behind a Web Proxy, you must also have a DHCP Server on your Network. You can buy a License from the ThinLinX online Store at any time during the Free trial and Register your device using TMS, this is the most convenient option or alternatively at the end of the 60 Day Free Trial your device will boot into Upgrade mode until it is Licensed. To return to normal mode you use TMS / Tools / Product Registration to License it, wait a few seconds until you see Product Registered appear in the TMS Status line, then use TMS / Tools / Exit Upgrade mode to return to Normal mode.
- I use VMware not Citrix, how do I install the VMware Horizon Blast Extreme client for the Raspberry Pi?
Install the ThinLinX VMware Horizon Client Hotfix which we have made available to VMware, you have to join the VMware RPi Beta program to receive access to the Hotfix. The performance is similar to Citrix HDX, you WILL be impressed, please contact email@example.com for more details on the Beta program
- How do I configure TLXOS Citrix HDX mode to auto connect and auto login?
You must install the new TLXOS 4.3.0 which includes Citrix Receiver 13.5 and supports not only H.264 decode but also the new V2 API, mixed mode H.264 & JPEG
Set the timezone using the TMS Timezone Icon, this must be set to the same Timezone as the Citrix Server
Use TMS to upload the client end SSL Certificate to the RPi's by selecting the check boxes next to their names, then click on the Upload Icon, Select SSL Certificate, browse to the Directory with the the SSL certificate which must have a .pem extension. Certificates can be exported in either DER (binary) or PEM (ASCII) format. If you export your certificate using Windows it will be DER by default - use the "Base64-encoded" option instead; this is what Windows calls PEM. The ".cer" filename extension doesn't really mean anything and is used for both formants
Use TMS Protocol Icon to select HDX mode put your StoreFront server name (must be the FQDN as exactly it appears in the server's SSL certificate!) in TMS' "Hostname[:Port]" box, your logon credentials in the TMS autologin boxes, and (optionally) the name of any application or desktop you want to automatically launch in the "Cmd line arguments" box. The application/desktop name is just the human readable label as it appears in StoreFront or the web UI, and you don't have to quote it if it contains spaces.
Reboot, The RPi will connect and Log into the Storefront, you will see all your authorised Apps and Desktops, or if you have added the App or Desktop name in the Cmd line arguments box the App or Desktop will auto launch
Ensure that you enabled http basic authentication on the storefront servers
- I am using NetScaler and can not connect in HDX mode but Web mode works
Are you using a Netscaler gateway via HTTPS, with the back end HDX servers on your internal network using HTTP? Have your Windows Receiver clients been registry hacked to allow insecure HTTP StoreFront stores?
If so, you should be aware that there is *no way* to perform an equivalent hack on Linux Receiver (we have asked Citrix to consider adding this). It is therefore essential that *both* the Netscaler gateway *and* the StoreFront server are configured to use HTTPS, and that the client is able to validate both (has all necessary CA certificates installed).
Web mode has no such restriction, which is why it works for you in Web mode but not HDX.
- When I attempt to register devices using TMS I get an error "SSL handshake error All product registration requests have been cancelled"
Some versions of Windows are missing the SSL Certificate that TMS needs, you can fix this easily by using Internet Explorer to connect to the ThinLinX License Server at https://tls.thinlinx.com
Windows will download and install the missing SSL Certificate, close TMS, reopen TMS and now you will be able to Register your RPis
- On the Micro Center HDX Ready Pi how do I configure the Web Browser to connect to my Citrix Server URL?
Either on the local configuration screen or using TMS select the Protocol Tab, select Web mode, enter your Server URL into the Cmd line arguments box
- How does the ThinLinX Management Software (TMS) discover the devices running TLXOS?
There are three discovery methods available to TMS, the default two methods are UDP Broadcast packets which are broadcast at 5 second intervals, (this interval can be adjusted under TMS / Edit / Settings) and DHCP Option Flags. The UDP broadcasts can be toggled on and off by clicking on the TMS Discover Icon
The Third Discovery method is to configure an already discovered Device by using TMS / Tools / Configuration / TMS server configuration, just select the Static check box and enter the Name or IP Address of the PC running TMS. You can leave the default Port at 8085, if you change the default Port you will also need to change the default TMS Port using TMS / Edit / Settings. You can also use the local configuration menu on the device running TLXOS to configure these settings
Once the Thin Client has been discovered by TMS commands can be sent to it. UDP Discovery can only be used on the same Subnet as Thin Clients, if you are shipping your Thin Clients to a regional Office or they are situated on a different Subnet you will need to use DHCP Option Flags or the third method above.
TMS communicates with the Thin Clients running TLXOS using a secure SSL connection, this allows a Thin Client that has been configured using DHCP Option Flags or the third Discovery method above to be located anywhere in the World. The Thin Clients can even be behind multiple Firewalls as they will tunnel out initiating the SSL connection to TMS
DHCP option flags can be used to pass a default configuration to TLXOS, consisting of TMS location and Port number, the IP Address or name of the Remote Desktop Server to connect to and the Protocol to use such as, WEB, HDX, RDP, RFX etc.
At the moment we have four options but may add others in the future. The Option Flags must all be configured as “Text” not “Integer”
Option 231 point to the TMS location
Option 232 sets the TMS Port number
Option 233 sets the IP, Name or URL of the Server to connect to
Option 234 sets the Protocol, in this case Web or HDX
The Linux version of TMS is built into every version of TLXOS, if you wish to use a Raspberry Pi as a TMS console you can do that by switching the Protocol to TMS. When using the Linux version of TMS built into TLXOS always accept the default installation location when switching to TMS mode as this location is writable.
- When I connect to a Remote Desktop using the Raspberry Pi2, I do not hear any Audio
This problem occurs with some Monitors. If TLXOS detects a HDMI Monitor the Audio is output through that, otherwise through the audio Jack. To get around this issue, you can turn off the RPi, remove the SD Card, place into a Card Reader and edit the config.txt file in the tlxboot partition, just uncomment the line hdmi_drive=2 by removing the # in front of that line. Save the file, insert into RPi and boot up.You can also adjust the default volume before connecting to the Remote Desktop session by pressing Ctrl-Alt-v
- The ThinLinX Management Software (TMS) does not discover my TLXOS device, how can I fix this problem?
and reboot, select TLXOS and press enter.
The golden rule when using the default UDP discovery mode is to never run more than one instance of TMS at once. When you launch TMS it sends UDP discovery packets with the IP ADDRESS and Port number of the system running TMS, the TLXOS clients connect to that System. If you launch another instance of TMS on a different system it will not see the clients as they have already connected to the other system.
Close all the instances of TMS that are running and then just run the one instance
The Rpi does not have a Real Time Clock, ensure your DNS is set up correctly as the Rpi needs to resolve names to contact the Time Server.
After the clients are discovered you can use TMS to set the IP ADDRESS and Port number of the system running TMS, you would use this mode to manage your clients anywhere in the world from one central location. Use TMS / Tools / Configuration / TMS Server configuration
The default UDP discovery only works on the same Subnet
TMS is also built into TLXOS, you can even use a RPi in TMS mode if you want to. Just switch the protocol to TMS
On some versions of Windows some dll files required by TMS are missing
TMServer.exe uses the DLL msvcr100.dll and srvcli.dll which are both in the folder "C:\Windows\SysWOW64\"
These DLLs are most likely missing if you don't have "Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)" installed.
Downloaded it from here https://www.microsoft.com/en-us/download/details.aspx?id=8328
- What do I do if my USB Keyboard and Mouse do not work on the Intel NUC
This problem is easily fixed, just boot the NUC while pressing F2 to enter the BIOS, select USB Legacy to on. Depending on the version of the BIOS in your NUC you may have to select USB XHCI to Off. Save the BIOS changes, reboot the NUC
- How do I upload a private CA certificate to TLXOS devices to allow them to connect to Storefront servers.
You must use the ThinLinX Management Software (TMS) to install the SSL Certificate. You can install the Certificate to hundreds of TLXOS Devices simultaneously if you wish to. Use TMS / Tools / Install / Install file on device / Install SSL Certificate.
- How do I obtain root access on a device running TLXOS?
The O/S has been tightly locked down to help prevent thin clients from being used as an attack vector against servers. Although SSH is installed, it does not support password authentication, and in any case none of the accounts on the system – including root – have password hashes; they are all locked accounts.
The only way you can get root access is to SSH in as root using a trusted key. By default, only public keys belonging to ThinLinX developers are listed in /root/.ssh/authorized_keys, but it is possible to use TMS to install more via the Install File on Device option in the Tools menu. The public key that you upload must be in OpenSSH format. On Windows platforms, PuTTYgen (part of the PuTTY suite - http://www.chiark.greenend.org.uk/~sgtatham/putty/) can be used to display the public key of a PPK file in OpenSSH format (copy and paste from the text box at the top – do not use the Save Public Key button, as creates keys in a non-OpenSSH format). If you have trouble logging in add a blank line before and after the pasted SSH key in your text file. That should sort out any compounded confusion over where the line breaks are. Also, please avoid putting non-alphanumeric characters that may potentially cause problems for the Linux shell (such as spaces or single quotes) in the name of your text file.
- How do I set up Dual or Triple Displays on the Intel NUC
Use the local Configuration menu to set up the Displays. The local Configuration menu has an Identify Monitors Tab which makes the set up easier. Select Configure, Displays, under Video Mode, click on Extend Desktop, in the case of the Dual Display DE3815 NUC to set the left Display to VGA and the Right Display to HDMI, set Output 1, Connector Tab to VGA, you can leave the rest of that line at the defaults, set Output 2, Connector Tab to HDMI, set position Tab to Right of, set Referent to Output 1, you can leave the rest of that line at the defaults. Ensure the Output 3 Connector Tab is set to None, click on Save Settings
- HOWTO set up your Printers
USB Locally connected Printers are easy if you are using Citrix or RemoteFX...In the case of Citrix plug the Printer into the NUC, boot the NUC and connect to the Remote Desktop, the Printer will be detected and the drivers will be installed. In some cases Windows won’t be able to find the drivers in which case you will need to go the Printer Manufacturers Website, download and install the Drivers. In the case of RemoteFX, boot the NUC with the Printer attached and then use the ThinLinX Management Software (TMS) to redirect the printer using TMS / Tools / Setup USB Redirection. Select the checkbox next to the Printer and then reboot the NUC to save the configuration. Connect to your Remote Desktop the Printer will be detected and the drivers will be installed. In some cases Windows won’t be able to find the drivers in which case you will need to go the Printer Manufacturers Website, download and install the Drivers.
In the case of a USB Printer using standard RDP or a Network Printer you must configure CUPS on the NUC to enable the remote system to see the Printer. Just select Web Mode to launch Chrome and then click on the Configure printers Bookmark at the top left.
Chrome will connect to the Local CUPS Server running on TLXOS
Please Google CUPS (Common Unix Printing System) for the fine print on how to set up CUPS printing.
For the best results when you set up your local printer you should consider providing the Windows PPD file instead of using the closest Linux Printer Driver. This is particularly important for Multi Function Printers where no Linux PPD driver exists
Once you have the Windows PPD file extracted from your Windows installation Disk you can use TMS to copy the PPD file to the NUC / Re-PC / Compute Stick / RaspberryPi 2
To copy the PPD file use TMS / Tools / Install File on Device / Select the PPD file
When you configure CUPS, select this PPD file
Reboot the NUC to save the PPD file to flash
You can also configure a Printer using CUPS as a RAW printer where the Server Printer Driver does all the work before sending the Raw data to the Printer
We also support Google Cloud Print
- Can't connect to a RDP or RemoteFX session
The most likely cause is the default TLXOS RDP or RemoteFX Security is too low, use TMS to set NLA on. You select Protocol, RemoteFX, click on the Security tab change from the default to NLA
- Can't install TLXOS
The most likely cause is that you removed the USB stick too early, you should wait until the installer prompt for its removal at the appropriate time.
- TMS can't discover the client
Press Control AlT and t Lower case t for terminal
This will open an xterm, enter /sbin/ifconfig to see the IP ADDRESS and ping whatever you like.
TMS in installation mode uses UDP broadcast, check your Firewall on the Server. You could try installing TMS on a VM and use that or any other version of Windows 7, Windows 8 etc. Please read the installation manual again available from here http://thinlinx.com/download.html
We will be releasing Apple Mac and Linux versions of TMS shortly
Also once you have installed TLXOS you can use TMS / Tools menu to configure the IP ADDRESS and port number that you want the client running from to use to connect to TMS. This way you can configure devices, ship them and manage them from anywhere in the World. We also have a dhcp options choice where a DHCP server at the client end will supply the TMS Server IP ADDRESS and Port number to connect
- How can I start an xterm?
Exit fullscreen or defocus your fullscreen application and then use control-alt-t. And anticipating your next question, no, there is no way to su to root in this window.
- How do I get out of fullscreen mode?
It depends on what mode you’re in:
HDX: shift-f2. Allegedly.
RDP and RemoteFX: control-alt-enter. This will release pointer grab, but the FreeRDP window will still intercept keystrokes while the window is in focus.
Spice: shift-f11 (and then shift-f12 to ungrab the keyboard and pointer).
VNC: control-alt-shift-f, or use f8 to bring up the configuration menu and click on Full Screen to toggle it off.
X11: you can’t, but you can use control-shift to toggle key grab between local and remote window managers. This will allow you to use local keyboard shortcuts such windows-d to show the desktop, control-alt to switch windows and so forth.
Everything else: there is no fullscreen mode, you just have a window that’s been sized to fit the current screen resolution. You can use normal window manager controls to resize or minimize it.
- Local audio is too loud/quiet, so I can’t make audio quiet/loud enough using remote or web page volume controls. Is there a volume control for local audio playback?
Yes, but right now it’s a bit ugly. Sorry about that. First exit fullscreen or defocus your fullscreen application, and press the control-alt-v key combination. This will bring up an ALSA mixer GUI. The controls that will probably be of most interest to you are DAC2 Digital Coarse and DAC2 Digital Fine..
- I tried changing resolution but now my screen is black / my monitor says “scan rate out of range”. I don’t have TMS / can’t get someone else to change settings using TMS. What can I do?
Use the appropriate key sequence to exit from fullscreen mode for whichever protocol you are currently using (see “How do I get out of fullscreen mode”, above), and then press the control-alt-r key combination twice within two seconds. This will cause your client to reset to a safe default resolution (1024x768) and reboot.
- Is there a way to bring up the configuration tool other than from the dialog window that comes up after a session has ended? I don’t want to close my application right now.
Yes. First exit fullscreen or defocus your fullscreen application (see “How do I get out of fullscreen mode”, above) and then use the control-alt-c key combination.
- My thin client can’t connect to anything and the configuration tool says that it has no IP address. What can I do?
Unplug the network cable, wait at least six seconds, and then plug in back in again. This will reset the interface and trigger a new DHCP request.
- Can I share my display with another person (for training or troubleshooting purposes)?
Yes. RDP and HDX (ICA) protocols have their own session shadowing features – which may or may not work with our client implementations – but TLXOS also has a VNC server capability that you can use. To initiate a shadow connection, first exit fullscreen or defocus your fullscreen application (see “How do I get out of fullscreen mode”, above), and then press control-alt-s and enter the hostname or IP address and TCP port number of the shadower in the window that appears.
You have the option of either connecting to a listening VNC client over an SSL connection (active mode), or setting up a TCP port forward via an SSH tunnel and awaiting a connection (passive mode). Active mode has the advantage of using ordinary HTTPS and being able to use a web proxy, which makes it suitable for highly secure environments that don’t permit direct connection to the Internet. Passive mode has the advantage of also providing an SSH port forward, allowing SSH as well as VNC access from the remote SSH endpoint. Unlike typical VNC servers, both modes of operation “dial out” to a remote server, which permits traversal of firewalls and NAT gateways and implicitly ensures operator consent.
For active mode, the shadowing system must be running stunnel (www.stunnel.org) redirecting to a VNC client application in listen mode (we recommend TurboVNC - www.virtualgl.org). Use of SSL is mandatory. For passive mode, the shadowing system must be running an SSH server that accepts publickey authentication and permits port forwarding, and has a user with a ~/.ssh/authorized_keys file that contains TLXOS’ SSH host public keys. A thin client using TLXOS can do both these things, and can therefore be used to shadow sessions on another TLXOS thin client.
- The web browser / Citrix / whatever says that the server SSL certificate is not trusted, but I’m sure that I have installed the correct CA certificate. What’s wrong?
It’s likely that your thin client’s local clock is wrong. To verify this, you can start a terminal using control-alt-t and then enter “date” in the window that appears. This happens because the TLX1000 has no battery-backed clock, so unless it can contact a network time server from which to get the current date and time, it will revert to a nonsensical value such as the year 2000 or 2027 whenever its power is reset. By default, it will try to contact Internet time servers, which may not succeed if there is an intervening firewall or if hostname lookups are failing.
To fix the problem, use TMS or the local configuration tool to set the time server to the name or IP address of a local NTP server that the client will be able to connect to. Typically this would be the same as the local DNS server (if it is an Active Directory domain controller) or default gateway (if it is a router appliance).