Thin Clients...

[paulrockliffe]

I have a copy of Windows 11 running in a Virtual Machine that I access via RDP on my Android Tablet for a few things. I have a temporary need to connect to a virtual machine from a proper desk and I have a Dell Wyse 5060 Thin Client. I think it has no OS on it.

Can anyone give me some pointers for what I need to do to get an RDP connection to my Virtual Machine going?

I've done some Google, but not really getting anywhere!

Thanks!

[Captain_Morgan]

Been some time since I played with thin clients but my recollection was they always ran a light weight os be that Linux or windows based, a quick google tells me that seems to still hold true, I’d install your Linux flavour of choice

[paulrockliffe]

I've been at it all afternoon, trying to install the Dell ThinOS that came with it, now I've found the files. Been following the instructions here:

https://www.dell.com/support/kbdoc/en-uk/000126362...

But when I get to Step 22 the Imaging Tool doesn't load. I've tried everything in the BIOS to get it to boot from the USB, but it's not having it! Not sure if I'm missing something on the USB, or whether it's the device settings, so annoying!

Had all sorts of issues with the Dell Imaging Tool too, doesn't work unless your USB is drive a:\ for some reason, took me ages to work that out!

I'm not really bothered what OS I put on it, it would be nice if I could boot straight into an RDP session, which I think the Dell OS does, but I'm at that stage now where I just want it to do something!

If anyone can point me in the direction of some instructions that will work for some other OS, please let me know!

[bangerhoarder]

Tried another USB stick (brand and model)? I’ve had similar issues with ESXi hosts flat out not booting from certain sticks, while others work fine.

[paulrockliffe]

Yes, I've tried a couple. I've managed to get another linux thingy boot up, so the hardware is working. I think the instructions are missing whatever it is that installs the Dell Wyse Imaging Tool so that that boots up, but Google just keeps looping back to those instructions.

My current strategy is to get a basic version of Linux to boot so I can install Thinstation from here:

https://www.thinstation.net/

I don't really know what I'm doing with this, so this maybe a terrible strategy and I'll discover that in a few hours time. Feels like I've wasted all day on this now!

[wombleh]

We’ve got some kit using linux as a thin client. It can work but RDP clients are a bit hit and miss. Remina was last one I used.

Have used wyse in the past, used to network boot then from a PXE service, but USB should be easier. If you can get the wyse boot image file then using something else like rufus to write it to a USB stick might work better than Dells own software.

[bangerhoarder]

We had some very, very old Wyse TCs running Windows CE that I had booting straight to a Server 2008 R2 session login. Actually worked well, but the users really struggled with why USB sticks didn’t really work on the ‘little PCs’.

I spent a lot of time on them - upgraded RAM etc. Was a bit of fun.

[paulrockliffe]

I managed to get a couple of Linux distros to boot up from USB, quite impressed with how they ran to be honest. Couldn't get either of them to install to the hard drive and then boot from there though, possibly something to do with boot records and partitions.

My plan is to sort that out and then clone Thinstation over the top. I don't know if my understanding is correct but I *think* when I manage that. I say when, but let's be honest, it's still an if! Anyway, if I manage that I would be left with Thinstation over the top of whatever distro I manage to get to work and it'll boot into Thinstation? Is that correct or complete bks?

I'm remembering why I stay away from Linux now.

If I get it working properly I might let my wife have the PC out of my workshop and use this to remote into my PC as it'll be nice to have exactly the same setup outside as inside. The thing I bought was £30 and is only a few years old and will run 2 x 4k displays , so should do a decnt job.

[anonymous-user]

This thread was not as interesting as the title suggested

[paulrockliffe]

Sorry, this is the section for computer people though, we're not the most interesting.....

[wombleh]

I am just guessing Paul but looks like thinstation is a complete Linux distribution itself, so you'd need to install that to start with rather than install something else like Ubuntu and then put it "over the top".

[paulrockliffe]

Yeah, I've read through it again and think I have a better idea. I have to setup a Thinstation server I think, then use PXE to load the OS on the Thin Client box from the network. I think, there's a lot of guesswork going on here!

https://github.com/ThinStation/thinstation/wiki/Ge...

That would actually be simpler maybe as I know I can get the Thin Client to boot using PXE and I can setup a Linux VM on my server very easily too. Maybe.

[wombleh]

That would work but sounds quite complicated, if 'twere me then I'd probably stick something like Ubuntu onto the Wyse box or just use a bootable USB, install "remina" or another RDP client onto it, then use that to get onto your Windows server and just ignore the rest of the Linux stuff sat behind it.

[paulrockliffe]

wombleh said:

That would work but sounds quite complicated, if 'twere me then I'd probably stick something like Ubuntu onto the Wyse box or just use a bootable USB, install "remina" or another RDP client onto it, then use that to get onto your Windows server and just ignore the rest of the Linux stuff sat behind it.

Maybe, though it sounds like you have the advantage of vaguely understanding this stuff!

I have Ubuntu installing on my Server as a VM now, so I might persist with turning it into a PXE server now I appear to be making vague progress. It's too hot to think now so a change of course isn't ideal!

[camel_landy]

Not sure if it has been mentioned but bear in mind that thin clients often operate with the disk in a Road-Only state. Any changes are simply cached and then wiped on reboot.

It might be worth confirming if your disk is in a RO or RW state.

HTH

M

[paulrockliffe]

camel_landy said:

Not sure if it has been mentioned but bear in mind that thin clients often operate with the disk in a Road-Only state. Any changes are simply cached and then wiped on reboot.

It might be worth confirming if your disk is in a RO or RW state.

HTH

M

Hmmmm, I guess that would explain why it won't boot once installed to. Where do you change that? In the BIOS or a jumper inside or something? I've not seen anything like that when poking through the BIOS.

[camel_landy]

paulrockliffe said:

camel_landy said:

Not sure if it has been mentioned but bear in mind that thin clients often operate with the disk in a Road-Only state. Any changes are simply cached and then wiped on reboot.

It might be worth confirming if your disk is in a RO or RW state.

Hmmmm, I guess that would explain why it won't boot once installed to. Where do you change that? In the BIOS or a jumper inside or something? I've not seen anything like that when poking through the BIOS.

I suspect it'll be device specific. I was working on HP Windows Thin clients and IIRC they had something within the OS, accessible via the Admin account... Which may not be much help for you.

Unfortunately, you're probably going to have to do some digging but hopefully that'll help point you in the right direction.

M

[paulrockliffe]

I hope so, thanks!