- Pacote de e-mail
- apt-get install mailutils
Using Ubuntu without a linux DHCP server
Install Ubuntu Feisty
Do system updates by Terminal or update icon
sudo apt-get update
sudo apt-get install upgrade
Reboot
Install the following using Terminal or the GUI Synaptic Package Manager:
Apt-get install ltsp-server thin-client-manager-gnome openssh-server
If you want local drive support such as cdrom/floppy/etc on the thinclient, Install ltspfs and add the user to the fuse group
Install LTSP thin Client
Sudo ltsp-build-client
Source for client build:
https://help.ubuntu.com/community/ThinClientHowto
To reduce network bandwidth used by X11 all traffic is tunneled through ssh, this proves remarkebly effective compared to NX compression. In order for the LTSP clients to access the server the server needs to have its IP address configured and available for SSH. Edit /etc/hosts and if you have a host line 127.0.1.1 change to the LTSP server IP address.
172.16.25.1 Demo
If you changed the hosts file you will also need to update the LTSP client with the new ssh keys, these are encryption keys used to verify the remote host of a ssh connection is who it is supposed to be, i.e. not another host with the same IP address.
$ sudo ltsp-update-sshkeys
Source:
http://developer.novell.com/wiki/ind...eKow_on_Ubuntu
Update LTSP Client Sources.list
Add sources from /etc/apt/sources.list to /opt/ltsp/i386/etc/apt/sources.list
Open a Terminal and type: sudo cp /etc/apt/sources.list /opt/ltsp/i386/etc/apt
Or sudo gedit
Edit source list on the ltsp client (/opt/ltsp/i386/etc/apt/sources.list) and add local machine sources.list (/etc/apt/sources.list) to the ltsp sources.list
Install x11vnc on ltsp client
Sudo chroot /opt/ltsp/i386
Apt-get update
Sudo apt-get upgrade
Sudo apt-get install x11vnc
exit
Edit /opt/ltsp/i386/etc/rc.local
Sudo gedit /opt/ltsp/i386/etc/rc.local
Add the following line before the exit 0 statement in this file and save it:
x11vnc -display :6 -forever -loop &
Ensure rc.local gets executed:
Sudo chroot
cd /etc/rc2.d
mv K99rc.local S99rc.local
exit
Source:
https://wiki.edubuntu.org/InstallX11VncOnLtspClients
Set up SSH for remote Admin
(This allows you to remote reboot your Thin Client)
As the current user logon using Sudo do the following
# SSH needs /dev/random and proc interface, so mount them
mount --bind /dev /opt/ltsp/i386/dev
mount -t proc none /opt/ltsp/i386/proc
# Make sure that resolv will work iin chroot
cp /etc/resolv.conf /opt/ltsp/i386/etc/
Now chroot the /opt/ltsp/i386
chroot /opt/ltsp/i386
# Install ssh server
apt-get install ssh
# Enable root user by setting a password
passwd root
It's also possible to install your public key in $CHROOT/root/.ssh/authorized_keys to connect to the terminal without using the root password.
Source:
https://help.ubuntu.com/community/Ho...velEnvironment
Give Root Logon Access
Sudo chroot /opt/ltsp/i386
Passwd
Run tftpd as a Daemon
sudo gedit /etc/default/tftpd-hpa
change the line that says
RUN_DAEMON=”no” to
RUN_DAEMON=”yes”
Once the LTSP server is online on the correct network do the following in a Terminal.
Sudo ltsp-update-sshkeys
Configure Client to get Hostname from the DHCP server
Edit /opt/ltsp/i386/etc/hostname
Delete the entry so nothing is written
Save
Configure LTSP Clients optional at this point
The configuration file /opt/ltsp/i386/etc/lts.conf can contain a list of X11 and LTSP configuration options that can be specified for individual or groups of machines. It can include X11 servers, mice, keyboards, attached devices, etc. A detailed list of the valid options can be found in /opt/ltsp/i386/usr/share/doc/ltsp-client/examples/lts-parameters.txt.gz including an example lts.conf.
[Default]
# LTSP server IP address
#SERVER = server
SERVER = 10.30.2.20
## Network syslog
#SYSLOG_HOST = server
## X11 driver, e.g. auto, vesa, i810
#XSERVER = auto
#X_COLOR_DEPTH = ""
X_COLOR_DEPTH = 16
#X_VIDEO_RAM = ""
#XF86CONFIG_FILE = ""
## Keyboard configuration
#XKBLAYOUT = us
#XKMODEL = pc105
#XKBRULES = xorg
#XKBOPTIONS = lv3:ralt_switch
#XKBVARIANT = ""
#CONSOLE_KEYMAP = ""
## Mouse configuration
#X_MOUSE_DEVICE = /dev/input/mice
#X_MOUSE_PROTOCOL = auto
#X_MOUSE_EMULATE3BTN = True
## X11 font server
#USE_XFS = False
#XFS_SERVER = server
## SSH compression between LTSP client and server
#NETWORK_COMPRESSION = False
## Network swap device for clients < 48 MB system memory
#NBD_SWAP = ""
#SWAP_SERVER = server
#NBD_PORT = 9572
#USE_LOCAL_SWAP = False
## Local media device support
#LOCALDEV = False
## Local printers
#PRINTER_0_DEVICE = ""
## Sound configuration
#SOUND = False
#SOUND_DAEMON = esd
## Terminal sessions
#SCREEN_07 = ldm
## Linux modules
#MODULE_01 = ""
## Custom startup scripts
#RCFILE_01 = ""
#LDM_REMOTECMD = ""
The configuration file can use "True" or "False", try not to be confused as regular LTSP 4.2 prefers "Y" and "N".
Windows 2003 DHCP set up
This page describes the steps needed to setup a windows DHCP server in order to run the LTSP Ubuntu
The Ubuntu default install of LTSP assumes that you are going to use the built in DHCP server to assign ip addresses to your clients. In many establishments this is not the desired method for implementation as there is most likely an existing DHCP server. The following steps detail how to make specific machines boot from the LTSP server, but utilise a windows DHCP server for the ip assignment.
This guide assumes you already have a running windows DHCP server and that you are specifying certain machines to boot from the LTSP server, ie. the majority of your machines are still running as they normally would.
You will need to obtain the MAC address of each machine that requires to be bootable on the LTSP server. This can be achieved by asking the specified machine to try to boot from LAN. A DHCP message will appear, similar to the following
CLIENT MAC ADDR: 00 0C 29 76 88 21 GUID: 234D234D-B4CC-6CEF-0EBD554566345
Login to your windows server and load the DHCP configuration screen
Create a DHCP reservation for the MAC address you obtained
Add the configuration options below to enable the machine to boot from the LTSP server
017 Root Path: /opt/ltsp/i386
066 Boot Server Host Name: <ip address>
067 Bootfile Name: ltsp/i386/pxelinux.0
012 HostName: enter the workstation name.
Note: If your thin client is not working, replace the NIC with a different model. Even if the thin client worked on a pure LTSP with integrated DHCP, it does not mean it will work with the Windows 2003 DHCP forwarding the pxe boot.
Source:
https://help.ubuntu.com/community/Ub...TSPWindowsDHCP
VMWare Desktop 6 Thin Client
Install Guest OS as the VM user
Create a directory in the / called Vmware
Ensure the correct permissions are set for the folder and files once the VM is completed
Go to System -> Administration->Users and Groups
Click Manage Groups
Add vmusers
Add the user for the vmware machines to the vmusers group
Do what ever you need, the above is/was the setup I was going to implement. You may be beter off just doing everything in default.
Add .xsession to the users home directory with a path to the virtual machine.
A little explanation on this...
What this does is, when the user logs on it will automatically start a vmware session. I found that Vmware workstation 6 works best so far. You can set it up so the thin-client boots with window or what ever os full screen. You can also make it look transparent to the end usre so it looks like the thin-client is using a plain old windows machine. Auto logo on and so on. The other cool thing is you can use the screen-viewer to see what the end user is doing, (there is a small bug with the Viewer. If the desktop of the thin client does not show up, just do a vncviewer IPaddress:0 to it, once its up close it, that try the viewer and you should see the thin-client desktop in the viewer.) or you could just vncviewer to the machine and control it.
You can also do all this with Win4lin server, but its a bit slower and uses a bit more processing power. I want to try to get virtualbox and Xen working the same way but dont have the time. I found some info on doing it with Xen here https://lists.ubuntu.com/archives/ed...er/002429.html
if anyone wants to check it out and give it ago.
Well if anyone has any info or success with doing this with Xen, or virtual box...Please post!
Example:
/home/test/.xsession
#! /bin/bash
vmware -X -q /VMware\ Machine/Windows\ 2000\ Professional/Windows\ 2000\ Professional.vmx
}
run_parts () {
# until run-parts --noexec is implemented
if [ -z "$1" ]; then
internal_errormsg "run_parts() called without an argument."
fi
if [ ! -d "$1" ]; then
internal_errormsg "run_parts() called, but \"$1\" does not exist or is" \
"not a directory."
fi
for F in $(ls $1); do
if expr "$F" : '[[:alnum:]_-]\+$' > /dev/null 2>&1; then
if [ -f "$1/$F" ]; then
echo "$1/$F"
fi
fi
done
}
Follow the Win4lin instructions.
Initial configuration may consist of simple changes such as ensuring that the Administrator user in Windows logs in automatically without having to prompt the user. Since the system image will be provisioned to other users in a "copy-on-write" fashion, it is not a security risk that the default user in Windows be Administrator. Once the initial configuration is complete, the system administrator shuts down the session using the Shut Down function of the Start menu. Next, the administrator makes a backup copy of the guest image, to preserve the pristine installation in case something becomes corrupt during future configuration steps:
cd ~/winpro
cp GUEST.IMG GUEST.IMG.bak
Next, the system administrator designates the winpro configuration of the master user as a master profile:
/opt/win4linpro/bin/export-profile
Notice that there are no special arguments to export-profile since the default winpro configuration is being used.
In order to complete the export, the session is started (and promptly shut down) one more time:
winpro
Now is a good time to import the profile for the two users we want to provision. This does not need graphical capabilities, so we can switch users using the su command and not worry about the DISPLAY variable. Each user's password is of course typed in at the su prompt:
User created on the server
su - testuser
/opt/win4linpro/bin/import-profile /home/master/winpro
exit
At this point the basic export/import of the master profile and provisioning to the users is complete. Any changes in the master profile will now automatically propagate to the users who import from it testuser. Also, further configuration may be done graphically and remotely from a computer running the Win4Lin WTS/VDS client. There is no need to use shell commands anymore, except of course to make a final backup of the master profile's GUEST.IMG file once the application configuration is done.
Copy the /opt/win4linpro/bin/mergepro.xsession to /home/testuser
Rename the mergepro.xsession to .xsession.
Start your LTSP thin client logon, and you should have a full screen win4lin session.
All this can also be done with VMware Player
This is criptic I know. If someone wants to clean it up and post it some where that be cool. Most of the info is floating around in different places on the net, some I just figgured out. Hope this helps someone out there. I posted most of the sources. As for the Win2003....There is info all over the place, little bits and pieces all over, I just put the pieces together.
Feed back would be good.
Let me know what you think.
Referencia: http://forum.freespire.org/showthread.php?t=10932