Thanks Ric_ you've been a big help!
Have you suffered from problems with wireless through thin Client? One supplier I know asked whether or not I was using 2200GB Intel because they had a problem with stopping logins on a fat network until the first 8 had finished? This might mean that it would also affect thin clients?
IIRC Ric is using wireless.
@wesleyw: I use that chipset and suggest that said supplier is talking out of somewhere other than their mouth.
Think about it logically... the amount of bandwidth required for a fat login is quite high since it pulls a desktop, start menu, some registry settings and more. With the thin client set up, you get a few screen refreshes. This is clearly less bandwidth hungry.
Cool thats all I needed to know. After what you've said I think I'll go with the other choice of Thin Client installer i.e. Precedence I won't mention the name of the company that said that about the chipset.
Answers on a postcard to...
Sorry to p&*s on your fire but this is not completely true.Quote:
The biggest problem with this Windows solution is the lack of load balancing. The only way to spread users across servers would be to use a crude 'round-robin-DNS' system of load balancing.
You can load balance Windows Terminal servers using a NLB cluster and load balance port 3389.
It may not be "true" load balancing eg. processor load etc. but it is load balancing nevertheless
How to Configure Windows Network Load Balancing for pure Terminal Server environments
Does anyone have experience with HP ThinConnect? Any advice? Which OS is best for most (if not all) types of USB memory sticks to work? Thanks
In the Client-side section, you state "Not all the benefits of thin client computing will be gained from using old hardware". I think that this needs clarification, ie what benefits are you missing out on and under what circumstances. For example, in a LTSP setup, using something like a PIII 533 MHz, 256Mb PC as a thin client, the only benefit that you are missing out on is aesthetics.
OT If you want a system for a small number of users, this is intersting Six headed, six user system
Have printed it off for a good read. ta!
That is interesting! I would like to have a go at that one day :) .Quote:
Originally Posted by openhgs
They had a few of those running as a net cafe at BETT. Wish I'd got more info from them now :(
I will answer your question and add it to the next version of the document...Quote:
Originally Posted by openhgs
The advantage of thin client computing is reduced TCO, not improved aesthetics. We all know that shiny mini-ITX computers can be bought and used in a fat-client environment.
With thin clients you are aiming to reduce the amount of money you spend maintaining your systems so you want to reduce power consumption (i.e. solid state devices without moving parts), increase lifespan of machines (no moving parts to wear out) and reduce the time that must be spent maintaining hardware (a PIII-533MHz is likely to be on its last legs and will require time caring for things such as PSUs, fans and the like).
Don't get me wrong, use old hardware until it starts to eat into your time and you have money to replace with easier to maintain hardware. I apologise for not explaining more fully but it was starting to get late when I got that far down my document ;)
I don't know anything about thin client networks or their configuring of them but i did come across a terminal services app out for OS X Server in this field.
You can now download a trial version but since i haven't got that basics set up i won't have the time to check it out before the installation expires.
If i remember correctly Ric_ has some macs at his place and with his thin client setup it would be interesting to see, if he has the hardware and the time to trial it to see how it fairs against more established hardware and software out there.
Apparently the clients can be PCs as well as macs to connect to the server.
A quick look at the FAQ just suggests that it is a VNC server but if I get time (unlikely at the moment) I may look in to it.