Setting up an Ubuntu Thin Client Server

With austerity being the watchword of our times being able to get as much out of that IT hardware you have is as important as ever, more so  when the industry is in shift at an OS level and maybe the hardware you have isn’t quite up to the task of Windows 8?

I have put this post together for a personal reference, it it helps someone else then that’s a good thing. 

Thin Client computing is a good example of how the IT world goes round in a circle, 30 or so years ago computers were huge beasts filling rooms the size of offices. To attach to them you had a termina, that terminal had no hard disk and everything you did was done directly on the “mainframe” While examples of this style of computing never died they were quickly outpaced by the computers we know today where the processing and computing is done at your desk and the files then saved to a server. (The client server model).

However as networks have become spedier, and servers more powerful the recycling of that old Idea has gone full circle and in this article i’m going to show you how to install an Ubuntu LTSP server which will deliver a complete Ubuntu desktop to a machine with no hard disk over your network. And if you are doing this in an office with an existing AD Infrastructure make use of this so users can use their AD login credentials to access the OS.

LTSP

The Linux Terminal Server Project is not new and has been around for a very long time which has a few key things which are a positive to anyone who wants to implement it. There is a lost of support available online for the projects assisting in many areas which the project developers may not have envisaged the project going. It is well supported and still very much in development and important factor for any technology which you may be looking to integrate into a commercial or educational infrastructure. It has also been integrated into many popular distributions which again provides good backing and help when needed.

Originally, LTSP was a stand-alone package. LTSP had to be installed on top of the Linux distribution you were using, and then configured. As time progressed major Open Source Linux distributions like Ubuntu (Canonical Ltd.), Fedora (Red Hat Inc.), OpenSuSE (Novell), and more began integrating LTSP directly into their distribution releases. At present, LTSP can be installed automatically using the Linux distributions mentioned above. LTSP’s current version is: 5. LTSP 5 addresses many key issues regarding network bandwidth with the implementation of Local Applications. LTSP 5 greatly improves multimedia, and network intensive applications on LTSP Thin Clients.

Installing LTSP

Starting with the Hardy Heron (8.04) release the LTSP installer functionality was moved to the Ubuntu alternate CD. All future releases follow this format.

Using 12.04 provides you with a stable 4 year supported version of Ubuntu.

 Get the Precise Pangolin alternate CD iso from http://releases.ubuntu.com/releases/12.04.

The installer will set up an out of the box working LTSP install for you if your server has two network cards built in.

If that is not the case it will tell you what to modify to run with a single network card.

Once you boot up the CD, hit F4. The “Modes” menu will pop up. Select “Install an LTSP Server”. Now just move on with the install.

Towards the end of the install the installer will start to build the client environment from the packages on the CD. When it gets to the 50% mark it might look like it has hung, it’s not it will just take a while to do the last stage.

Which then will be compressed into an image…

If the installer is done and has rebooted into your new system you will be able to boot your first Thin Client right away. However it’s useful to know what is happening under the hood and you may want to do some changes.

1. Change your available network adaptor IP to a fixed entry.

• Most local network already use the 192.168.0.xx range of IP addresses, but the default install of LTSP relies on this range being available. In this tutorial we will set up the LTSP network on the 192.168.1.xx range.
• You also need a separate network adaptor with internet access during the install process.
• The LTSP server install wants to install it’s own DHCP server, so if you have a router with it’s own DHCP server it could cause conflicts if in the same network IP range.
• So what to do is change your unused LAN port’s IP address to a fixed IP in another IP range. For example my setup has a router with a DHCP server running on 192.168.0.1, and provides the Internet access on the system.  I changed my other LAN adaptor’s IP to 192.168.1.1 , this will be used for the LTSP network.
• NOTE: For some reason the DHCP server does not want to start correctly on system startup if the network adaptor’s IP is not set in the network interfaces config file. (see 1d. below)

1a. Go to Network Connections and select the LAN network adaptor you intend to use for your thin client network and click edit.

1b. Change your adaptor to use Manual IP and set a new fixed IP for the adaptor and save.

This will be your LTSP server IP.

1c. Set the fixed IP for the network adaptor the classic way to ensure the DHCP server starts correctly.

• Add the information for your network adaptor that you selected in 1c. as shown below.
• We added eth0 with a static IP of 192.168.1.1
• Open the Terminal Window and enter :

sudo gedit /etc/network/interfaces

1d. Change the Network Manager config file to allow control of your network adaptor with fixed IP.

• For some mysterious reason if you enter the IP manually in the interfaces file, Network Manager ignores them and you cannot use the Network Manager to control the adaptor any more. So we have to enable it.
• Change the “managed=false” to “managed=true” as seen below.
• Open the Terminal Window and enter :

sudo gedit /etc/NetworkManager/NetworkManager.conf

2. Install the LTSP server.

If you have followed the instructions above you can skip this and head to step 3. If you’ve got a dual nic stock Ubuntu Desktop or Server install you can install LTSP as a package.

• Open the Terminal Window and enter :

sudo apt-get install ltsp-server-standalone openssh-server

​

3. Edit the DHCP configuration for your LTSP server to match your chosen IP range.

• In this case 192.168.0.xx changes to 192.168.1.xx.
• Open the Terminal Window and enter :

sudo gedit /etc/ltsp/dhcpd.conf

​4. Select the network interface/s for the DHCP server

• Add the network devices you would like the DHCP server to run on. In this case we changed the value of INTERFACES to include eth0
• Open the Terminal Window and enter :

sudo gedit /etc/default/isc-dhcp-server

​5. Restart the DHCP server

• Open the Terminal Window and enter :

sudo /etc/init.d/isc-dhcp-server restart

Tip: previous ubuntu versions need to use : sudo /etc/init.d/dhcp3-server restart 

6a. Optional step to configure a Fat Client not a Thin Client before build

• This step is only needed if you intend to use your LTSP server for Fat clients, rather than Thin clients or both. For more information between the differences between Thin and Fat clients and configuration see UbuntuLTSPFatClients 
• This step edits the LTSP build client configuration file to install Ubuntu desktop and create LTSP Fat client image.
• NOTE: only software installed in the Fat client image will be available to the client, and internet access for each client needs to be configured as the clients will not share the server network connection to the internet as is the case with the thin clients.
• Open the Terminal Window and enter :

sudo gedit /etc/ltsp/ltsp-build-client.conf

• Here you can customize your installation image for Fat clients.
• We will only install the standard Ubuntu Desktop system to run on the client side for now. We can install more software to the image later, this is to get a basic Fat client image built.
• Add the following to the file and save.

# ltsp-build-client.conf - many other options available 
# The chroot architecture.
ARCH=i386

# ubuntu-desktop and edubuntu-desktop are tested.
# Ubuntu 12.04 LTS working perfectly with Unity and Unity 2D.
FAT_CLIENT_DESKTOPS="ubuntu-desktop"

6b. Optional step to disable NBD compression

• NDB compression is enabled by default in Ubuntu 12.04 to speed up client disk access and boot times, but takes a much longer to generate a compressed image file. During development work is might be easier to disable this feature and re-enable it when the setup of the client image is complete.
• Open the Terminal Window and enter :

sudo gedit /etc/ltsp/ltsp-update-image.conf

• Add NO_COMP=”-noF -noD -noI -no-exports” line to disable compression. Enable the compressing by adding the # symbol, or delete the line completely
• Make sure the file now looks like this example below and save.

# Configuration file for ltsp-update-image
# Do not compress the client image. Comment out the line below to enable again.
NO_COMP="-noF -noD -noI -no-exports"

6c. Build the i386 (32bit)  LTSP Thin/Fat Client

• This step builds the 32bit Thin Client Ubuntu 11.04 image needed to boot the thin clients on the network.
• This step downloads and installs all the 32bit Ubuntu client elements. Could take a while.
• Open the Terminal Window and enter :

sudo ltsp-build-client --arch i386

​​Tip: to set up 64bit thin clients  leave out the ‘–arch i386′ part and enter: sudo ltsp-build-client 

7. Reboot your new LTSP server to complete LTSP server install

• At this point your Ubuntu LTSP server should be up and running.
• You should be able to boot a Thin Client via the network.
• You could also set up a Virtual Machine to act as a thin client for testing your server. See: How to create a VirtualBox Ubuntu LTSP Thin Client.

Tip: After reboot make sure that the DHCP is running correctly. Open a Terminal Window and enter:

sudo /etc/init.d/isc-dhcp-server status

Tip: If after this point you change your IP address on the LTSP  server you need to enter the following :

sudo ltsp-update-sshkeys

sudo ltsp-update-image --arch i386

8. Set up Thin Client Admin user

• Replace the adminname with your admin user name.

sudo -s -H
chroot /opt/ltsp/i386
useradd -m adminname -G sudo
passwd adminname
exit
exit

• Lock the admin account’s password

sudo chroot /opt/ltsp/i386 passwd -l adminname

• Update the client image

sudo ltsp-update-image --arch i386

 If you are wanting to like the Thin Client login to your existing AD infrastructure then you may not want to setup these local user accounts.  I have included instructions on how to do this at the end as a section 11 

9. Set up a Thin Client User Account

9a. Open Users and Groups

• Make sure you have gnome system tools installed as this has been removed in Ubuntu 12.04.

sudo apt-get install gnome-system-tools

• In Ubuntu 12.04 search for Users and Groups under applications after installation.

9b. Click Add to add new user account

9c. Add new username details

9d. Add new user password

9e. Change User Advanced Settings -> User Privileges

10. Boot your Thin Client from the Ubuntu LTSP server

• Connect your Thin Client computer or Virtual Machine to your LTSP network Switch/Hub.
• Alter the Thin Client Machine BIOS Boot settings to boot from LAN / Network / Pxe.
• Boot the machine.
• If all is set up correctly you should see the following Ubuntu LDM login screen on your Thin Client.
• You will be able to login with your newly created Thin Client username and password.

11. Active Directory Login

Assumptions

It is assumed that you have a Windows 2008 Active Directory Domain setup and working properly along with a DHCP server. Your domain controller can be your DHCP server or you can setup a different box to distribute the DHCP leases. If your domain controller or DHCP server are not setup, please set these up first. It is also assumed that the reader has some basic Linux experience. You will need to know how to move around in the Linux terminal, install applications, and edit files using vi or nano.

Network Layout

For the purpose of this tutorial, this is the layout of the domain.internal network on the 10.0.0.0/24 subnet.

dc.domain.internal

Windows 2008 Server running Active Directory and DNS

server.domain.internal

Windows 2003 Server hosting user home directories and file shares

thinserver.domain.internal

Ubuntu 12.04 server with LTSPv5

dhcp.domain.internal

Add thinserver to the Windows Domain

Before we add thinserver to the domain, we’re going to have to install Samba along with some other packages.

sudo apt-get install samba smbclient winbind libpam-cracklib krb5-user

Make sure that thinserver is named correctly.

hostname

If the hostname command doesn’t return thinserver.domain.internal, rename it to thinserver.domain.internal.

hostname thinserver.domain.internal

Edit the /etc/resolv.conf to use dc.domain.internal as the primary DNS server.

search domain.internal

nameserver 10.0.0.10

On your domain controller create a host (A) record in your DNS for thinserver.

Verify that thinserver can resolve domain.internal:

nslookup domain.internal

The results should look something like this:

test@thinserver:~$ nslookup domain.internal
Server:        10.0.0.10
Address:    10.0.0.10

Name:    domain.internal
Address: 10.0.0.10

Make sure that Samba and Winbind are not running:

/etc/init.d/smbd stop
/etc/init.d/winbind stop

Just to be safe lets backup the smb.conf, krb5.conf, and PAM common files. I like to append the date when I make a backup of a file so that I know when the changes were made.

d=`date "+%m%d%y"`
cp /etc/samba/smb.conf{,.$d}
cp /etc/krb5.conf{,.$d}
mkdir /etc/pam.d/backup
cd /etc/pam.d/
for file in `ls`;do cp $file{,.$d}; done
mv *.$d backup/

Edit the /etc/krb5.conf file to look like this:

[logging]
 default = FILE:/var/log/krb5libs.log
 kdc = FILE:/var/log/krb5kdc.log
 admin_server = FILE:/var/log/kadmind.log

[libdefaults]
 default_realm = DOMAIN.INTERNAL
 default_keytab_name = FILE:/etc/krb5.keytab
 default_tgs_entypes = rc4-hmac des-cbc-md5
 default_tkt_entypes = rc4-hmac des-cbc-md5
 permitted_entypes = rc4-hmac des-cbc-md5
 dns_lookup_realm = true
 dns_lookup_kdc = true
 ticket_lifetime = 24h
 forwardable = yes

[realms]

 DOMAIN.INTERNAL = {
  kdc = DC.DOMAIN.INTERNAL:88
  default_domain = DOMAIN.INTERNAL 
 }

[domain_realm]

 domain.internal = DOMAIN.INTERNAL
 .domain.internal = DOMAIN.INTERNAL
[appdefaults]
 forwardable = true
 pam = {
   minimum_uid = 16777216
   debug = false
   ticket_lifetime = 36000
   renew_lifetime = 36000
   krb4_convert = false
   DOMAIN.INTERNAL = {
	ignore_k5login = true
	}
 }

Edit the /etc/samba/smb.conf file to look like this:

[global]
   workgroup = DOMAIN
   password server = *
   realm = DOMAIN.INTERNAL
   local master = no
   security = ads
   idmap backend = tdb
   idmap uid = 16777216-33554431
   idmap gid = 16777216-33554431
   idmap config DOMAIN : backend = rid
   idmap config DOMAIN : range = 16777216-33554431
   idmap cache time = 60	
   template homedir = /home/%u
   template shell = /bin/bash
   kerberos method = secrets and keytab
   dedicated keytab file = /etc/krb5.keytab
   winbind separator = +
   winbind use default domain = yes
   winbind refresh tickets = true
   winbind cache time = 10
   winbind offline logon = true
   winbind enum users = Yes
   winbind enum groups = Yes
   passdb backend = tdbsam

   server string = Samba Server Version %v
   log file = /var/log/samba/%m.log
   max log size = 50

Moving forward it’s advisable to have a second root terminal open just in case something doesn’t work as expected. Happens to the best of us )

I would recommend creating a “linux_admins” group in Active Directory and adding it to the /etc/sudoers file. An alternative is to add the “domain admins” group and to login using the administrator account.

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
%linux_admins ALL=(ALL) ALL

Edit the PAM common file /etc/pam.d/common-account:

account     sufficient	  pam_winbind.so use_first_pass cached_login 
account     required      pam_unix.so broken_shadow

Edit the PAM common file /etc/pam.d/common-auth:

auth	[success=2 default=ignore]	pam_unix.so nullok_secure
auth	[success=1 default=ignore]	pam_winbind.so krb5_auth krb5_ccache_type=FILE cached_login try_first_pass
auth	requisite			pam_deny.so
auth	required			pam_permit.so

Edit the PAM common file /etc/pam.d/common-password:

password	requisite			pam_cracklib.so retry=3 minlen=8 difok=3
password	[success=2 default=ignore]	pam_unix.so obscure use_authtok try_first_pass sha512
password	[success=1 default=ignore]	pam_winbind.so use_authtok try_first_pass
password	requisite			pam_deny.so
password	required			pam_permit.so
password	optional			pam_gnome_keyring.so

Edit the PAM common file /etc/pam.d/common-session:

session	    required	  		pam_env.so
session     required      		pam_unix.so
session     required      		pam_winbind.so use_first_pass 
session     required      		pam_limits.so
session     required      		pam_mkhomedir.so
session     [success=1 default=ignore] 	pam_succeed_if.so service in crond quiet use_uid

Edit the PAM common file /etc/pam.d/common-session-noninteractive:

session		[default=1]		pam_permit.so
session		requisite		pam_deny.so
session		required		pam_permit.so
session		optional		pam_winbind.so cached_login
session		required		pam_unix.so

Make sure that /etc/nsswitch.conf has the winbind entries for login.

passwd:         compat winbind
group:          compat winbind
shadow:         compat

Now we’re ready to add thinserver to the Windows Domain.

kinit administrator@DOMAIN.INTERNAL
net ads join -U administrator
net ads keytab create -U administrator
/etc/init.d/smbd start
/etc/init.d/winbind start

Verify that you are on the domain and that you can see all the users and groups in the domain.

wbinfo -u
wbinfo -g
getent passwd

You should now be able to log onto the server with your domain username and password. Verify that you’re getting a Kerberos ticket.

klist

Reboot the Network Workstation and you will be provided with the login prompt, this time instead of using the local Ubuntu users you should be able to login using an AD login

12. Configuring FAT Clients

1. Disable root login on fat clients.

• To disable root login from thin clients edit the ssh_config file .
• Open the Terminal Window and enter :

sudo gedit /opt/ltsp/i386/etc/ssh/ssh_config

• Change the following if set or add to the bottom of the config file :

PermitRootLogin no

2. Copy DNS and Repository information from server to fat client to sync updates.

• To update the DNS information on the fat client image simply copy your LTSP server DNS details to the client image.
• Open the Terminal Window and enter :

sudo cp /etc/resolv.conf /opt/ltsp/i386/etc/resolv.conf

• An easy way to install software sources for fat clients is to install the repositories on the LTSP server and then copy the software sources to the fat client image.
• Open the Terminal Window and enter :

sudo cp /etc/apt/sources.list /opt/ltsp/i386/etc/apt/sources.list
sudo cp /etc/apt/sources.list.d/* /opt/ltsp/i386/etc/apt/sources.list.d/

3. Update & Upgrade fat client installation.

• For normal updates open the Terminal Window and enter :

sudo chroot /opt/ltsp/i386 apt-get update 
sudo chroot /opt/ltsp/i386 apt-get upgrade

• When done, update the client image

sudo ltsp-update-image --arch i386

• For Kernel updates do the following from the Terminal :

export LTSP_HANDLE_DAEMONS=false
sudo mount --bind /dev /opt/ltsp/i386/dev
sudo chroot /opt/ltsp/i386
mount -t proc proc /proc
apt-get update && apt-get dist-upgrade
exit
sudo ltsp-update-kernels
sudo umount /opt/ltsp/i386/proc
sudo umount /opt/ltsp/i386/dev

• When done, update the client image

sudo ltsp-update-image --arch i386

4. Install additional fat client software.

• If you have added the Google Chrome PPA’s details to your software sources, and copied these sources in step 2. you will be able to install Google-Chrome, open the Terminal Window and enter :

sudo chroot /opt/ltsp/i386 apt-get install google-chrome-stable

• To install the Flash Plugin for your thin/fat clients, open the Terminal Window and enter :

sudo chroot /opt/ltsp/i386 apt-get install flashplugin-installer

• To replace Gnome-Screensaver (Black screen only) with XScreensaver, open the Terminal Window and enter :

sudo chroot /opt/ltsp/i386 apt-get remove --purge gnome-screensaver 
sudo chroot /opt/ltsp/i386 apt-get install xscreensaver xscreensaver-gl

• When done, update the client image

sudo ltsp-update-image --arch i386

5. Autostart software on all fat clients.

• To autostart a program for all fat client users is fairly easy, simply copy the .desktop shortcut of the application to the /etc/xdg/autostart folder.
• If you want to start google-chrome and xscreensaver for all fat client users open the Terminal Window and enter :

sudo cp /opt/ltsp/i386/usr/share/applications/google-chrome.desktop /opt/ltsp/i386/etc/xdg/autostart/
sudo cp /opt/ltsp/i386/usr/share/applications/xscreensaver-properties.desktop /opt/ltsp/i386/etc/xdg/autostart/xscreensaver.desktop

• Tip: To autostart Google Chrome in full screen mode on a specific webpage, edit the new autostart google-chrome.desktop file and add –kiosk and you site URL as shown below :

[Desktop Entry]
X-AppInstall-Package=google chrome
X-AppInstall-Popcon=39584
X-AppInstall-Section=universe
Version=1.0
Name=Google Chrome
GenericName=Web Browser
Comment=Access the Internet
Exec=/opt/google/chrome/google-chrome --incognito --kiosk http://www.google.com
Terminal=false
X-MultipleArgs=false
Icon=google-chrome
Type=Application
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml_xml;x-scheme-handler/http;x-scheme-handler/https;x-scheme-handler/ftp;
X-Ayatana-Desktop-Shortcuts=NewWindow;NewIncognito

[NewWindow Shortcut Group]
Name=New Window
Exec=/opt/google/chrome/google-chrome
TargetEnvironment=Unity

[NewIncognito Shortcut Group]
Name=New Incognito Window
Exec=/opt/google/chrome/google-chrome --incognito
TargetEnvironment=Unity

• Now edit the new autostart xscreensaver file and replace “-demo” with “-nosplash” :

sudo gedit /opt/ltsp/i386/etc/xdg/autostart/xscreensaver.desktop

6. Auto login fat clients based on IP address.

• To auto login clients you need to supply the usernames and passwords for each user based on the IP address of the client machine.
• For the Terminal Window and enter :

sudo gedit /var/lib/tftpboot/ltsp/i386/lts.conf

• Replace the usernameX and passwordX with the username and password for each user  :

[Default] 
# Local Apps 
LOCAL_APPS = True 
LOCAL_APPS_MENU = True 
LOCAL_APPS_MENU_ITEMS = firefox, google-chrome 

# Network settings 
DNS_SERVER = 192.168.1.1 
LDM_DIRECTX = True 

# Theme Settings 
LDM_THEME = ubuntu 

# Restrictions 
LOCALDEV_DENY_CD = True 
LOCALDEV_DENY_USB = True 
LOCALDEV_DENY_INTERNAL_DISKS = True 

# Auto Login 
LDM_AUTOLOGIN = True 

[192.168.1.21] 
LDM_USERNAME = username1 
LDM_PASSWORD = password1

[192.168.1.22] 
LDM_USERNAME = username2 
LDM_PASSWORD = password2 

[192.168.1.23] 
LDM_USERNAME = username3 
LDM_PASSWORD = password3

[192.168.1.24] 
LDM_USERNAME = username4 
LDM_PASSWORD = password4 

[192.168.1.25] 
LDM_USERNAME = username5 
LDM_PASSWORD = password5

Post Install

Post install there may be some things you want to do some of these are covered here.

Passwordless SSH with Kerberos

One of the benefits of having a Kerberos enabled server is that you can now enable passwordless login via SSH. To make this work you need to have both your Linux workstation and server on the domain with Kerberos configured correctly.

Make these changes in the /etc/ssh/sshd_config file on thinserver:

# GSSAPI options
GSSAPIAuthentication yes
GSSAPICleanupCredentials yes
UseDNS yes

Make these changes in the /etc/ssh/ssh_config file on your Linux workstation:

GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes

Test ssh to make sure that authentication is working with Kerberos. Try to login to thinserver from your workstation.

ssh -v thinserver

If authentication with Kerberos succeeded you shouldn’t be promted for a password and you should see the “debug1: Authentication Succeeded (gssapi-with-mic) message:

debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Delegating credentials
debug1: Delegating credentials
debug1: Authentication succeeded (gssapi-with-mic).

Problems and Solutions

These are some of the other issues that I came accross. Hopefully they’ll help someone.

PROBLEM : LTSP client authenticates but logs out immediately
SOLUTION: gconftool-2 –direct –config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory –type string –set /desktop/gnome/session/required_components/windowmanager metacity

PROBLEM: You get a Pae error on your thin client on boot

SOLUTION:

change this file: ‘/usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/020-kernel-selection’. I removed 2 times ‘-pae’ in the kernel selection. Seems to install by default the pae kernel. Removing this ended with an install of non-pae kernel for the thin clients.

PROBLEM : No VNC on thin clients
SOLUTION: http://bootpolish.net/home_ltsp_installx11vnconltsp5

PROBLEM : Change the default login screen to a custom one
SOLUTION: https://help.ubuntu.com/community/EdubuntuFAQ

PROBLEM : How to setup root password on thin client
SOLUTION: https://help.ubuntu.com/community/EdubuntuFAQ

PROBLEM : No logout icon
SOLUTION: http://ubuntuforums.org/archive/index.php/t-815188.html

Sources:

• https://help.ubuntu.com/community/UbuntuLTSP/LTSPQuickInstall
  
• http://www.ltsp.org/
• http://www.thefanclub.co.za/how-to/how-create-ubuntu-1104-x64-ltsp-server-32bit-thin-clients
• http://www.howtoforge.com/how-to-set-up-and-integrate-an-ubuntu-10.04-ltspv5-server-into-a-windows-2008-active-directory-domain
• http://www.thefanclub.co.za/how-to/configure-update-auto-login-ubuntu-12-04-ltsp-fat-clients