Thinclient – Jeffrey Pine Hein https://jphein.com Just plain helpful. Wed, 04 Nov 2026 15:40:02 +0000 en-US hourly 1 https://wordpress.org/?v=7.1.5 https://jphein.com/wp-content/uploads/2020/08/jphein-logo-cropped-100x100.png Thinclient – Jeffrey Pine Hein https://jphein.com 32 32 109828812 How To Create Infinite Windows Cloud Desktops for Your Nonprofit with BoXenLinux® https://jphein.com/how-to-create-infinite-windows-cloud-desktops-with-boxenlinux/ https://jphein.com/how-to-create-infinite-windows-cloud-desktops-with-boxenlinux/#respond Thu, 08 Nov 2018 02:47:01 +0000 https://blog.jphein.com/?p=5117 Running Windows allows you to easily access proprietary closed source vertical market software. Using  an Azure Nvidia Tesla virtual machine lets you run graphic intensive programs in the cloud. For instance 2D and 3D CAD Drafting, Video, and 3D educational tools. Even 3D games! O_O Coupled with BoXenLinux, and a decent Internet connection you can dramatically reduce hardware, software, maintenance, and energy costs. While still providing many clients Windows Desktop Experiences. To find out more about BoXenLinux visit the github project page here: https://github.com/jphein/boxen

As you can see from the matrix below there are MANY ways of providing desktops to your users.

However, I think this way has many advantages for a Nonprofit. I would recommend it generally, although of course other topographies are more useful in specific situations.

Benefits for a Nonprofit

  • Green computing – Thin clients use less power than traditional workstations.
  • Reduced maintenance costs – Thin client deployment means you’re only maintaining a couple servers, instead of multiple traditional workstations. Using Azure cloud means you don’t have to maintain server hardware.
  • 100% free horizontal software – Completely free Open Source horizontal market software.
  • Discounted vertical market software – Purchase heavily discounted MS remote desktop licenses at Techsoup. Along with anything else you might need. e.g. Quickbooks, MS Office, and any other vertical market software.  https://www.techsoup.org/
  • $3500 Azure Credit, Free Office 360 – Free cloud servers, Office.
    Apply for Microsoft Nonprofit here: https://nonprofit.microsoft.com/register
  • Free Voice,Gsuite,etc.. – Free cloud Telephony, calendaring, file management, and email with custom domain.
    Apply for Google Nonprofit here: https://www.google.com/nonprofits/
  • Free hardware; Nevada County among others will donate their old computers, and peripherals to any eligible local nonprofit. Perfect for blazingly fast thin clients. Bring your tax exempt paperwork to the warehouse on the last Friday of the month. Or, try Purchasing hardware from your local government entity here: https://www.publicsurplus.com/sms/nevadacounty,ca/list/current?orgid=315996 After that try eBay: https://rover.ebay.com/rover/1/711-53200-19255-0/1?mpre=https%3A%2F%2Fwww.ebay.com%2Fb%2FPC-Desktops-All-In-One-Computers%2F179%2Fbn_661752&campid=5337848787&toolid=20008
  • No taxes – If you use Comcast as your internet provider, make sure to file tax exemption paperwork with them to waive the applicable taxes. Email tax exempt certificate to: [email protected] . Include service address & account #.
  • 50% off internet – If you are school, or other eligible nonprofit in California sign up here for 50% off your internet bill. https://jphein.com/discounted-phone-and-internet-for-nonprofits-in-california/

Terms

  • [wiki]Vertical market software[/wiki] – https://en.wikipedia.org/wiki/Vertical_market_software
  • [wiki]Thin client[/wiki] – https://en.wikipedia.org/wiki/Thin_client
  • [wiki]Linux Terminal Server Project[/wiki] (LTSP) – https://en.wikipedia.org/wiki/Linux_Terminal_Server_Project
  • [wiki]Ubuntu[/wiki] – https://en.wikipedia.org/wiki/Ubuntu
  • [wiki]Remote Desktop[/wiki]

Guide

Follow along. At the end of this guide you should be able to plug in any number of old computers without hard drives into your local network. Then have them boot blazingly fast Windows based modern software. Wireless, and remote VPN clients are also supported.

In this setup all thin clients will be sharing a single Windows 2016 Datacenter instance. However, you can provide any number of environments using this method, including huge VDI deployments. My favorite is using LTSP Ubuntu fat client desktops with RemoteApps for seamless cloud integration of necessary windows based proprietary software.

I am using Ubuntu 18.04 Bionic Beaver for the LTSP server, because LTSP does not currently work with Ubuntu 18.10 Cosmic Cuttlefish.* In my case the entire setup was virtualized in the Azure cloud using KVM Virtual Machine Manager for virtual thin clients.

It might look like this:

[Azure Standard D4s v3[[PXE thin client – KVM guest] –> [Ubuntu 18.04] LTSP Server]] –>[Azure Standard NV6 [Windows 2016]]

In real life the more likely scenario would be to install Ubuntu on a bare metal server onsite. Then, install Ubuntu 18.04 inside a KVM vm. Plug a thin client into your network, and configure it for PXE boot in BIOS. It would look a little like this:

[PXE thin client] –> [[Ubuntu 18.10] [Ubuntu 18.04 KVM guest LTSP server]] –> [Firewall] –> [Internet] –> [Azure Standard NV6 [Windows 2016]]

In this guide I will be first showing you how to set up the virtualized system, and then go into some changes you’ll need to make in the field.

Requirements

  • An internet connection. 3MB/s or more recommended.
  • A computer with keyboard and display capable of running at least SSH. To issue the commands from.
  • A computer capable of running Ubuntu with at least one network card. Or a virtual machine capable of nested virtualization like the Azure Standard D4s v3. For the LTSP server.
  • A virtual or real windows machine locally or in the cloud. You’ll need Remote desktop licenses if you want to use microphone forwarding. If using Azure, not every region has the NVIDIA Tesla servers (NV6) for hardware graphics rendering. USA South Central is what I used. This is used for the desktop environment.

IPs

  • 10.0.0.1 – Gateway.
  • 10.0.0.5 – eth0 – Local interface on Ubuntu server – Connected to the Internet.
  • 192.168.122.1 – virbr0 – Virtual bridge on Ubuntu server for testing virtual thin clients.
  • 10.0.0.4 – Windows 2016 datacenter RDP server with NV6 Nvidia Tesla hardware.

Create your Azure Virtual Machines

After signing up and being accepted to Microsoft Nonprofit, verify your $3500 credit here: https://www.microsoftazuresponsorships.com/Balance

Create your virtual machines here: https://portal.azure.com
Note: DO NO USE accelerated networking on the Ubuntu Server.

Screenshot from 2018-11-14 18-49-20

LTSP Server

  • Image type: Ubuntu 18.04
  • Size: Azure Standard D4s v3

Desktop Server

  • Image type: Windows 2016 Datacenter
  • Size: Azure Standard NV6

[jbox]Azure comes with a premade Ubuntu 18.04 image, but if you are doing this in the field you would need to install Ubuntu on your server:

Install Ubuntu 18.04.1 Desktop (Minimal)

If you decide to have a local Windows server instead or in addition to the Azure vm, you’ll need to install Windows locally.

Install Windows 2016 Datacenter

  • Download ISO from Microsoft Volume Licensing Center
  • Install

[/jbox]

Configure Windows 2016 Datacenter

Configure remote desktop for microphone redirection:

  • Install Remote Desktop Session Host
  • You’re either still inside the grace period OR have the Remote Desktop Licensing role installed and a valid CAL
  • Make sure the remote desktop group policy allows audio recording

Configure graphics acceleration: https://lg.io/2016/10/12/cloudy-gamer-playing-overwatch-on-azures-new-monster-gpu-instances.html

Configure the Ubuntu and install LTSP Server

[jbox]You can find a bash script automating all the below commands here: https://raw.githubusercontent.com/jphein/boxen/master/boxenbrain [/jbox]

To manually install BoXenLinux we will be configuring LTPS using the Chrootless Proxy mode for in the field. It is the easiest of the 4 ways to install LTSP. However, for the Azure cloud we’ll need to install using a chroot.

[jbox color=green]Set a static IP for your wired network interface in the field

Microsoft azure VM comes with the static IP set on your default interface. However, in the field you’ll need to set a static IP address.
https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/netplan-how-to-configure-static-ip-address-in-ubuntu-18-04-using-netplan.html

https://netplan.io/examples

[/jbox]

Optional: Install OpenSSH server
If using the Azure install as the LTSP server, you’ll want to overwrite the existing sshd_config so that you can using password login if you used a key when creating the VM.

sudo apt install ssh

Install LTSP and epoptes (epoptes lets you remote desktop in and help anyone using a thin client), Instructions from http://wiki.ltsp.org/wiki/Installation/Ubuntu:

sudo add-apt-repository --yes ppa:ts.sch.gr #The Greek Schools repository
sudo apt install --yes --install-recommends ltsp-server-standalone ltsp-client epoptes

Configure dnsmasq

Note: You may want to edit the /etc/dnmasq.d/ ltsp-server-dnsmasq.conf and add “dhcp-option=3,192.168.122.1” to set a different gateway, but probably not.

sudo ltsp-config dnsmasq --enable-dns
sudo service dnsmasq restart

Add yourself the epoptes group

sudo gpasswd -a ${SUDO_USER:-$USER} epoptes

Was told to remove these packages

sudo apt purge --yes --auto-remove mate-hud snapd

[jbox color=blue title=”Optional: Chroot Install”]

Build a chroot client for alternate arch, dekstop enviroment or package base

Grab freerdp’s key 

cd /etc/ltsp 
sudo wget http://pub.freerdp.com/repositories/ADD6BF6D97CE5D8D.asc
  • Option 1 – with command
sudo ltsp-build-client --purge-chroot --mount-package-cache --mirror 'http://azure.archive.ubuntu.com/ubuntu/' 
 --apt-keys '/etc/ltsp/ADD6BF6D97CE5D8D.asc, /etc/apt/trusted.gpg.d/ts_sch_gr_ubuntu_ppa.gpg' 
 --extra-mirror 'http://ppa.launchpad.net/ts.sch.gr/ppa/ubuntu bionic main, http://pub.freerdp.com/repositories/deb/bionic/ freerdp-nightly main' 
 --late-packages epoptes-client freerdp-nightly --prompt-rootpass --fatclient
  • OR, Option 2 – using my ltsp-build-client.conf
sudo wget https://github.com/jphein/boxen/raw/master/etc/ltsp/ltsp-build-client.conf
sudo ltsp-build-client --config ltsp-build-client.conf

You may want to install a new kernel like this one if the azure kernel doesn’t work with all of KVM’s input drivers:

sudo apt-get install linux-image-lowlatency

Then you have to edit the update-kernels.conf file, so that LTSP chooses that one to boot the client.

Create some symlinks so freerdp-nightly is more easy t my lazy scripting

sudo ltsp-chroot
ln -s /opt/freerdp-nightly/bin/xfreerdp /usr/bin/xfreerdp-nightly
ln -s /usr/share/ltsp/screen.d/xfreerdp /usr/share/ltsp/screen.d/xfreerdp-nightly
exit

Create GUI login screen for xfreerdp-nightly (Not updated!)

cd /opt/ltsp/amd64/usr/share/ltsp/screen.d/

sudo wget https://raw.githubusercontent.com/jphein/boxen/master/rdpgui

sudo wget https://raw.githubusercontent.com/jphein/boxen/master/xfreerdp-prompt

sudo chmod +x rdpgui xfreerdp-prompt
sudo ltsp-update-image

Note: You may get this error on Microsoft Azure VM! https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1802707 hmmmm…. This script seems to fix it:

#!/bin/bash
# tadaen sylvermane | jason gibson
# configure locales for ubuntu bionic ltsp chroot creation


for var in LC_ALL= LANG= ; do
        export "$var"en_US.UTF-8
done
ltsp-build-client --chroot "$1"

[/jbox]

[jbox color=green title=”Local Chrootless Install”]

This is the recommended, and simplest install

Install FreeRDP-nightly and client zenity GUI

sudo sh -c 'echo "deb http://pub.freerdp.com/repositories/deb/$(lsb_release -cs)/ freerdp-nightly main" >> /etc/apt/sources.list.d/freerdp-nightly.list' 
wget -O - http://pub.freerdp.com/repositories/ADD6BF6D97CE5D8D.asc | sudo apt-key add - 
sudo apt update 
sudo apt install --yes freerdp-nightly
sudo ln -s /opt/freerdp-nightly/bin/xfreerdp /usr/bin/xfreerdp-nightly
cd /usr/share/ltsp/screen.d/
sudo ln -s xfreerdp xfreerdp-nightly
sudo wget https://raw.githubusercontent.com/jphein/boxen/master/usr/share/ltsp/screen.d/rdpgui 
sudo wget https://raw.githubusercontent.com/jphein/boxen/master/usr/share/ltsp/screen.d/xfreerdp-prompt 
sudo wget https://raw.githubusercontent.com/jphein/boxen/master/usr/share/ltsp/screen.d/launch
sudo mkdir boxen  
cd boxen
sudo wget https://raw.githubusercontent.com/jphein/boxen/master/usr/share/ltsp/screen.d/boxen/welcome 
cd ..
sudo ln -s launch welcome
sudo ln -s /sbin/shutdown shutdown
sudo chmod +x rdpgui xfreerdp-prompt launch boxen/welcome

Create LTSP client NBD image using the chrootless method of the servers root /

You need to run this any time you make changes to your filesystem you want to be updated in your LTSP client.

sudo ltsp-update-image --cleanup /

[/jbox]

Grab the lts.conf for our thin clients

cd /var/lib/tftpboot/ltsp/amd64/
sudo wget https://raw.githubusercontent.com/jphein/boxen/master/var/lib/tftpboot/amd64/lts.conf

Edit lts.conf to suit your needs

nano -w lts.conf

Test with KVM virtual pxe thin client

If you are already using KVM to install Ubuntu in a VM then you don’t need to install it again. However, if you are using a real bare metal server then you’ll need to run the install command.

sudo apt install virt-manager

[jbox]Libvirtd will run dnsmasq on virbr0 by default. We need to kill that instance and restart the global dnsmasq with our LTSP configs. You will need to killall and restart dnsmasq every time you reboot.

###dnsmasq hack for testing
sudo mv /etc/dnsmasq.d/libvirt-daemon /root/
sudo sh -c 'echo "dhcp-range=192.168.122.20,192.168.122.250,8h" >> /etc/dnsmasq.d/ltsp-server-dnsmasq.conf
#These steps will need to performed again if you reboot
sudo killall dnsmasq
sudo service dnsmasq restart

[/jbox]

#Create the PXE test KVM client
sudo virt-install 
  --name pxe 
  --memory 4096 
  --vcpus 2 
  --disk none 
  --pxe 
  --os-variant ubuntu17.10 
  --wait 0

Connect locally using very nice spice

virt-viewer --connect qemu:///system pxe

Connect remotely using spice

virt-viewer --connect qemu+ssh://[email protected]/system pxe

PXE boot menu in Virt Viewer: Welcome to BoXenLinux, type brain, baby or hdScreenshot from 2018-11-11 23-58-02


Screenshot from 2018-11-14 21-30-44 Screenshot from 2018-11-14 21-33-48 Screenshot from 2018-11-14 21-34-11 Screenshot from 2018-11-14 21-41-25 Tada!!!

See also

lts.conf manpage ltsp-build-client manpage ltsp-update-image manpage ltsp-config manpage ltsp-chroot manpage http://wiki.ltsp.org/wiki/Installation/Ubuntu https://help.ubuntu.com/community/HowToSetupLTSPDevelEnvironment https://github.com/wyllianbs/xfreerdp-gui https://unix.stackexchange.com/questions/119880/make-freerdp-prompt-user-for-username-and-password/187370 http://www.saminiir.com/debugging-pxe-boot/

* Ubuntu 18.10 I previously tried this with Ubuntu 18.10 Cosmic Cuttlefish, and ran into some issues. Mainly the maintainer of LTSP for Ubuntu does not fix anything that is not a LTS release.

Optional Install ltsp-manager


sudo add-apt-repository --yes ppa:franz-die/ltsp-manager; apt update

sudo apt install ltsp-manager

Optional: Install X2Go remote desktop software

sudo add-apt-repository ppa:x2go/stable
sudo apt-get update
sudo apt-get install x2goserver x2goserver-xsessions x2gomatebindings

Optional: Install Ubiquity to install Ubuntu on PXE booted clients or servers

sudo apt-get install ubiquity ubiquity-frontend-gtk

Running it is a manner of running from the client

ubiquity gtk_ui

Optional: Add iPXE to grub menu

apt install grub-ipxe

[jbox]Optional: Set up Firewall with IP Masquerading 

Probably won’t need to do this.

First, packet forwarding needs to be enabled in ufw. Two configuration files will need to be adjusted, in /etc/default/ufw change the DEFAULT_FORWARD_POLICY to “ACCEPT”:

sudo nano -w /etc/default/ufw #change DEFAULT_FORWARD_POLICY="ACCEPT"

Then edit /etc/ufw/sysctl.conf,

sudo nano -w /etc/ufw/sysctl.conf

and uncomment:

net/ipv4/ip_forward=1
net/ipv6/conf/default/forwarding=1

Now add rules to the /etc/ufw/before.rules file. The default rules only configure the filter table, and to enable masquerading the nat table will need to be configured. Add the following to the top of the file just after the header comments:

sudo nano /etc/ufw/before.rules
# nat Table rules
*nat
:POSTROUTING ACCEPT [0:0]

# Forward traffic from eth1 through eth0.
-A POSTROUTING -s 192.168.122.0/24 -o eth0 -j MASQUERADE

# don’t delete the ‘COMMIT’ line or these nat table rules won’t be processed
COMMIT

Allow SSH

sudo ufw allow 22
sudo ufw allow from 192.168.122.0/24 
sudo ufw enable

[jbox]

Optional: Install apt-cacher

apt-cacher will cache packages so you don’t waste your time downloading them again again.

sudo apt install apt-cacher
sudo nano /etc/apt-cacher/apt-cacher.conf #Uncomment allowed_hosts= *
sudo ufw allow 3142/tcp
sudo sh -c 'echo "Acquire::http::Proxy "http://10.0.0.5:3142"";' > /etc/apt/apt.conf.d/01proxy
sudo /usr/share/apt-cacher/apt-cacher-import.pl -l /var/cache/apt/archives
sudo service apt-cacher restart

Optional: Test with QEMU

Set up virtual bridge for client networking

On the azure VM I was able to use the default virtual bridge virbr0. Just commented out the dnsmasq.d/ file libvirt that prevented dnsmasq from serving IPs on that network. However, testing on a real server I needed to make my own bridge. These commands should not be issued if working on your server remotely. Only a local bare metal install should issue these commands.

sudo ip tuntap add dev virttap mode tap user $USER
sudo brctl addbr virtbr
sudo brctl addif virtbr eth0 # your LAN interface
sudo brctl addif virtbr virttap
sudo ip link set virtbr up
sudo ip link set eth0 up
sudo ip link set virttap up
dhclient virtbr

You may need to restart dnsmasq again

sudo service dnsmasq restart

Run QEMU to test your LTSP setup

cd
qemu-img create -f vmdk testpxe.vmdk 10
/usr/bin/qemu-system-x86_64 -m 1024 -hda testpxe.vmdk 
                              -boot n 
                              -option-rom /usr/share/qemu/pxe-rtl8139.rom 
                              -net nic 
                              -net tap,ifname=virttap,script=no,downscript=no

 

]]>
https://jphein.com/how-to-create-infinite-windows-cloud-desktops-with-boxenlinux/feed/ 0 5117
HP T620 VS Dell Wyse V10D Thinclient and the HP Elite 8000 ultra-slim https://jphein.com/hp-t620-vs-dell-wyse-v10d-thinclient/ https://jphein.com/hp-t620-vs-dell-wyse-v10d-thinclient/#respond Wed, 25 May 2016 04:06:07 +0000 https://blog.jphein.com/?p=3805

20x Dell Wyse Z10D Dual core 1.65GHz 2GB
http://www.arcy.com/wyz1re2gwt90.html$180/per Free shipping


20x HP T620 4GB, Quad core 1.5GHz
https://www.nautilusnet.com$190/per + $190 s/h


20x HP Elite 8000 Ultra slim Dual 3GHz 4GB
http://www.newegg.com/Product/Product.aspx?Item=9SIA5YV20K0343
$150/per + Free shipping

]]>
https://jphein.com/hp-t620-vs-dell-wyse-v10d-thinclient/feed/ 0 3805
Windows 10 VDI deployment: Architecture and Taxonomy https://jphein.com/boxenlinux-architecture-and-taxonomy/ https://jphein.com/boxenlinux-architecture-and-taxonomy/#respond Mon, 23 May 2016 19:53:53 +0000 https://blog.jphein.com/?p=3793  

Virtual server mirror. Serving Windows 10 pro desktops to 20x thin clients.


Mirror

Server: 2x Dell r710 12 cores @ 3GHz, 64GB RAM, w/ Intel 2x 10GBE port and dual 850W Power
Storage per server: 2x300GB SSD, 4x146GB SAS 15K, 2x1TB SAS 7.2K
Software: M$ Windows 2012r2 Datacenter or Ubuntu Linux 16.04


Architecture:

  
                           ~20x Clients
                                 |
                                 |
                            1GB/s speed
                                 |
                        --------------------
                        |      24 port     |
            ------------|    1GB Switch    |-----------
            |           |                  |          |
            |           --------------------          |
            |                                         |
            |                                         |
            |                                         |
            |                                         |
  1GB Network Card 1 (eth0)                 1GB Network Card 1 (eth0)
            |                                         |
  --------------------                      --------------------
  |                  |                      |                  |
  |     Server 1     |                      |     Server 2     |
  |                  |                      |                  |
  --------------------                      --------------------
            |                                         |
  10GB Network Card 2 (eth1)                10GB Network Card 2 (eth1)
            |                                         |
            |                                         |
            |          Direct 10Gb/s Ethernet         |
            -------------------------------------------

Virtual Machines

Per physical server:

  • 1x Windows 2012R2 Domain Controller
  • 1x Windows 2012R2 Application server
  • 1x Bitdefender Appliance
  • 20x Windows 10 Professional (Virtual snapshots)

Required storage space:
+500GB 20x Win10 VMS x 25GB (Much less usually because we will be using virtual snapshots)
+200GB 2x Win2012R2 x 100GB
+100GB Bitdefender virtual machine
+100GB User data
+100GB Main install
= 1TB (Available 1.88TB)


RAID per server

[Fast] 300GB RAID1 – 2x300GB SSD for application server vm,  and bitdefender vm.

[Medium] 392GB RAID10 – 146GBx4 15K for 20x Windows 10 virtual machines, and domain controller vm.

[Slow] 1TB RAID1 – 2x 1TB 7.2K  for backup and share data

8GB USB thumb drive for OS

Filesystem: ZFS


Network

LAN Subnet = 10.x.x.xxx

I like to isolate
Static to 100-199(Servers 100-129, Workstations 130-179,
Printer DHCP to 200-239,
and keep 001 as the gateway, 002-099 and 240-254 for utility. ~Doug

Subnet Mask: 255.255.255.0
Gateway: 10.0.0.1

10.0.0.111 DNS-1 – DVVMWS01 (DC)
10.0.0.112 DNS-2 – DVVMWS02 (DC)
10.0.0.100 – DVRMLS01 – Host of VM’s
10.0.0.101 – DVRMLS02 – Host of VM’s
10.0.0.131-146 – 16 – DVVMWW01-16

Layout:

InternetA  --> Firewall --> Server 1 --> Switch --> Clients
InternetB  -->          --> Server 2            

Server 1 and 2 are directly connected with 10GB connection.
Every other connection is 1GB.
Spare firewall, switch, and thinclients on hand.

Taxonomy

1. First 2 characters for the Company,

2. Next two for Machine Type = Virtual Machine or RM for Real Machine

3. Next two Workstation or Server – WS = Windows Server, WW = Windows Workstation, LS = Linux Server, LW = Linux Workstation.

4. The last 2 = nn = number.

5. Example = DVRMLS01 = Domain Vacations, Real Machine, Linux Server, 01

~Doug


Thinclients

20x HP G4U40UA Flexible Thin CLient T620 AMD GX-415GA 1.5GHz 4GB 8GB SSD ThinPro

]]>
https://jphein.com/boxenlinux-architecture-and-taxonomy/feed/ 0 3793
Wireless thin client using Ubuntu 18.04.1 named BoXenbaby https://jphein.com/boxenbaby/ https://jphein.com/boxenbaby/#respond Sun, 15 May 2016 06:18:13 +0000 https://blog.jphein.com/?p=3627 UPDATE: BoXenbaby is simply Ubuntu 18.04.1 Desktop minimal install with OpenVPN,  FreeRDP-nightly, and other modern clients.

This document describes how to:

Automatic Install
Part 1 – PXE
Install BoXenbaby to a computer plugged into a BoXenbrain network.

Manual Install
Part 2 – USB
Install BoXenbaby with a USB drive.
Download the usb image here:

Check out BoXenLinux here: https://github.com/jphein/boxen

Goal: Make a tiny (< 50MB) thinclient OS that can be loaded by iPXE over LAN, WIFI, or WAN using HTTP and HTTPS. I should load completely into RAM. It should be able to support these client applications/protocols: RDP, VNC, SSH, SPICE, X2Go. It should also have a web browser kiosk mode (Google Chrome).

My project is to have a wireless PC using a 1MB iSCSI image on usb flash, booting into  Ubuntu 16.04 desktop, Windows 10 pro desktop, and MacOSX 10.11 desktop KVM virtual machines using the KVM-VDI project with virtual snapshots enabled.

Custom iPXE image made with rom-o-matic,
https://www.rom-o-matic.eu/
pointing to my fork of the boot.rackspace.com iPXE LiveCD project.
https://github.com/rackerlabs/boot.rackspace.com
New project is netboot.xyz
Good list of alternatives: http://www.rmprepusb.com/tutorials/ipxe

I want to use Thinstation as the running in RAM OS that iPXE boots. Not sure if x2go is supported in thinstation yet. Then by using the thinstation.conf create a remote-viewer Session wrapped by KVM-VDI script.

Here is someone who was able to iPXE boot thinstation:?
http://thinstation.4464.n7.nabble.com/OT-ipxe-chainloading-td24153.html
Here is a way to netboot a liveCD from iPXE:

iPXE Network booting for ISO images


Good iPXE guide: http://www.denverslair.co.uk/tech/iPXE.php

Procedure for running windows 10 or 2012r2 over lan with iPXE and iSCSI:
https://www.computeraudiophile.com/forums/topic/26705-diskless-windows-10-pc-setup-procedure/

Wireless iPxe: https://www.coreboot.org/IPXE

Not so hard, right?

It already supports integration with LTSP for wired zeroclients over PXE and thinclients over iPXE. LTSP, also offers thinclient and fatclient modes for shared Remote desktop if you don’t have the resources to offer a Virtual machine pool. Thinstation can also be a thinclient for shared or virtual machine resources.

I currently use Ubuntu LTSP with xfreerdp and I custom login script. That only supports wired zero clients. Wireless or WAN clients boot from a CD, USB, Hard drive or SD card.

Thinstation is needed for Wifi or WAN links, with iPXE downloading the image from the internet or local cache. Otherwise plain PXE works great!

X2Go is used if I want to offer shared Ubuntu desktops over WAN. FreeRDP for shared or virtual Windows desktop over WAN. RemoteAPPs for seamless desktop. VNC for shared MacOS over WAN. (or slow Wifi) SSH for admin. Spice for VDI with KVM. Chrome for web browsing and remoteapps.

Here is an amazing guide for thinstation and RDP over PXE :
https://hinchley.net/articles/use-thinstation-to-build-a-network-bootable-rdp-enabled-thin-client-image/

I am sooo close. I’ll I need is to able install and run remote-viewer, and x2goclient on thinstation, and have it remastered.

Here are the Thinstation Issue tickets for adding x2go and spice:
https://github.com/Thinstation/thinstation/issues/106
https://github.com/Thinstation/thinstation/issues/141

Here are some guides on how to do this with alternatives:

http://hinchley.net/2016/01/17/use-thinstation-to-build-a-network-bootable-rdp-enabled-thin-client-image/

https://github.com/Thinstation/thinstation/wiki/Getting-Started-with-Thinstation

[Outdated] http://tsomatic.agarwal-associates.com/index.php <– seems to be outdated.

Or

[DEFUNCT] LPS https://en.wikipedia.org/wiki/Lightweight_Portable_Security

Or,

[jbox color=green]make my own with lubuntu:

https://wiki.ubuntuusers.de/LiveCD_manuell_remastern/

http://pinguyos.com/2015/09/pinguy-builder-an-app-to-backupremix-buntu/

[/jbox]Couldn’t get Tinycore to work

TinyCore Linux

  1. Make custom version of TinyCore Linux with extensions embedded. http://forum.tinycorelinux.net/index.php?topic=17423.0
    1. You can make Pure64 version with FreeRDP
    2. An i386 version can be made with TigerVNC
  2. Host custom image on public or private server
  3. Make custom iPXE image here: https://rom-o-matic.eu/
    This should call the hosted iPXE script below.
  4. Copy and host iPXE script from: http://boot.rackspace.com
]]>
https://jphein.com/boxenbaby/feed/ 0 3627
KVM-VDI Session Screen Script for LTSP thin clients running under Ubuntu 16.04 xenial https://jphein.com/kvm-vdi-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu-16-04-xenial/ https://jphein.com/kvm-vdi-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu-16-04-xenial/#respond Fri, 13 May 2016 18:11:37 +0000 https://blog.jphein.com/?p=3598 Sweet new open source project: https://github.com/Seitanas/kvm-vdi

It is required to run the installation readme above to use KVM-VDI.

KVM-VDI does not come with a built in LTSP (client) script. So, I created one.
This is useful if you want your thinclients to be able to remote into a KVM-VDI, and want full control using lts.conf.

Run the following on your Ubuntu LTSP server, this will install packages you’ll need on the thinclient: (Replace <base> with whatever you used for ltsp-build-client –chroot <base>)

ltsp-chroot --arch <base> -m
apt-get xdotool x11-utils xwit python python-requests virt-viewer freerdp-x11 pulseaudio xinit
exit

[jbox]NOTE: You can also add this to the build client config file so that any time you upgrade or build your client image it automatically installs it. –> /etc/ltsp/ltsp-build-client.conf

Here is an example: ltsp-build-client.conf

[/jbox]
The /var/lib/tftpboot/ltsp/<base>/lts.conf options are:

#KVM-VDI Remote Desktop to Virtual Machine
SCREEN_07 = vdi

Here is an example: lts.conf

Put the below screen script into: vdi <– Right click and “Save link as”
/opt/ltsp/<base>/usr/share/ltsp/screen.d/
IMPORTANT: Be sure to name it “vdi“

The last step is to run

ltsp-update-image <base>

LTSP comes with these screen scripts by default:

kiosk ldm menu rdesktop shell ssh startx telnet xdmcp xfreerdp xterm

I created a VNC session script here, and a SPICE session script here.

(ldm is enabled on VT_07 by default)

 

]]>
https://jphein.com/kvm-vdi-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu-16-04-xenial/feed/ 0 3598
Spice Session Screen Script for LTSP thin clients running under Ubuntu https://jphein.com/spice-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/ https://jphein.com/spice-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/#comments Thu, 12 May 2016 00:55:27 +0000 https://blog.jphein.com/?p=3569 LTSP does not come with a built in Spice (client) script. So, I created one.
This is useful if you want your thinclients to be able to remote into a KVM VDI.

I use the virt-viewer package. Run the following on your Ubuntu LTSP server:

ltsp-chroot --arch <base> -m
apt-get install virt-viewer
exit

NOTE: You can also add this to the build client config file so that any time you upgrade or build your client image it automatically installs it. –> /etc/ltsp/ltsp-build-client.conf

The /var/lib/tftpboot/ltsp/<base>/lts.conf options are:

#Spice KVM Remote Desktop to Virtual Machine
SPICE_SERVER = "192.168.11.5"
SPICE_OPTIONS = "--kiosk-quit=on-disconnect --kiosk"
SCREEN_07 = remote-viewer

Put the below screen script goes into
/opt/ltsp/<base>/usr/share/ltsp/screen.d/
IMPORTANT: Be sure to name it “remote-viewer“

remote-viewer <– Right click and “Save link as”

The last step is to run

ltsp-update-image <base>

LTSP comes with these screen scripts by default:

kiosk ldm menu rdesktop shell ssh startx telnet xdmcp xfreerdp xterm

I created a vnc session script here

(ldm is enabled on VT_07 by default)

I use the menu screen script on VT_07 so that it gives me the option of what desktop to log into. My lts.conf looks like this: (lts.conf default location is: /var/lib/tftpboot/ltsp/i386/ or /amd64/ you may have to create it)

[default]
SCREEN_07 = menu

#RDP Windows Remote Desktop
RDP_SERVER = "/v:192.168.56.25"
RDP_OPTIONS = "/u:client /p:password /sound /microphone /multimedia /rfx /cert-ignore /drives /f"	
VNC_SERVER = 192.168.56.5
VNC_OPTIONS = "-fullscreen -autopass"
VNC_PASSWORD = "password"
SPICE_SERVER = "192.168.56.1"
SPICE_OPTIONS = "--kiosk-quit=on-disconnect --kiosk"

MENU_ITEM_01="Ubuntu 16.04 LTSP"
MENU_COMMAND_01="ldm"
MENU_ITEM_02="Windows 10 Professional"
MENU_COMMAND_02="xfreerdp"
MENU_ITEM_03="MacOS 10.11"
MENU_COMMAND_03="vncviewer"
MENU_ITEM_04="Android 5.5"
MENU_COMMAND_04="vncviewer 192.168.56.6"
MENU_ITEM_05="KVM Virtual Machine (Linux,MacOS,Windows)"
MENU_COMMAND_05="remote-viewer"
MENU_TITLE="Please choose a desktop: "

LDM_DIRECTX = True

As you can see this gives the thinclient to terminal into Linux, Windows, MacOS, or Android. Either shared, or personal virtual machines. o_o

You can view how to enable remote desktop in MacOS here:

https://help.ubuntu.com/community/AppleRemoteDesktop

]]>
https://jphein.com/spice-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/feed/ 2 3569
3 Free Linux based thin client distributions (Thinclient OS) [FREE] https://jphein.com/3-free-linux-based-thin-client-distributions-thinclient-os-free/ https://jphein.com/3-free-linux-based-thin-client-distributions-thinclient-os-free/#respond Thu, 05 May 2016 05:00:48 +0000 https://blog.jphein.com/?p=3476 Thinstation

X2OS

iPXE (you can use this to chain load other thin OS’s over the internet, nfs, smb, etc..)

Very small, and configurable. Supports some wireless cards.

Basically a zero client. < 1MB.

 

Ubuntu LTSP! Zero clients that boot over PXE (Thinclient or fatclient options)

 

Windows XP, Vista, 7, 8, embedded, CE, etc…

If you already have a windows device, you can convert it into a thinclient using:

thinwin

 

Commercial options

Wyse ThinOS

 

These two support SPICE! For VDI deployment to KVM-QEMU

http://www.jieyung.com/en/product.asp?wid=195

https://www.igel.com/us/products/igel-linux-thin-clients.html

http://edocs.igel.com/manuals/pdf/en_udlx_v5.pdf

 

nComputing

VDI Blaster http://www.devonit.com/thin-client-solutions/vdi-blaster

]]>
https://jphein.com/3-free-linux-based-thin-client-distributions-thinclient-os-free/feed/ 0 3476
iPXE thinclients over wireless or wan https://jphein.com/ipxe-thinclients-over-wireless-or-wan/ https://jphein.com/ipxe-thinclients-over-wireless-or-wan/#respond Wed, 04 May 2016 05:31:15 +0000 https://blog.jphein.com/?p=3458 Boot URL:
http://boot.ipxe.org/demo/boot.php

Tutorial:
http://www.rmprepusb.com/tutorials/ipxe

Script:
http://ipxe.org/scripting

Create bootable iPXE images with automated scripts:
https://www.rom-o-matic.eu/

Example:
https://gist.github.com/robinsmidsrod/2234639

]]>
https://jphein.com/ipxe-thinclients-over-wireless-or-wan/feed/ 0 3458
Least expensive thinclient or fatclient for LTSP or Edubuntu 16.04 Xenial https://jphein.com/least-expensive-thinclient-or-fatclient-for-ltsp-or-edubuntu-16-04-xenial/ https://jphein.com/least-expensive-thinclient-or-fatclient-for-ltsp-or-edubuntu-16-04-xenial/#respond Sat, 23 Apr 2016 08:29:48 +0000 https://blog.jphein.com/?p=3254

]]>
https://jphein.com/least-expensive-thinclient-or-fatclient-for-ltsp-or-edubuntu-16-04-xenial/feed/ 0 3254
Using LTSP on Ubuntu 15.10 wily [Solved] https://jphein.com/using-ltsp-on-ubuntu-15-10-wily-solved/ Tue, 22 Mar 2016 20:40:05 +0000 https://blog.jphein.com/?p=2842 LTSP does not work out of the box on Ubuntu 15.10 wily with –arch AMD64 or i386 & thinclient or fatclient. You will get this error:

chroot: can’t execute ‘/usr/bin/test’: Exec format error
overlayfs: missing ‘workdir’
mount: mounting overlayfs on /root failed: Invalid argument
mount: mounting /dev/ on /root/dev/failed: No such file or directory
No init found. Try passing init= bootarg.

Here is a link to a chatroom where someone with this problem get’s to talk with the author of the patch:

http://irclogs.ltsp.org/?d=2015-06-08

Bug report: https://bugs.launchpad.net/ltsp/+bug/1555168, https://bugs.launchpad.net/ltsp/+bug/1506756

There are two options to fixing it:

  1. Manually Patch

  1. Patch it your self with this patch: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2639
    1. sudo ltsp-chroot -b <base>
    2. cd /usr/share/initramfs-tools/
    3. edit hooks/ltsp and scripts/init-bottom/ltsp
    4. exit
  2. After you do that you have to get the chroot to rebuild it initramfs. You can do this by issuing these commands:
    1. Supposedly this works:
      1. sudo ltsp-chroot -b <base> /usr/share/ltsp/update-kernels; sudo ltsp-update-kernels
    2. I had to issue these commands instead
      1. sudo ltsp-chroot -b <base>
        update-initramfs -u
      2. exit
  3. Optional: Rebuild image and restart nbd server (This will disconnect existing clients)
    1. ltsp-update-image
    2. service nbd-server restart

OR

2. Install Greek schools PPA


Use the Greek schools PPA both on the server and in the chroot

add-apt-repository ppa:ts.sch.gr
apt-get update
apt-get dist-upgrade
ltsp-chroot -m
apt-get install software-properties-common
add-apt-repository ppa:ts.sch.gr
apt-get update
apt-get dist-upgrade
exit
ltsp-update-image
service nbd-server restart

]]>
2842
VNC Session Screen Script for LTSP thin clients running under Ubuntu https://jphein.com/vnc-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/ https://jphein.com/vnc-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/#respond Mon, 07 Mar 2016 06:29:28 +0000 https://blog.jphein.com/?p=2816 LTSP does not come with a built in VNC viewer (client) script. So, I created one.
This is useful if you want your thinclients to be able to remote into MacOS or Android OS’s.

I use the xtightvncviewer package. Run the following on your Ubuntu LTSP server:

ltsp-chroot
apt-get install xtightvncviwer
update-alternatives –config vncviewer #You may need to run this if there is another vncviewer installed in the chroot
exit

NOTE: You can also add this to the build client config file so that any time you upgrade or build your client image it automatically installs it.

The lts.conf options are:

VNC_SERVER = 192.168.1.1
VNC_OPTIONS = “-fullscreen -autopass”
VNC_PASSWORD = “password”

Put the below screen script goes into /opt/ltsp/amd64/usr/share/ltsp/screen.d/
IMPORTANT: Be sure to name it “vncviewer”

vncviewer <– Right click and “Save link as”

The last step is to run

ltsp-update-image

LTSP comes with these screen scripts by default:

kiosk ldm menu rdesktop shell ssh startx telnet xdmcp xfreerdp xterm

(ldm is enabled on VT_07 by default)

I use the menu screen script on VT_07 so that it gives me the option of what desktop to log into. My lts.conf looks like this: (lts.conf default location is: /var/lib/tftpboot/ltsp/i386/ or /amd64/ you may have to create it)

[default]
SCREEN_07 = menu

RDP_SERVER = 192.168.56.25
RDP_OPTIONS = “-a 16 -f -r disk:Drives=/media/root -r sound:local”
VNC_SERVER = 192.168.56.5
VNC_OPTIONS = “-fullscreen -autopass”
VNC_PASSWORD = “password”

MENU_ITEM_01=”Ubuntu 15.10″
MENU_COMMAND_01=”ldm”
MENU_ITEM_02=”Windows 7″
MENU_COMMAND_02=”xfreerdp”
MENU_ITEM_03=”MacOS 10.5.5″
MENU_COMMAND_03=”vncviewer”
MENU_ITEM_04=”Android 5.5″
MENU_COMMAND_04=”vncviewer 192.168.56.6″
MENU_TITLE=”Please choose a desktop: ”

LDM_DIRECTX = True

As you can see this gives the thinclient to terminal into Ubuntu Linux, Windows 7, MacOS, or Android. o_o

You can view how to enable remote desktop in MacOS here: https://help.ubuntu.com/community/AppleRemoteDesktop

]]>
https://jphein.com/vnc-session-screen-script-for-ltsp-thin-clients-running-under-ubuntu/feed/ 0 2816