If your computer budget is too high, then you need to look at this instructable. Great way to save on costs. Older machines can be converted to thin clients therefore reducing the need to purchase new equipment. Linux is replacing proprietary systems everywhere.  Get on the bandwagon and save money! This project (the first time we used it), saved us over ten thousand dollars in licensing fees alone for just a small office. That could make the difference in the bottom line. Those savings do not even touch the amount we saved in hardware costs by not having to get all new equipment.  It's your wallet.

ltsp (Linux Terninal Server Project).LTSP allows you to have one computer to do the heavy lifting for several or many thin clients. It is cheaper to purchase thin clients than full desktops, therefore less computer hardware cost overall. Also you have only one computer to support software wise as you only have to update just one machine instead of many.  Ltsp has been around a long time and I think was started by Redhat, but picked up by the community. You can cluster ltsp together and build massive networks, It is also very good for small businesses and small schools such a day care center.

What's needed:
Basic knowledge of linux and networking (tcpip setup and usage). If not get a pro to help.
Internet connection for downloading and installing software.
Computer (min 300mhz, but the faster the better) with two nics (network interface cards). the nic that will be used for the thin clients must be set up as static (256 meg ram plus 64 - 128 meg ram for each thin client. (i'm using 512 meg ram and a 800mhz machine for demo purposes. 
Some pxe bootable x86 compatible thin clients (or pxe bootable x86 based diskless pc's) with 128 meg ram or better that are setup for getting dhcp dynamically based ip addresses. The more memory the better and no need to statically assign ip addresses of client systems.
Network cabling (as needed). (100mhz or better).
Network switches (as needed). (100mhz or better).

Note: www.rom-o-matic.org allows you to make cd/usb/floppy boot disks if your computer does not support pxeboot.
Later you can also add support for other architectures such as the intel atom or even the old ppc based macs. If you are using a 64bit server, you will need to load the support for the 32bit architecture to support the older x86 systems.
Original instructable: https://www.instructables.com/id/Using-Thin-Clients-a-quick-way-with-Debian-linux/

Future instructables:
Part II  LTSP Internet access and some safety net.  https://www.instructables.com/id/Another-almost-free-computers-thin-client-set-up-P/
Part III LTSP Maintenance. https://www.instructables.com/id/Part-III-LTSP-Maintenance/
Part IV LTSP Clustering (in progress)

Note: the original version of ltsp (v4) supported the old less than 128 mb thin cleints and computers. Some people say that they run both at the same time, but I have never tried it. Still do have a server with the old version of ltsp on it. Just to keep the old thin clients useful.

Setup a Raspberry Pi as an LTSP client: https://www.instructables.com/id/Raspberry-Pi-Jack-of-all-trades/#step7

Note: You can use an RDP client to access MSWindows servera and Vnc to access Apple based systems. So you are not locked out of access those worlds.

Step 1: Software Install (on Ubuntu)

Pretty straight forward.  Installs the server side software.

Open a terminal prompt and type:
$ sudo apt-get update
$ sudo apt-get  install ltsp-standalone-server openssh-server.

This may take a short while depending on your internet connection.

Note: you may want to add a lighter desktop to ease memory usage/

$ sudo apt-get update
$ sudo apt-get install lxde

Step 2: Update Dhcpd.conf.

Updating the configuration for the DHCP:

1. Edit the dhcpd.conf for the ltsp. You will need to change the domain name to your preference. You will also need to change the network to agree with the ipadress of the nic to the ltsp thin client network. in this case it should be the one described below. I used for the pictured config,  Nic should be set to boot to use static ip or otherwise dhcp and other needed services will not start.

$ sudo nano /etc/ltsp/dhcpd.conf

# Default LTSP dhcpd.conf config file.


subnet netmask {
    option domain-name "example.com";
    option domain-name-servers;
#    option netbios-name-servers;
    option broadcast-address;
#    option routers;
#    next-server;
#    get-lease-hostnames true;
    option subnet-mask;
    option root-path "/opt/ltsp/i386";
    if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
        filename "/ltsp/i386/pxelinux.0";
    } else {
        filename "/ltsp/i386/nbi.img";

2. Make sure dhcpd is set to use the correct network interface.On mine it is eth1 or the second network interface.

$ sudo nano /etc/default/dhcp3-server:


3. Make sure the main dhcpd config honors the ltsp dhcpd.conf configuration.

$ sudo nano /etc/dhcp3/dhcpd.conf

Add the following line near the top:

include "/etc/ltsp/dhcpd.conf";

One last command to make sure the dhcpd server starts at boot up.

$ sudo chgrp dhcpd /etc/dhcp3/dhcpd.conf

Step 3: Set Up the Client Software.

The thin clients will boot their own system, so you are actually have two operating systems. one for your server and one for the thin clients. Almost like what is called a dual boot computer. This will take a while depending on the speed of the network and your server,

$ sudo ltsp-build-client
$ sudo ltsp-update-image

Note: I used a system with a 40 gig hard drive and only about 5 gig used.

Reboot the machine after this is all done, but not before then.

Once the server is back up, you can log in and set-up users. (System > Administration > Users and groups)

Start up one of the thin clients and watch the magic happen. You should be presented with a login screen.

This ends part 1. In part 2 (another instructable) we will be demonstrating how to do updates and tweaking the system as well as add- management packages. (In Progress)

Let me know if you have any questions.

Step 4: Other Screen Shots and Info.

Just some other shots I took for de-bugging purposes.

1st shot: what happens if your nic is not set to autostart the static ipaddress.

2nd and 3rd shot: restarting of the dhcpd server to make sure it is working.

4th shot: Make sure thin client is set to look for the dhcp address.

Might add a few more.

Other sources about LTSP:

Step 5: Screenshots

Screenshot of a compaq amd64 accessing the server as a pxeoot remote client with lxde desktop. Video and sound work quite well.

Screeenshot of another system accessing the system via rdp (xrdp must be installed on the server.) Using gnome desktop for normal login.

Step 6: Other Thin Clients Work With Ltsp Also.

Diskless Pentium 1 - 233mhz
Standard thin client that supports pxebooting/ (we use Compaq t32/30 clones) most any decent x86 pxebootable system should work.
Also booted Apple "new world" G3's into ltsp via netboot. The latest ltsp no longer supports the PPC  framework, but it could be installed later.
You could also add the arm architecture to the mix.There is also an image that will let the Raspbeyy Pi as as a thin client for Ltsp. Tried it and it works. Information about the Beaglebone can be found at: http://elinux.org/BeagleBoardUbuntu
This one?
<p>Model number?</p>
<p>3com usually make good equipment. Seems like it would work as a switch.</p>
<p>To my knowledge, that is not my picture, but to answer the question, if it is a true router, it should work,</p>
No, its not your picture, i meant is this little box the switch. Thx for your answer.
<p>Can you use a OLD officeconnect switch 5 as the &quot;switch&quot; you show in the picture?<br>(I think so, but ain't totally sure)</p>
<p>If you are talking about the white box, that is a thin client and not a switch, but yes it works if you use pxeboot.</p>
<p>Would this work with raspberry pi's as thin clients?</p>
<p>Yes, In fact I have an older image or a pointer to an older image for the RPI in the thin client instructables.</p>
Hello! Let me start off by saying I found your instructable to be very helpful. I have always wanted to do something like this but I never could figure out how to do it. But I ran into a problem, the thin client won't boot. I followed your instructions exactly except I did it on ubuntu 10.04 Desktop i386 edition. I put etherboot on a CD and booted it on a thin client. It went through all the DHCP junk ok but then it halted and said &quot;No root path or file defined, NO BASIC System halted&quot;. Can you please help me? Thanks for helping!
Are the thin clients on the separate ltsp network and not your normal local lan network? If you are using only one thin client and not using a switch or hub, you may need to use a crossover cable when only one client is connected. Normal networking cablling protocol and nothing to do with ltsp. Does that make sense? You also need to make sure the network card is supported on your thin client software and there are not other dhcp servers (i.e. router on the same ltsp network).
Would Handy Cafe also work with this?<br>http://www.handycafe.com/
It depends. Handy Cafe is for MSWindows computers and LTSP is for linux based computers. If they were on separate machines or one was in a virtial machine you might be able to have them work together. in some way. There is also Zencafe available for linux that might be a better choice for linux if you are wanting to go in that direction. I probably need to do an instructable about it. Internet cafes were all the rage for a while in this area until cable took hold and now they have all disappeared.<br><br>Update: just installed xrdp so a MSWindows type machine could access the server. Fixing to install Zencafe and see if it works with xrdp.

About This Instructable




Bio: computoman.blogspot.com Bytesize articles instead of a trilogy in one post.
More by Computothought:Coffeepot meals Easy sun hat Easy cakes and pies. 
Add instructable to: