Thinstation is an open source product that allows the computer to change a bit 'dated in terminals.
Its use is quite simple, as long as you already know quite well how Linux works and services terminal. This article briefly describes how to set Thinstation installation in a typical scenario. Thing to note is that before you begin any of the virtual machines currently on the market with Etherboot compatible network cards and Thinstation in general, then we must immediately rule out testing in the VM.
The scenario considered is as follows:
- using Windows Terminal Services;
- PCs possess floppy drive and CD-Rom;
- we service with Microsoft Windows Server DHCP active;
- a Linux machine to compile the images TS.
We want to start the PC with TS from the network and connect them to the Windows server via RDP.
1 - PREPARATION
Get Thinstation 2.2.2 (currently stable version) from here ; about 50MB we have everything you need. From a Linux installation unpack the package. In the folder that we get build.conf find a file that is used to configure the hardware package of the machines in question.
before completing the whole and get our pictures up, we need to collect some data needed by the PC on which we want to run TS:
- make and model network card;
- make and model video card;
- make and model Chipset;
- mac address card network;
- make sure that the ram is 64MB, otherwise TS will not start.
For the collection of this data Everest Portable Board (thanks to Bert). Write the file
build.conf as examples in the same folder, adding the packages you need. Besides these we also rdesktop package, which manages the RDP.
NB: for the redirection of USB, you will see from Windows Explorer. E 'must include packages "supermount" and "automount" as well as cha naturalemnte "usb-hid."
Compile all running the terminal command ". / Build".
In Folder "boot-files/etherboot" find the two files that we need to boot from network using Etherboot, there are other folders for other images to boot media (cdrom) and methods (PXE, syslinux etc.. ).
2 - BOOT
To allow network booting via Etherboot floppy disk will take care of writing the image Etherboot client machines that TS provides us in the "prebuild. The image to 32KB is used to force the boot from the network even to PCs that do not support it.
We also need to setup a server (TFTP is a protocol very rough for sending images via network boot) use for this Solarwind TFTP server (free), by setting that the server is read-only (NB: the outbound port of this server is 69 UDP, set of Therefore any firewall).
In the folder that we set as the TFTP root and put the files thinstation.nbi thinstation.nbi.zpxe found after compilation in "boot-files/etherboot. In the DHCP MMC
also, Setting Options, activate the entries 066 and 067 respectively with the server's IP address and name of the boot files "thinstation.nbi.zpxe.
NB: some guides to show that Etherboot DHCP must be set in the file "thinstation.nbi," but we also want compatibility with PXE.
3 - Configuring TS
The following provides a working setup in many cases:
NET_USE_DHCP = On
KEYBOARD_MAP = en
USB_ENABLED
CUSTOM_CONFIG = On = Off = On
RECONNECT_PROMPT
SESSION_0_TITLE = "Terminal 1"
rdesktop
SESSION_0_SCREEN SESSION_0_TYPE = = 1 = 192.168.1.17
SESSION_0_RDESKTOP_SERVER
with # redirect the usb chivette
SESSION_0_RDESKTOP_OPTIONS = "-u 'DOMAIN \\ \\ user'-r disk: USB = / mnt / USBDevice, sound: off"
SESSION_0_AUTOSTART = On
SCREEN_RESOLUTION = "1280x1024"
SCREEN_COLOR_DEPTH = "16"
SCREEN_BLANK_TIME
SCREEN_STANDBY_TIME = 20 = 10
SCREEN_SUSPEND_TIME
SCREEN_OFF_TIME = 30 = 60 =
X_DRIVER_OPTION1 "hwcursor Off"
NET_HOSTNAME = Nomepc
The entries are self explanatory, also thinstation.conf.sample is all well documented. We have many options for how and where to place the configuration files, I prefer to do one for each machine that loads from the same network when you start.
To do this we set the IP reservations in the DHCP server (by entering the mac address of the card) and placed in the root of the TFTP server files with names like this "-thinstation.conf 192.168.1.11" in order to check the configuration of each machine simply by changing a configuration file on the server. The file is read only at startup of TS.
Lastly, a similar product: NetStation, which is less flexible and less powerful but lighter, and then to be taken seriously if the ram of the terminals is very low (even 8 MB).
0 comments:
Post a Comment