how to setup thin client windows with linux server?

[wahdangun]

like the title said, can anyone help me how to setup it? please because i have search it in google but can't find anything

 

[Nothinman]

What will the Linux box be serving to them? X sessions?

 

[wahdangun]

I will build internet cafe with windows xp client, and I'm planning for it to open 24/7

 

[Nothinman]

I will build internet cafe with windows xp client, and I'm planning for it to open 24/7

That doesn't say what the Linux box will be serving. Do you want it to just be an AP with some second-level auth so people have to pay to use your Internet?

 

[Khyron320]

What your trying to do is setup plop Linux... but if your doing windows... I'm sure they have a solution for a few thousand. I think at that point you may as well just setup nonthin clients.

 

[sourceninja]

I'm confused on what the OP actually wants. Does he mean windows desktops running virtualized on a linux server and delivered over RDP to thin client devices? Or does he mean windows computers that are opening up X sessions to a linux server (providing linux apps or a gnome desktop)?

 

[wahdangun]

sorry if I'm confusing you guys, what do I mean is its something like booting windows xp through the network using PXE, so the linux just act as hdd, something like diskless system. But I didn't know if that can be done with linux as the server

 

[Nothinman]

sorry if I'm confusing you guys, what do I mean is its something like booting windows xp through the network using PXE, so the linux just act as hdd, something like diskless system. But I didn't know if that can be done with linux as the server

Probably, but that's not a thin client setup. A thin client means you have a device with a minimal OS that boots up and right after getting IP information initiates an RDP, ICA, etc connection to a terminal server and gives you a remote desktop from there.

I don't have any specific information regarding PXE booting Windows from the network other than stop looking at XP and use Win7 from the start. XP is on its last legs and will be completely unsupported soon.

 

[postaled]

Probably, but that's not a thin client setup. A thin client means you have a device with a minimal OS that boots up and right after getting IP information initiates an RDP, ICA, etc connection to a terminal server and gives you a remote desktop from there.

I don't have any specific information regarding PXE booting Windows from the network other than stop looking at XP and use Win7 from the start. XP is on its last legs and will be completely unsupported soon.

It sounds like what he really needs is to have a minimal os boot through PXE and just rdp into a windows environment.

 

[VinylxScratches]

RDP wouldn't play video/music nice at all...

 

[wahdangun]

Probably, but that's not a thin client setup. A thin client means you have a device with a minimal OS that boots up and right after getting IP information initiates an RDP, ICA, etc connection to a terminal server and gives you a remote desktop from there.

I don't have any specific information regarding PXE booting Windows from the network other than stop looking at XP and use Win7 from the start. XP is on its last legs and will be completely unsupported soon.

yes that what I mean, but iI don't think I need minimal OS, i just need full blown windows XP, and it will be used to play games too

It sounds like what he really needs is to have a minimal os boot through PXE and just rdp into a windows environment.

no I don't need minimal OS boot, I just need the client to boot over LAN, because it will make me easier to maintenance, and it will be cheaper because I don't need to buy HDD for the client

RDP wouldn't play video/music nice at all...

so what is RDP ??

 

[Nothinman]

yes that what I mean, but iI don't think I need minimal OS, i just need full blown windows XP, and it will be used to play games too

I meant minimal from the client side, otherwise there's no point to using a terminal server.

no I don't need minimal OS boot, I just need the client to boot over LAN, because it will make me easier to maintenance, and it will be cheaper because I don't need to buy HDD for the client

It will be a lot more difficult because Windows wasn't meant to be run like that and the latency will be killer unless you have a ton of network bandwidth at your disposal. You're adding the latency of the network + concurrent access to whatever disk array you have in the server to normal disk access. Meaning, if the array can normally give you <3ms seeks, you'll be at least doubling that with CAT5 and probably taking it up even higher because you'll have multiple machines trying to use the disks at the same time.

If you just want easier maintenance you need to look at AD and GPOs for remote management, that's what it was designed for. And again, you shouldn't even be considering XP at this time unless you have some 3rd party business critical app that requires it because it's support from MS is ending very soon.

so what is RDP ??

Remote Desktop Protocol. I don't mean to be a dick, but if you have to ask this question then the project is probably out of your league.

 

[aceO07]

no I don't need minimal OS boot, I just need the client to boot over LAN, because it will make me easier to maintenance, and it will be cheaper because I don't need to buy HDD for the client

HDDs aren't that expensive compared to the rest of the system. Also if you're playing games, you'll need decent graphics cards.

The setup you've thought up is probably best for web browsing, office applications, etc.

 

[Paperlantern]

HDDs aren't that expensive compared to the rest of the system. Also if you're playing games, you'll need decent graphics cards.

The setup you've thought up is probably best for web browsing, office applications, etc.

This is also what I was thinking. GAMING on a thin client, or watching movies or other media content (the primary thing a station in a internet cafe DOES) is not the forte of a thin client type of setup.

 

[MrChad]

A thin client is not what you want. In the XP days, SteadyState was a good solution for shared access machines. Now you can get most of those features with OOTB features in Windows 7. Take a look at this guide on setting up your machines so that they are locked down and easily managed/restored.

 

[Scarpozzi]

A thin client is not what you want. In the XP days, SteadyState was a good solution for shared access machines. Now you can get most of those features with OOTB features in Windows 7. Take a look at this guide on setting up your machines so that they are locked down and easily managed/restored.

If he was just needing a thin client, the Wyse boxes are about the best....they connect to Xen desktop, Vmware view or RDP....and basically take the client side hardware out of the equation by being so slick...

I just doubt he has the bank to setup the server side of things. It takes some complex configuarations to get desktop virtualization deployed....

 

[sourceninja]

If he was just needing a thin client, the Wyse boxes are about the best....they connect to Xen desktop, Vmware view or RDP....and basically take the client side hardware out of the equation by being so slick...

I just doubt he has the bank to setup the server side of things. It takes some complex configuarations to get desktop virtualization deployed....

Don't forget that just having view or xendesktop or even a vmware server running windows desktops and using rdp is not being compliant with MS licensing. You need to buy VDA licenses for each device that will be accessing those desktops.

 

[stlcardinals]

yes that what I mean, but iI don't think I need minimal OS, i just need full blown windows XP, and it will be used to play games too

I don't think he needs a thin client then.

 

[xSauronx]

I don't think he needs a thin client then.

im with Nothinman...this is almost certainly out of his league. The OP clearly is not familiar with the technology, protocols and processes involved

 

[Jeff7181]

What he needs is some Ubuntu Live CD's and some cheap PC's. Done.