![]() I'd recommend creating the folder home/user/compile/thinstation_src-2.2.2 location, but it's up to you. Create a folder in the dialog box that appears and click the extract button. From there just click the extract button on the menu bar. Right click on the "Thinstation src-2.2.1.tar.bz2" file and click open with Archive Manager. Once you have the files copied locally on the Ubuntu machine you will need to extract the files. You can copy them to an ISO or a USB key and access the key from the Virtual Machine or you can create a folder and share the folder to your windows machine. "Thinstation src-2.2.1.tar.bz2" and "thinstation src-2.2.2 2" files are the ones we need.Ĭopy the files to the Ubuntu Virtual Machine. Once you have that downloaded, go back to the main download page and click the "thinstation developer" package. The filename is "Thinstation-2.2.2.tar.gz". We are going to download the thinstation 2.2 package. We will need to download the "thinstation" package and the "thinstation developer" package.įirst click the "thinstation" package. This redirects your current frame to the sourceforge downloads for thinstation. When you access the site, choose the downloads link half-way down the page. Once you have it downloaded run the installation for the player. The VMware Player can be downloaded here for free under the Desktop downloads section. You could use an actual machine or another VM technology but we are using VMware because they already have a pre-built Ubuntu appliance that will save a lot of configuration. We can begin this by downloading the VMware Player from VMware's web-site. To begin with we will be to create a build environment for the ISO. The technologies used for these are all available on the internet and include the VMware player, Ubuntu Linux (available from VMware as a preloaded appliance) thinstation distribution, Intel NIC drivers and of course the Out of Band software from Symantec.ġ) Download and Install the VMware player The first scenario can be addressed by creating a Linux ISO, complete with network drivers and terminal server client. In both of these scenarios the ISO would have to be small enough that it could be copied over the WAN using the IDE-redirection and be able to load in memory so that if the time-out hits, you can continue using the ISO with no issues. Once the computer had been reimaged you can copy the user's data back to the computer. However with a bootable ISO that allows for NTFS access and network access you can copy the user's data to a local server and then re-image the computer. This still takes the computer out of commission inconveniencing the user and wasting time. Once again in order to do this you have to send a technician on-site to replace the hard drive or have the computer sent to a repair location. However there may still be accessible data that can be copied to a server and then the hard drive can be reimaged. This scenario is similar to scenario 1 in that a user's hard drive is no longer bootable. While waiting for the technician or the hard drive to arrive the user can access standard applications through the terminal server. However with a bootable ISO that connects directly to a terminal server you could allow the user to continue working on the computer while you sent a technician on-site or sent a pre-imaged hard drive on site and walked the user through swapping it out. Either way this takes the computer out of commission inconveniencing the user and wasting time. In order to do this you have to send a technician on-site to replace the hard drive or have the computer sent to a repair location. When the timeout kicks-in you lose your OS that you have booted to.Ī user's hard drive crashes and needs to be replaced. ![]() Further some ISOs don't load into memory requiring that the source files which are provided through the IDE redirection are available. That works well for LAN connections but once you start trying to load an ISO image that big over the WAN you'll find that the timeout for the IDE redirection may kick in before you even get the image loaded. Those limitations include booting to a WINPE ISO image that is bloated, usually in the 250mb range. However IDE redirection has been slow to pick up any real usefulness because of the current limitations when using the out of box options. There has been a lot of information released regarding the synergies of Intel's VPro technology that used AMT and Symantec's Altiris Out of Band Management that utilizes those technologies for things such as reboots, power-on and IDE redirection allowing for booting to a remote ISO image.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |