You can boot Thinstation from a hard disk using either Loadlin or Syslinux. Loadlin use a DOS file system, whereas syslinux use. Reboot the Thinstation PC. This disc is meant to install the build env along with the dev env into /thinstation. It will install a bootable TS image onto the hard drive and make this. Please note you do still need the TFTP server to deliver the thinstation.conf file unless you adapted the thinstation.conf.buildtime correctly and make an unique image for each computer or you use the STORAGE_PATH option in thinstation.conf.buildtime and have a local thinstation.conf.user directly on the media as STORAGE_PATH/thinstation.profile/thinstation.conf.user. Sep 14, 2014 This video shows the installation of ThinStation 5.2.4 DevStation on a Virtual Box system. This is the first step to building a ThinStation system. You will use the DevStation box to build your custom builds. Custom builds are usually booted from PXE, from the network. Booting from USB drives, CD-Rom / DVD, and the hard drive is possible too.

Part III – How to add drivers to your Thinstation build Part IV – How to configure Thinstation and Google Chrome for a true, thin client experience Towards the end of my studying for the VCP5-Desktop exam, I decided to look into using some old laptops and PCs I had lying around as thin clients. Sony Internet Tv User Manual on this page. Searching the web, I ended up settling on and wresting with for a couple days. As one of the few, free, thin client options, Thinstation is probably the most stable and most up to date software available. This post shares the efforts I put into getting it running in my home lab. You can follow Thinstation documentation in the same way that one can simply walk into Mordor.” – Mike Brown My end state goal is to touch the thin client as little as possible before working from a View desktop. So my vision, then, is to PXE boot the end point, let it download the thin client OS, and have it auto-launch a View desktop client.

From there, a user could enter credentials and log in. What’s the idea? There are a few ways to get Thinstation working in a PXE boot environment. The overall idea, no matter how you go about it, is that you have to use a development station to build the thin client boot image that will be downloaded to your thin client hardware via a PXE boot infrastructure. There are no good materials on the intertubes to follow in a step-by-step fashion for this setup, so here’s my attempt at the first such walkthrough, as far as I can tell. Winusb Deb 2017.

The above graphic describes the servers and clients in the environment. I used a Windows Server 2008 R2 VM as a DHCP server and Active Directory, the was used to install the PXE boot server in a VM, what the Thinstation team calls the “DevStation,” a name I’ll continue to use in this article, a View Connection Server 5.3 server in a VM, the thin client hardware (an old Dell Inspiron 6000 laptop for me), and finally, a Windows 7, View Composer Linked-Clone desktop. I am, of course, leaving out a few crucial elements, like a vCenter Server, ESXi hosts, and View Composer, but that’s really not the detail needed in this post. I’m assuming you already have a working View environment at least for LAN users. I happen to be using linked-clones, which requires View Composer, but you don’t even need those. Full View desktops would work just as well in this post.

PXE Booting Using the diagram above, here’s a quick refresher on PXE booting. The thin client hardware has been configured in the BIOS to PXE boot first. In addition, I chose to disable all other boot options. When PXE booting, the client requests a DHCP address and receives one. As a PXE boot client, it also receives, from the DHCP server, Option 66, the IP address of the PXE boot server, and Option 67, the path and boot file name to request from the PXE boot server. The boot file name is pxelinux.0.