Slashdot Mirror


Where Are the Cheap Thin Clients?

Darren Ginter writes "I find many aspects of desktop virtualization compelling, with one exception: the cost of the thin clients, which typically exceeds that of a traditional box. I understand all of the benefits of desktop virtualization (and the downsides, thanks) but I'm very hung up on spending more for less. While there are some sub-$200 products out there, they all seem to cut corners (give me non-vaporware that will drive a 22" LCD at full resolution). I can PXE boot a homebrew Atom-based thin client for $130, but I'd prefer to be able to buy something assembled. Am I missing something here?"

349 comments

  1. other costs by Anonymous Coward · · Score: 1

    We usually use WYSE clients and you might be right, however, don't forget to sum up additional costs for traditional hardware, such as maintenance (drives, fans)

    1. Re:other costs by Anonymous Coward · · Score: 3, Insightful

      A PXE-booted Atom board has neither drives nor fans.

    2. Re:other costs by Anonymous Coward · · Score: 0

      way to miss the point

    3. Re:other costs by Skapare · · Score: 1

      Isn't the point to keep the cost of a thin client really thin?

      --
      now we need to go OSS in diesel cars
    4. Re:other costs by Dragonslicer · · Score: 1

      A PXE-booted Atom board has neither drives nor fans.

      Discuss.

    5. Re:other costs by Anonymous Coward · · Score: 0

      PXE: Doesn't need drives
      Atom: Doesn't need a fan

      Such a system could use a drive or a fan, if necessary. Now what else is there to discuss?

    6. Re:other costs by 0100010001010011 · · Score: 1

      Go with clientless thinclients depending on how large your install base is.

      Multiseat linux setups are rather easy to setup. There are even a few commercial applications. (My local library has one).

      If they don't need DVI, there are some solutions which you just run a single USB cable and it carries sound, USB & VGA. If your work environment is setup so people are relatively close together, give each desk cluster a quad or octocore CPU and everyone their own X session.

      I have a friend with a few kids (3-4) and the oldests are now starting to both want to use the computer. You can either 1) Buy 2 separate computers 2) Get 1 decent computer (dual core should be plenty for a 5 year old) and just setup 2 monitors side by side.

      http://linuxgazette.net/124/smith.html
      http://www.oreillynet.com/onlamp/blog/2005/12/multiseat_x_under_linux.html

    7. Re:other costs by Zerth · · Score: 1
    8. Re:other costs by femtoguy · · Score: 1

      And the Acer Aspire Revo ( http://www.newegg.com/Product/Product.aspx?Item=N82E16883103228&cm_re=revo-_-83-103-228-_-Product ) looks like a pretty cheap and capable box at $200. VGA and HDMI, low power, and a commodity product, so you can have spares on hand.

    9. Re:other costs by Anonymous Coward · · Score: 2, Insightful

      ...says the person who uses fail as a noun. :)

    10. Re:other costs by Xaositecte · · Score: 1

      Honestly, this one is pretty obscure. Went right over my head too.

    11. Re:other costs by Anonymous Coward · · Score: 0

      Yeah, over mine too, and I wrote that comment.

    12. Re:other costs by welsh+git · · Score: 1

      He was pointing out that a typical Thin Client has no fans or drives, so the cost saving of not having to services such things in traditional computers should also be factored in.

      --
      Sig out of date
  2. Yes by Anonymous Coward · · Score: 5, Funny

    Am I missing something here?

    A cheap thin client?

    *ducks*

    1. Re:Yes by Anonymous Coward · · Score: 5, Funny

      In my experience ALL clients are cheap.

    2. Re:Yes by VampireByte · · Score: 1

      ...but I'd prefer to be able to buy something assembled

      Slashdot, news for nerds. So sad, I remember when nerds built their own systems.

      --

      Run and catch, run and catch, the lamb is caught in the blackberry patch.

    3. Re:Yes by wampus · · Score: 2, Informative

      Some of us have jobs that involve lots of users. I wouldn't want to put together more than two or three boxes, let alone hundreds or thousands of them.

    4. Re:Yes by orlanz · · Score: 3, Funny

      And few consultants are thin.

    5. Re:Yes by Anonymous Coward · · Score: 0

      You're probably just dealing with the thick ones.

    6. Re:Yes by Anonymous Coward · · Score: 0

      Yeah, but - in my experience - they are usually fat.

    7. Re:Yes by mabhatter654 · · Score: 1

      we don't get paid $50 per hour to build PCs from parts. It might actually be cheaper per box, but the company wants to be spending your limited time (=$$) on other things with more return.

    8. Re:Yes by InlawBiker · · Score: 2, Funny

      I got color on my 80x24 terminal running at 9600 baud full duplex, bitches. Lynx screams now.

    9. Re:Yes by NotBornYesterday · · Score: 3, Funny

      Which color? Amber, green or white?

      --
      I prefer rogues to imbeciles because they sometimes take a rest.
    10. Re:Yes by shaitand · · Score: 1

      Most admins lack the skills and knowledge to build quality pc's anyway. They are software guys not hardware guys.

      But I do wonder if these admins who just buy a dell realize that you can build a pc of any given spec with the cheapest offbrand crap and it will still seriously outperform a dell (or any other name brand) of comparable spec.

    11. Re:Yes by Anonymous Coward · · Score: 0

      Sadly I am due to my customers being cheap!

    12. Re:Yes by Bat+Country · · Score: 1

      Yes.

      --
      The land shall stone them with the bread of his son.
    13. Re:Yes by shaitand · · Score: 1

      It's always baffled me. I can piece together a box with the same chipsets and the same specs and load stock windows on it and a dell and the dell will still be very noticably slower.

      What do they do, go out of their way to deliberately engineer their boxes to perform poorly?

    14. Re:Yes by myrmidon666 · · Score: 1

      Cheap as in beer or.... ?

      --
      *Process is Irrelevant, Progress is Paramount*
    15. Re:Yes by RockDoctor · · Score: 1

      XOR(Amber, green, white)

      FTFY.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    16. Re:Yes by Anonymous Coward · · Score: 0

      But, in U.S. of A., none of them are thin :)

    17. Re:Yes by Anonymous Coward · · Score: 0

      And in the US, very few are thin.

    18. Re:Yes by jon3k · · Score: 1

      Most admins can't build a pc? Really? You honestly believe that?

    19. Re:Yes by Anonymous Coward · · Score: 0

      Most smart admins aren't going to waste there valuable time building boxes. Seriously. I've worked with some dumb ones. Who like you count their work time as free. Then we've got to come up with the cash to pay for the hours they wasted saving a few dollars. I've got a guy who can't throw something away if he thinks he can fix it. He'll even pull stuff out of the trash with some long story about how he could combine that with something and make something useful. It's broken part that costs $10 new. Leave it in the trash.

    20. Re:Yes by bill_mcgonigle · · Score: 1

      Some of us have jobs that involve lots of users. I wouldn't want to put together more than two or three boxes, let alone hundreds or thousands of them.

      At that kind of volume you can do some local job creation (high schooler, etc.) and still have money left over to send him for pizza.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    21. Re:Yes by Bat+Country · · Score: 1

      They tend to load them up with crapware.

      That and they tend to use the very cheapest motherboard they can find, which usually means extremely bad northbridges.

      --
      The land shall stone them with the bread of his son.
    22. Re:Yes by Anonymous Coward · · Score: 0

      Iunno about that.

      I bought a Vostro 220 off the Outlet at Dell. 2.6GHz Core2Duo proc, 2 GB of RAM, 250 GB HDD, Vista Business.
      I've been able to use it quite tolerably with its base configuration for just shy of a year now.
      For me, "quite tolerably" is being able to run EVE, Lord of the Rings Online, Half-Life 2 Episode 1, or play a bunch of other, less intensive games without the game stuttering. Granted, the graphics aren't generally set to some ridiculously high and fancy level - I've just the cheap onboard graphics, so I turn it down a bit. Games are playable and enjoyable, but I might not get the super jiggly boobies switch in some game. :B

      I spent $280 on that machine with shipping.
      I've not been able to match that price building a box on my own, but I honestly don't notice any slowness on the system, compared to a similarly spec'd non-Dell box. (Keep in mind, yes, I wiped the HDD and did a fresh install of the OS on the Dell, to get rid of the specialfunhappy software that is added to some models.)

      (Full disclosure: I do phone support for Dell, but I am not directly employed by them.)

  3. It's like bicycles... by Eric+Smith · · Score: 4, Insightful
    The more you pay, the less you get.

    Though not for the same reason. You get a complete PC for less than a thin client because complete PCs are made in insanely high volumes compared to thin clients, which are a niche item.

    1. Re:It's like bicycles... by geekmux · · Score: 4, Interesting

      The more you pay, the less you get.

      Though not for the same reason. You get a complete PC for less than a thin client because complete PCs are made in insanely high volumes compared to thin clients, which are a niche item.

      Er, sorry. I consider dual-socket desktops with 64GB of RAM and 8 cores attached to a 30" monitor running 3D CAD programs a "niche" item. Thin-client hardware has been around now for at least 10 years. I'm struggling to find the connection there, especially when those that truly find the value in deploying this hardware usually do so with an order for hardware in the hundreds or thousands.

      They charge what they want to charge more likely because companies like WYSE know that when you buy their hardware, the functional lifespan is likely 2 to 3 times that of a traditional desktop, and it's gonna be a while before you're knocking on their door for a purchase again.

    2. Re:It's like bicycles... by bigsteve@dstc · · Score: 2, Informative

      I'm struggling to find the connection there ...

      The comparison is not with massively over-spec'ed gaming machines or CAD monsters. It is with the bottom end desktop boxes, etcetera that millions of office workers use.

      Two of the factors that drive price in the PC marketplace are competition and scale. On the one hand, if WYSE (or whoever) are the only people selling thin client machines, then they don't need to worry about competitors undercutting them. On the other hand is WYSE is only selling low volumes of thin client machines (because most customers are buying regular desktops/laptops/notebooks/whatever), then they have to sell them at a higher price to recoup development costs, costs of setting up production lines, costs of buying components in smaller volumes, marketing costs and so on.

    3. Re:It's like bicycles... by characterZer0 · · Score: 1

      The more you pay for a bicycle the less you get? What on Earth are you talking about?

      The only way that makes sense is if you are only referring to weight, but that is an undesired quality, and something the engineers try to reduce.

      It is like saying that the more you spend on a computer, the less slowness you get.

      --
      Go green: turn off your refrigerator.
    4. Re:It's like bicycles... by Znork · · Score: 4, Informative

      It is with the bottom end desktop boxes

      Which usually contain COTS hardware. Which a thin client can also use today. Like the submitter said, slapping together a thin client is easy.

      they have to sell them at a higher price to recoup development costs

      There are basically no development costs in this case, nor are the components high margin enough that production volume can make a significant difference in purchasing price. We're not talking special hardware here, we're talking miniITX/laptop MB's which are produced in the bazillions range whether or not a thin client producer uses them.

      Personally I'd say the higher price is because the target market is almost fully corporate and corporate purchasers usually have difficulty comparing prices with anything that's not explicitly listed as equivalent. Which gets you the old triple-the-list-price and then let them negotiate a 50% discount and the customer will feel good about his leet bargaining skillz.

    5. Re:It's like bicycles... by jonbryce · · Score: 2, Informative

      Chip PC also sell thin client machines. I don't know how the price compares to Wyse. They don't sell direct, so you need to contact one of their resellers.

    6. Re:It's like bicycles... by drinkypoo · · Score: 4, Informative

      The more you pay for a bicycle the less you get? What on Earth are you talking about?

      The most expensive bicycles are not full-suspension mountain bikes that can go anywhere. They are racing bikes with few gears and really suited only for flat terrain (although with a sufficiently powerful "motor" you can go up hills, of course.) So yes, the more you pay, the less you get. It's not just weight, but it's largely because of weight.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:It's like bicycles... by moonbender · · Score: 1

      Racing bikes with no gears, my biking-geek friends tell me.

      --
      Switch back to Slashdot's D1 system.
    8. Re:It's like bicycles... by vegiVamp · · Score: 5, Funny

      > The more you pay for a bicycle the less you get? What on Earth are you talking about?

      It works exactly the same for bikinis, really.

      --
      What a depressingly stupid machine.
    9. Re:It's like bicycles... by Daengbo · · Score: 3, Informative

      People are looking in the wrong place. Move outside Intel and AMD.

      $99 for a computer in a keyboard from Norhtec. (In fact, the prototype is still linked in my sig, but I have no connection to the company.) Video is available at Linux For Devices, but the Gecko Surfboard doesn't appear to be listed on tNorhtec's site yet.

    10. Re:It's like bicycles... by gbjbaanb · · Score: 1

      Er, sorry. I consider dual-socket desktops with 64GB of RAM and 8 cores attached to a 30" monitor ... a "niche" item.

      Sorry, but I don't. there again, I am running Office 2007 and I need Outlook, 2 Word documents and an Excel document open *at the same time* on a daily basis. :)

    11. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      If you're not getting a corporate discount, you should probably be looking at why you're virtualizing such a low number of machines.

    12. Re:It's like bicycles... by Linuxmonger · · Score: 2, Informative

      Thin clients have been around more like 40 years.

    13. Re:It's like bicycles... by dimeglio · · Score: 4, Insightful

      I think the savings in deployment and long term maintenance of these terminal units are just an illusion. 1. it simply switches the cost of the workstation maintenance to the back office as you need an immensely powerful data centre to drive thousands/tens of thousands of these terminals; 2. you still need a service desk as most requests we get are for new employee accounts and handling typical release incident; 3. people want to stay competitive and having a one size fits all typically prohibits one-offs, even if there is an obvious advantage; 4. problems affecting a cluster will affect everyone so you still need backup PCs for critical service delivery. It was a great idea when all you needed was amber on black text and typically only ran 3-4 applications but now people expect full multi-media experiences, web 2.0, and although terminals are able to a certain degree to deliver these, it is often awkward and demands more than a cheap disk-less unit.

      --
      Views expressed do not necessarily reflect those of the author.
    14. Re:It's like bicycles... by kFiddle · · Score: 4, Insightful

      This basically just reaffirms the submitter's point. The PC-in-a-keyboard is not a thin client--it's a full, although lightweight, computer in a keyboard. It's $100. Want to buy an actual thin client? Expect to pay $300-$1000. Throw in a keyboard and monitor, and that ups the price quite a bit.

      Also, the argument that thin clients are "specialty" items that drives up production costs doesn't hold up, since one would assume the $99 computer-in-a-keyboard is also a specialty item. It contains, at a minimum, a hard drive and a keyboard, which is already much more than a thin client has (not incl thin client laptops).

      So why are thin clients so expensive? I've had the same question for a while now, since I've been looking around for a thin client laptop that's cheaper than a traditional laptop/netbook. So far I haven't succeeded, with most thin client laptops being much more expensive.

      My guess is that the marketers hear phrases like "high security," "low energy consumption," "remotely managed," "longer longevity," "virtualization," "cloud computing," etc and think they have features that can drive the price up. The geeks, though, understand that they could build their own "thin client" by just subtracting physical parts from their existing computer and doing a little configuration.

      --
      In the world of kung fu, speed defines the winner.
    15. Re:It's like bicycles... by Clover_Kicker · · Score: 1

      That's pretty sweet, the first thing I'd do is install a Commodore 64 emulator.

    16. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      So they just run with these no-gear bikes? It's racing bikes with ONE gear my pedantic friends tell me.

    17. Re:It's like bicycles... by Daengbo · · Score: 1

      I don't understand your point about this. It doesn't have local storage. You can network boot or install some minimal thin-client OS on compact flash. It would be dead simple to hook 30 of these up to an LTSP server. Also, why would having a keyboard disqualify it from being a thin client? In fact, according to the referenced article it

      is said to make a "great thin client," and to be "ideal for bank tellers, reservation clerks, POS, home, schools, or hospitals."

    18. Re:It's like bicycles... by selven · · Score: 1

      Isn't it two gears? You need a gear to mesh with the first gear.

    19. Re:It's like bicycles... by graffix01 · · Score: 1

      Funny I think you'd have a hard time finding a more expensive bike than the ones they use in the Tour De France and I seem to recall a few hills in that race. Track bikes on the other hand have one gear and are not nearly as expensive. Granted, weight or the goal of reducing it is the basis for cost, your comment about lack of gears and being intended for flat ground is quite wrong. Modern road bikes have 20-30 gears to chooses from.

      --
      Women don't want to hear what you think. Women want to hear what they think, in a deeper voice.
    20. Re:It's like bicycles... by reub2000 · · Score: 1

      A full suspension mountain bike can be expensive as you want it to be.

    21. Re:It's like bicycles... by kFiddle · · Score: 1
      I don't understand your point about this. It doesn't have local storage.

      From the link you posted:

      Features and specifications listed by NorhTec for the Gecko Surfboard include:

      * Storage -- SD/SDHC card or IDE-interfaced 2.5-inch hard disk drive

      You can network boot or install some minimal thin-client OS on compact flash. It would be dead simple to hook 30 of these up to an LTSP server.

      Of course. You can take any PC and make it a thin client. The point here (from the original poster) is (and I quote), "I can PXE boot a homebrew Atom-based thin client for $130, but I'd prefer to be able to buy something assembled." I also assume it's implied the poster is looking for a solution that doesn't require additional configuration. I.e. a thin client "out of the box," regardless of how easy you or me think it's easy to setup using an existing PC.

      Also, why would having a keyboard disqualify it from being a thin client?

      It doesn't (and, in fact, I mentioned thin client laptops, which would have both a monitor and a keyboard). What I meant was that the PC-in-a-keyboard comes with a keyboard and hard drive and is essentially a full computer for the very cheap price of $100. Buy a thin client with the same specs WITHOUT these components and pay at least 3 times more.

      By the way, I actually do think the PC-in-a-keyboard is pretty cool. Eee is also making one if I recall correctly, though the initial price was higher.

      --
      In the world of kung fu, speed defines the winner.
    22. Re:It's like bicycles... by hedwards · · Score: 1

      A couple of reasons, for one thing when you're talking about sub $200 computers you're talking about commodity pricing. The average profit margins on computers in that range are tiny, they make up for it by making a huge number of computers.

      Additionally adding to that problem is that a thin client really requires components that are more similar to laptop components than to desktop components. Admittedly you don't have to, but otherwise you're going to have to put up with the heat dissipation, noise and size problems that come with desktop components. They've gotten better, but they're still not anywhere near the efficiency of laptops in general.

      Not to mention that there's a lot of engineering work which doesn't generally need to be redone for desktops. But over all, there isn't really any reason why one couldn't use a netbook as a thin client, it just isn't likely to drive a monitor of that sort of size.

    23. Re:It's like bicycles... by Hurricane78 · · Score: 1

      The problem is that they aren’t. People buy vastly overpowered computers, just as they buy SUVs instead of normal, good looking, money saving, parking spot fitting and fast cars. ;)

      It’s because they think that’s what’s missing from not feeling like they are worthless crap. (Which of course has other mental reasons.)
      It’s to brag, so others might ‘like’ them. (Which of course is doomed to fail.)
      They don’t buy it to do those power-user things. They buy it because they buy a dream. (Wasn’t that also a quote from Hoover?)

      So while you are certainly right that thin clients should not be a niche item, but overpowered machines should be, in reality, both ends of the bell curve are niches. It’s just that the curve is a bit shifted towards the higher end. So thin clients are even more of a niche.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    24. Re:It's like bicycles... by pnutjam · · Score: 1

      HP and Wyse are both very expensive in my experience. I have had very good luck with Igel.
      Their entry level units are pretty close to the $200, price-point.

      Their remote management software is light-years ahead of wyse's.

    25. Re:It's like bicycles... by Antidamage · · Score: 1

      I don't get the reasoning behind not having any stepping in the gearing. Are they just too hard for bike-jocks to use? Did they take their brains out to save weight? Surely gearing lets you take off faster and reach higher speeds. The human leg has a power curve as well.

    26. Re:It's like bicycles... by hoggoth · · Score: 1

      Every problem is an opportunity.

      If it's so easy and so inexpensive (and I agree it is) why doesn't someone reading this START MAKING AND SELLING thin client systems with $150 clients and matching LTSP and Windows server servers? It sounds like a great business opportunity to me.

      --
      - For the complete works of Shakespeare: cat /dev/random (may take some time)
    27. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      The cost depends entirely on your workload and business situation. For us, we have an office of 35 people, and close on all of the PCs were in need of replacing. The workload is using a web browser, email, MS Word, Excel, Quicken and the corporate database. A $6k Windows Terminal Server, $1k per seat in Microsoft licensing and a $500 WinTerm per seat (kept existing LCD screens) - that's $1500 / seat for the upgrade, plus $6k for the server, which is about the same. A couple of things set this setup aside:

      1. Travelling salespeople can RDP into the server and work like they're at work (they love this).
      2. I have to maintain 1 machine, not 35 of them. (admins love this)
      3. Every 3 years, I just buy a new $6k server from Dell, and all 35 people get an upgrade (the bean counters love this). It comes with a 24x7 4hr response hardware support contract - so I get 24x7x4hr for all my desktops by default.

      So everyone's happy. No, it doesn't save you a huge pile of money in hardware on the first hardware cycle, but on following hardware cycles it does, and I spend far less time fixing PCs, and far more time writing code. I'm happy - I'd highly recommend it to anyone whose client workload is not hard on CPU.

    28. Re:It's like bicycles... by Sikmaz · · Score: 3, Informative

      Let me answer your points directly as someone who has been doing some POC's of thin clients in a large (40k+ environment)

      1. it simply switches the cost of the workstation maintenance to the back office as you need an immensely powerful data centre to drive thousands/tens of thousands of these terminals;
      True except it is always cheaper to manage and maintain those systems than desktops. We know per unit how much each desktop costs us to manage and maintain and we also know the same information for our big-iron boxes and Citrix farm and it came out that if we could serve 20 users per server it was a large cost savings and it helped with support. We even got savings at 10 per

      2. you still need a service desk as most requests we get are for new employee accounts and handling typical release incident;
      You need this now anyway in a large enterprise environment and you now need less deskside people and remote support is easier.

      3. people want to stay competitive and having a one size fits all typically prohibits one-offs, even if there is an obvious advantage;
      Not if you do VDI which means you deliver a full desktop to the users

      4. problems affecting a cluster will affect everyone so you still need backup PCs for critical service delivery.
      No you just have a multiple deployments and redundancy. In most large corporations most apps are client server (Regardless of if that is a fat client or web client) so there is experience in making systems redundant.

      Does it work for every user? No but it does for most, the challenges are:
      1) The initial cost of deployment
      2) User and business acceptance

      If you can solve those issues you will experience year to year cost reductions.

    29. Re:It's like bicycles... by vacuum_tuber · · Score: 1

      At least 25 years if you are talking about a diskless PC built into a keyboard and booting from a network.

      --
      Look at the bright side: there's always seppuku.
    30. Re:It's like bicycles... by mysidia · · Score: 2, Insightful

      The PC-in-a-keyboard is not a thin client--it's a full, although lightweight, computer in a keyboard.

      No. It's a fricckin thin-client. This argument is something like saying a computer monitor that has an HDMI input in addition to DVI is not a monitor, because computer monitors only have DVI/VGA inputs.

      OMG: being a computer doesn't disqualify something from being a thin client. All thin clients are computers.

      It's the lightweight part and low-cost that by definition makes the system a thin-client.

      Having a hard drive or other storage media doesn't mean it's not a thin client either.

      The actual qualification to being a thin client refers to how the machine is used, not the actual specs of the machine.

      For a machine to be used as a thin client, it indicates the bulk of the data processing and long-term storage will be handled by the server.

    31. Re:It's like bicycles... by kesuki · · Score: 1

      "I think the savings in deployment and long term maintenance of these terminal units are just an illusion."

      well for an illusion they suck a lot of power. this is strange but i can't help but say this. pandora alone in the universe forever. there.

    32. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      Your witless politics are showing. I'm comforted by the likelihood that if you, in your fast, parkable, efficient car get in an accident with me, in my SUV, I'll be the survivor and you will contribute to an improvement in the gene pool.

    33. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      I'm sorry this is totally false. Yes 64 GB of RAM and 8 cores is a niche but how many companies are supplying this to their employees? (The only place thin clients are used anyway). I agree with Eric, and in fact I came to the same conclusion after putting several months of testing and trial time into virtualizing a call center prior to concluding that at a total cost of $300 more than a standard desktop per seat, it's not worth the cost. Thin clients are a NICHE field used almost exclusively in call centers and other places where computing power isn't a necessity.

      As far as failure time is concerned, that has nothing to do with it at all. Anybody that works in IT knows that any standard machine has just as good a chance to LAST 8 or 9 years as a thin client does. Generally the thing that brings the machine down is either the HD (easily replaced) or the PSU (less easily replaced, but still pretty easy). Also it's just a likely that a thin client would be replaced with roughly the same time cycle as a PC because of how fast virtualization technology is evolving. Today's model is not going to be compatible with technology a year from now, and you can bet WYSE and others are doing that on purpose.

      These companies need to realize that the market is not going to grow at all until thin clients come down in price to around $100-200. $350-400 is literally a stones throw away from the $450 units we were purchasing for full out desktop units. The only way this market will thrive is by them realizing that these clients are using for a browser and nothing more, who want's to spend $350 + $300 in licensing for a browser?

    34. Re:It's like bicycles... by CAIMLAS · · Score: 1

      On the other hand is WYSE is only selling low volumes of thin client machines (because most customers are buying regular desktops/laptops/notebooks/whatever), then they have to sell them at a higher price to recoup development costs, costs of setting up production lines, costs of buying components in smaller volumes, marketing costs and so on.

      Nonsense. Who working in IT hasn't looked at their computing infrastructure (regardless of whether it's 10 or 10,000 workstations) and thought: gee, it sure would be nice to use thinclients instead of these large, hot, noisy, and relatively expensive desktops.

      After all, you can buy a (very capable) beagleboard for $150. It's a small-number production, to be certain. It's definitely smaller production than anything WYSE does.

      The "cost" of a thinclient, to the developer,is negligible: the hardware is dirt cheap, the protocols are fairly static, and licensing is likewise probably fairly cheap. The reason WYSE charges what they do, when it comes down to it, is demand: there aren't really all that many providers of inexpensive thinclient hardware. It's not a competitive market, in part due to continued drops in the "PC" market costs, but also because WYSE (and others) can still make a profit at low volume. Since product reliability (and general QOS/QA) tends to suffer with higher volume, naturally they're staying at lower numbers. (The curve to high-volume profit is likely not steep enough to justify the higher volumes.)

      Without looking into it too much, I suspect the big problem is licensing. I know that as long ago as 4 years ago there was a company which made "thinclients" which would connect to hacked-up XP terminal services - 2 per XP machine, I seem to recall. They cost under $100 each and had a fair number of capabilities - certainly enough for your average user. They could even do video over the connection better than the 'stock' terminal services. (Anyone who bought such a thing would, of course, void the license on XP by using the product.)

      Honestly, there are enough inexpensive ARM based boards available now, I hope someone writes an "open" firmware for such boards which is simply a thinclient ROM. That'd be pretty awesome.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    35. Re:It's like bicycles... by Toonol · · Score: 2, Informative

      So why are thin clients so expensive?

      My gut feeling is because the people shopping for them are demonstrably suckers. If you have a customer that's willing to spend money based on ridiculous fashion trends, why not convince them that an expensive specialty thin client is magically better than a cheaper, more useful, low-end pc?

    36. Re:It's like bicycles... by dasunt · · Score: 1

      Though not for the same reason. You get a complete PC for less than a thin client because complete PCs are made in insanely high volumes compared to thin clients, which are a niche item.

      Actually, isn't that similar to bicycles?

      The typical big box discount retailer, such as Walmart or Target, orders bicycles in high volume. The bicycles are made for a consumer who may ride only a hundred miles in the lifespan of the bicycle, and wants to pay less than $200.

      A $800-$1000 bicycle from a shop may not have any more features than a Walmart bike (and frequently has less, since a lot of those bikes won't have a full suspension), but the components are higher quality, and, with regular maintenance, are designed for thousands upon thousands of miles.

      So, to review, a Walmart bicycle is a mass market item, sold in high volumes, but at low quality.

      A bicycle shop bicycle is a niche item, sold in low volumes, but the quality is much higher.

    37. Re:It's like bicycles... by BitZtream · · Score: 1

      Not really, the more you pay for a bikini, the more everyone else gets :)

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    38. Re:It's like bicycles... by CAIMLAS · · Score: 1

      Well, one gear ratio, then. And only one gear sprocket, as the other one is a drive sprocket. Or no gears, depending on your definition of gears (ie you'd need a 2nd geared sprocket, with a different power ratio, to constitute 'gears'). :)

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    39. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      You really don't get the point. If boring old PC's are being put together by the truckload, that doesn't mean making small quantities of thin clients will be equally cheap. Not even if they use the same components.

    40. Re:It's like bicycles... by Awptimus+Prime · · Score: 1

      Yes, but do you want to be running around supporting a 1,200 system deployment of the shittiest model Dell with an assortment of different motherboards, drives, lots of fans, and questionable build quality or 1,200 Wyse terminals that are identical in every fashion with no moving parts to fail?

      Sure the prices get on up there for a good thin client, but it scales similar to going from GMA video to a Matrox or ATI dual head video card when comparing the nicer models to the most basic ones.

      I guess if your IT people work for free, the Dell would be a better choice. Really, anyone wanting to put white-box or shitbox solutions in place of a proven thin client should not be in the position to make such decisions.

    41. Re:It's like bicycles... by Migraineman · · Score: 1

      Thanks for the product link. I think I just found my new MAME machine. Might not be grunty enough to handle the newer machines, but it should be plenty for old-school games.

    42. Re:It's like bicycles... by kFiddle · · Score: 1

      I agree with you that a thin client can be defined by its function, and so any PC can act as a thin client. However, I would say that the industry definition of a thin client is a diskless workstation. Do a quick google product search (http://www.google.com/products?q=thin+client&aq=f) for "thin clients," and check this yourself. This is specifically tied to the fact that companies that use thin clients have moved all storage to a server farm in order to cut costs. Local storage does not make sense in this model, as it would increase the overhead that thin clients are intended to reduce.

      It's the lightweight part and low-cost that by definition makes the system a thin-client.

      That is absolutely wrong. You're probably thinking of nettops, which is another class altogether. Your confusion arises because nettops offer "less," just like a thin client does.

      --
      In the world of kung fu, speed defines the winner.
    43. Re:It's like bicycles... by Zappy · · Score: 1

      Iff you don't mind the GPL violation the hardware is ok.

    44. Re:It's like bicycles... by rbcd · · Score: 1

      Single speed provides a significant weight saving. Most of the bike disappears. A much simpler rear hub, no cassette or chainrings, no dérailleurs and no rear brake. You end up with so little bike that there is very little left that can fail.

    45. Re:It's like bicycles... by shaitand · · Score: 1

      People buy those oversized SUV's because they have a herd of four or five brats, a load of groceries, and all the toys and gear required for the activities of said brats to haul on a single outing.

      A van would also serve this purpose but even a mini-van is bigger than an SUV.

      People also buy them because it gives you some of the transport, hauling, and four wheel drive capabilities of a truck but in a package that doesn't scream 'red neck hick' and looks more sleek and consumer friendly. But most buy if for the rugrat factor.

    46. Re:It's like bicycles... by reub2000 · · Score: 1

      A derailer is very complex system that is completely exposed to the elements. Dirt gets thrown in it's direction and it's likely to get banged around. It has to move smoothly and quickly and be very precise. The cable that controls it also has to work flawlessly.

    47. Re:It's like bicycles... by reub2000 · · Score: 1

      Often times these feature are crappy things thrown in to cover up low quality. It's like selling a cell phone with a 5MP camera and a crappy lens. Now, somebody putting the extra research would realize in this case that suspension saps energy from peddling. Of course, if you plan on riding on rough terrain, you could always find mountain bikes in that price range which come with suspensions much more advanced than those used in walmart bikes.

    48. Re:It's like bicycles... by lordtoran · · Score: 1

      Ah, the good old Atari ST.

      --
      Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
    49. Re:It's like bicycles... by Daengbo · · Score: 1

      But it doesn't come with a hard drive or SSD in the default config ($99). It has expansion capability if you want that. There's no assembly required to PXE boot. You just attach this to the network and go.

      In other words, it's a thin client out of the box. It fits the submitter's requirements. I think you misunderstood something about the Gecko Surfboard.

    50. Re:It's like bicycles... by dbIII · · Score: 0

      it simply switches the cost of the workstation maintenance to the back office as you need an immensely powerful data centre to drive thousands/tens of thousands of these terminals

      Which in some cases means you save a lot, especially when you only need to upgrade a few servers instead of a few hundred desktop machines. Malware and security is also an issue. For example, lawyers may have clients that insist on very high levels of security to prevent employees taking sensitive information out of the building and you can either put epoxy in all the USB ports or have thin clients. You can have whatever policy you like but even if you tatooed it on employees there are many that would just not understand that there is anything wrong with plugging their iPod into any computer anywhere - you need some sort of physical prevention method if you have such a policy.

    51. Re:It's like bicycles... by TakeyMcTaker · · Score: 1


      The actual qualification to being a thin client refers to how the machine is used, not the actual specs of the machine.

      This is exactly right. Further, the thin-client isn't limited to a hardware concept. Most thin-client implementations start in software, not hardware -- VNC, RDP, and Citrix are good examples. I would argue that netbooks and nettops are a full replacement for old thin-client hardware concepts, both in terms of function and cost. Local storage can mean local cache, not just offline use.

      In any case I don't see the future as cloud vs. desktop. I just see a balance, where the cloud makes for easier sharing and dynamic offloading, and the desktop basics (like storage) allow for offline operation and enhanced compression techniques when the cloud is necessary.

    52. Re:It's like bicycles... by mysidia · · Score: 2, Interesting

      No.. I think some players in the industry just want to create confusion, and make you think a thin-client is a specially-packaged "diskless workstation" for their own benefit.

      First of all, the term thin-client came way before there were any products named thinclient.

      It's true that many packaged thinclient products today will be diskless, or will utilize compact flash for local storage (Just like that PC in a keyboard product, by the way, with the SD/SDHC card option), and include curious features like smartcard readers.

      Anyways: companies that sell products for implementing thin-clients want to convince you that their product is somehow different (or better) than using an old ordinary PC, so they can differentiate their product in the marketplace.

      IOW: They want you to believe their product is different (even in ways that it is not). In the case of thin clients: they want you to believe their product has a lower TCO; they would have you think it will (A) last longer, not be likely to fail, (B) use less electricity, (C) be more secure, than using generic thin-client hardware.

      They will try to convince you that using no local disks or using CF instead, somehow makes the product better, or make it last longer, while costing less to maintain, than anything using something capable of being a PC. Even though these claims have not really been shown to be true.

      Otherwise you would just use uber-cheap PC hardware, instead of paying the extra premium for a brand-name "packaged thin client".

      Unplug the power cable to the HDD if you want, slap an internal USB stick, or PXE boot mod, and call it a day.

      In other words, the motive of companies that speicalize in thin-clients is inherently self-serving, they want to warp the industry's perception of what a thin client is.

      The truth is... when you aren't talking about solutions packaged by major vendors:

      Not all thin clients have to be diskless.

      Not all thin clients have to be off-the-shelf products "designed originally to be thin clients"

      All ultra light-weight PCs are good candidates, especially units that don't need fans for cooling or mechanical storage (e.g. systems that use SD/SDHC, CF, or SSDs, are great candidates for quiet low-power thinclients).

      Sometimes a local HDD may be used to boot a thin client, or you may use PXE boot or a simple $5 USB thumb drive to startup the thin-client (despite any existence of local disk).

      In some cases it could be simply read-only storage to load a ramdisk from. In other cases, there could be local caching of various things.

      HDDs don't drop dead that often -- if you execute power management well, and use HDDs only to boot the thin-clients, they will be spun down most of the time, anyways, extremely low mechanical wear, and you can expect 10+ years on average, easily.

    53. Re:It's like bicycles... by characterZer0 · · Score: 1

      Track bikes do not have a front brake either. It would be unsafe for anybody to be able to stop that fast when riding so closely on a track.

      --
      Go green: turn off your refrigerator.
    54. Re:It's like bicycles... by drinkypoo · · Score: 1

      A full suspension mountain bike can be expensive as you want it to be.

      Owning one myself (Haro Xsomething with Fox shocks) and having priced far more, I well know that to be true. I got mine used, of course, with some scratches and in slight need of a fork rebuild. On a good hard ride I end up having to re-pump, so that's high on my list of things to do. But at the same time, you can get a quite fine example that will take you all kinds of places for less than what a competitive racing bike will run. And let's face it, with enough customization, anything can cost almost anything.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    55. Re:It's like bicycles... by Dan+Ost · · Score: 1

      You've got it backwards. SUVs categorically have the highest fatalities per mile driven (not counting motorcycles). In layman's terms, an SUV driver is far more likely to die in an accident than a non-SUV driver.

      It might be true that an SUV driver has a better chance of surviving an accident, but that advantage is more than offset by the SUV's increased risk of having an accident in the first place.

      And while it might seem unintuitive at first, the car's improved ability to avoid accidents in the first place means that a disproportionate amount of SUV accidents will be with other SUVs, negating any size advantage you think you're gaining by driving an SUV in the first place.

      You're right, there is a selection mechanism present here, but not the kind you thought it was.

      --

      *sigh* back to work...
    56. Re:It's like bicycles... by killmenow · · Score: 1

      No, the savings are not illusory. The primary savings advantage for organizations (like the one I work for, as an example) is in LABOR. You know, the single most expensive item of almost every business in the world. We have 20 remote branch office locations. We have ZERO IT staff in any of those remote locations. Because we have ZERO PCs to get f*ed up by the users in those branch offices. Yes, you can lock down desktops so they can't install crap and mess them up. But it requires a lot less IT presence to support a couple dozen "thin terminals" that have no CD drives, no floppy drives, NO MOVING PARTS, and so fewer parts to possibly fail than the alternative with desktop PCs.

      I imagine if you look at the "TCO" of desktop PCs deployed in an organization like ours verses the thin clients we use, the difference in equipment and software licensing costs is likely negligible either way. Where thin clients come out on top is in overhead spending on labor.

    57. Re:It's like bicycles... by kFiddle · · Score: 1

      I would agree with you on this. I hinted about some of these points in my original post, but I think you've hit the nail on the head as far as answering the original submitter's question. The "thin client" term is clearly being abused to jack up the prices.

      All disagreements over terminology aside, I think our (or at least my) frustration lies in the fact that we think we should be able to find a plain diskless workstation with lower specs for much cheaper than they're currently being sold. "Thin client" is the term we use when we google because it yields the most accurate results as far as hardware to what we had in mind. (but no one disagrees about buying a cheap nettop or other variation).

      --
      In the world of kung fu, speed defines the winner.
    58. Re:It's like bicycles... by jon3k · · Score: 1

      Clearly spoken like someone who's never managed a large install base of workstations.

    59. Re:It's like bicycles... by jon3k · · Score: 1

      We use IGEL here. The entry level isn't bad, but once you start adding features the price starts climbing. Although their licensing model is really nice and their management software is great.

      The sad part is, we can basically get a full blown desktop PC from HP for the same price. Although I'd much rather manage a couple thousand thin clients than Windows XP desktops.

    60. Re:It's like bicycles... by jollyreaper · · Score: 1

      > The more you pay for a bicycle the less you get? What on Earth are you talking about?

      It works exactly the same for bikinis, really.

      But it's soooo worth it.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    61. Re:It's like bicycles... by vacuum_tuber · · Score: 1

      No, I recall regular commercial offerings of self-contained PCs in keyboards, diskless, for network boot, in the second half of the 1980s. Nothing to do with Atari or game stuff.

      --
      Look at the bright side: there's always seppuku.
    62. Re:It's like bicycles... by Anonymous Coward · · Score: 0

      PC in a keyboard has been around for a while. In fact I have a TRS-80 Model 1 right here...

  4. What did you expect? by Anonymous Coward · · Score: 0

    Buzz is expensive and somebody's gotta pay for it.

    1. Re:What did you expect? by AHuxley · · Score: 1

      Yes reinventing the past is lucrative and so much fun.
      Cheap Thin Clients are cheap in terms of ... ?
      The big box that they connect to?
      The applications?
      The end users 'box'?
      This is the new gold rush and your it :)

      --
      Domestic spying is now "Benign Information Gathering"
  5. Nettops? by sznupi · · Score: 4, Interesting

    http://en.wikipedia.org/wiki/Nettop

    Comes assembled, quite cheap, can drive usual resolutions, often Atom/x86 compatibility...typically has few redundant things though, like HDD; but that might be useful, together with x86, in case you change your mind.

    --
    One that hath name thou can not otter
    1. Re:Nettops? by erroneus · · Score: 1

      I find this interesting. As I was reading through this page, I see that many of the devices listed use Windows. How is this accomplished over a network? Using some sort of network based block interface like iSCSI?

      Running Linux is well practiced using NFS as the means of mounting exports and allows many machines to use the same files on a single server. Windows, on the other hand, wants exclusive access to whatever block device is being used to host the operating system. Would a wide deployment of such devices under Windows require massive machine disk image files on a server? Or worse, massive machine disk partitions on a server?

    2. Re:Nettops? by temojen · · Score: 1

      They have HDDs or SSDs. You'd PXE boot them to load the windows image, then run off local store.

    3. Re:Nettops? by erroneus · · Score: 1

      That sounds like it would take too long. I wonder why Microsoft hasn't attempted to work in this market? It would make administering Windows machines much easier and keeping machines patched and operating reliably much easier as well.

    4. Re:Nettops? by pnutjam · · Score: 1

      either terminal services, or some sort of virtual desktop solution, vmware and citrix both have them, as do other companies.

    5. Re:Nettops? by Rudeboy777 · · Score: 1

      My thought exactly, let me link you to exactly what the OP is asking for for 200 bucks:

      http://www.newegg.com/Product/Product.aspx?Item=N82E16883103228&Tpk=aspire%20revo

      Don't need the hard drive? Who cares??

      --

      From hell's heart I fstab at /dev/hdc

    6. Re:Nettops? by temojen · · Score: 1

      Places that are set up this way normally only PXE boot the build process once, then just boot off the hard drive. Once the image is loaded and booted, the machine is part of the domain, and patches are sent out automatically. usually (not always, sadly) the user home dirs are on the server anyways, so if a workstation dies or needs to be re-imaged you just pop a new one in. Sure, maybe it's a 2 hour service call, but it's way better than non-managed systems.

    7. Re:Nettops? by funnyguy · · Score: 1

      Nettops with network boot are a good choice. The reason Thin Clients are more expensive is they usually have an expensive, flash based disk inside. Thin clients also often include a Windows XP embedded or some other tweaked OS. It isn't like 20 years ago when they were just XTERMs.

      Also, you are likely paying a tax for the thin client management software that accompanies most thin clients now days. This software allows you to do things like install applications directly to a thin client's flash. Not so thin anymore.

    8. Re:Nettops? by jvin248 · · Score: 1

      Best options for most companies using less than a hundred thin clients is to just get auctioned-off pc boxes and strip them down to basic thin clients (remove all drives). A few years ago I got a pallet of 7 year old pcs for $5 each. Another option is to go to gumstix.com and grab their basic computer on a stick - $130-$160. Enough to run LTSP clients (with some Ram increase to 128MB). Probably better for larger deployments to get OEM large lot pricing.

  6. Cart before the horse? Use a PC if its cheaper! by Anonymous Coward · · Score: 3, Insightful

    To me the compelling aspect of virtualisation for the desktop is to be able to use a standard computer to access specialised systems, such as CAD (check out RHEV with SPICE), legacy software or test environments. At work our conference room PC's are actually normal PC's that connect to a 'conference' room virtual machine, it allows instant display of said specialised systems without effort.

    AB

  7. In the queue... by Goffee71 · · Score: 1

    ...waiting for a skinny latte and no-meat salad?

    --
    If he's the Walrus then can I be a penguin please?
  8. 1996 called, by type40 · · Score: 4, Insightful

    they want their "future of desktop computing" back.
    Seriously, I remember talking with some IBM engineers back in high-school and they were so certain that thin clients were the hot new thing that would change the face of computing.

    You want to know where to buy thin clients? Goto www.dell.com and buy the cheapest POS they have with a fast network card. Thin clients will always be a more expensive niche player to the PC. After all what is a thin client? A PC with no local storage that can only work if it has a network connection.

    --
    "You can see I know very little about pimp policy." George McGovern.
    1. Re:1996 called, by timmarhy · · Score: 4, Insightful
      err no they aren't. you can buy an entry level thin client for $99.

      thin clients never caught on because not enough MCSE's get taught about them and the CIO doesn't like all the restrictions it puts on his playing of porn.

      in environment's where things like CAD are used thin clients aren't a viable option (yet), but for a lot of businesses it's by far the best way to go.

      --
      If you mod me down, I will become more powerful than you can imagine....
    2. Re:1996 called, by Anonymous Coward · · Score: 0

      Actually for most businesses it's probably not the best way to go but the cheapest for IT. If you look at it from the client's viewpoint - why should I rely on IT to provide me with a service that is limited by IT and generally aimed at how IT see the need? Or to put it another way, if you are old enough do you remember Green Screen computing?

      It may be easier to support; it may mean greater security; but if it doesn't offer enough stuff that those pesky users want then it will be resisted and then subverted. IT Departments cannot impose there will on their clients in the long term.

    3. Re:1996 called, by peragrin · · Score: 1

      Fine but why does the secretary, accounting, and the boss need full blown computers? When all they use is MS office, and a web browser?

      --
      i thought once I was found, but it was only a dream.
    4. Re:1996 called, by Anonymous Coward · · Score: 0

      Because you have to pay $149 for one TS Client Access License. Additionally not all MS Office licenses can be used in Terminal Services environment.

    5. Re:1996 called, by Keruo · · Score: 4, Informative

      The problem with thin clients isn't the lack of knowledge. It's the break-even point.
      In order for thin clients to become more affordable than deploying standalone workstations, you need to deploy atleast 200 of them, and 200 workstations rules out a lot of businesses.
      Cost of licensing and server infrastructure is really the problem, not the cost of thin clients themselves.

      --
      There are no atheists when recovering from tape backup.
    6. Re:1996 called, by drinkypoo · · Score: 1

      Accounting needs different machines for legal reasons; unfortunately they're usually windows, which throws any theories about it being for security out of the window. The boss should have his own machine for the same reason; it shouldn't run windows either, and for the same reason. Bosses often play with other software when they should be doing real work, e.g. MS Project.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:1996 called, by Hognoxious · · Score: 2, Insightful

      but if it doesn't offer enough stuff that those pesky users want then it will be resisted and then subverted.

      They're supoosed to get what they need, not what they want. The don't need dancing pigs.

      IT Departments cannot impose there will on their clients in the long term.

      Finance can (we're using this because it's cheaper), Legal can (installing unauthorized software puts the company at risk) and HR can (if you don't like it, then get out).

      IT just needs to convince them.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    8. Re:1996 called, by ThePhilips · · Score: 2, Insightful

      It may be easier to support; it may mean greater security; but if it doesn't offer enough stuff that those pesky users want then it will be resisted and then subverted. IT Departments cannot impose there will on their clients in the long term.

      Or in other words, the IT becomes "single point of failure." While PC can run without any infrastructure or IT involvement.

      That has been always the biggest argument against thin clients.

      Plus few people actually want to work on the thin clients, so you rarely see any grass root support for them coming from employees. And "better PC" is often used by management as an incentive for subordinates too.

      --
      All hope abandon ye who enter here.
    9. Re:1996 called, by Anonymous Coward · · Score: 0

      And when you do have 200+ workstations, you will find a whole range of other reasons why it is not practical.

      1. The need for portable computers for an ever growing part of your workforce.
      2. The bigger the company, the bigger the chance you use some legacy software that really does not play nice with citrix, etc.
      3. Some of those do work but require admin access.
      4. There are always people who need some non-standard, specialized, software. Those are usually not tested against citrix, you will have to do it yourself.
      5. Or it comes with USB dongles.
      6. applications (websites) requiring specific java versions.
      7. Flash, Silverlight. There will be at least 1 business related website that requires these.
      etc, etc.

    10. Re:1996 called, by greenreaper · · Score: 2, Funny
    11. Re:1996 called, by gedhrel · · Score: 3, Informative

      The organisation I work at (it's a university) spends about a million quid a year because people fail to turn off PCs overnight. The running costs of your cheap Dell POS are much higher; the power consumption too.

      For clerical and administrative staff, we can put 7-14 virtualised desktops onto a single box/blade - more with non-whole-stack virtualisation or terminal services. We put our heat generation in a few places, we do get better utilisation. We also export pictures of our data to users, not the data itself, which is quite a bonus.

      The downsides are what you'd expect: mostly, we have fewer spindles to deliver storage to the desktops (this is the biggest issue we face, I think); multimedia is okay-ish; for heavy computational users there aren't really gains to be had.

      It's certainly got its place. Anyone selling you a "one size fits all" for your organisation probably doesn't understand your organisation, but this isn't not a completely incredible approach.

    12. Re:1996 called, by RKThoadan · · Score: 1

      Because if you live in Word and type 90+ words per minute most thin clients can't keep up. I've seen thin clients rolled out to all the executive assistants in a medium size corporation. It wasn't pretty.

    13. Re:1996 called, by mjpaci · · Score: 1

      MS Project isn't software. It's a religion.

    14. Re:1996 called, by Clover_Kicker · · Score: 3, Insightful

      Or in other words, the IT becomes "single point of failure." While PC can run without any infrastructure or IT involvement.

      Eh?

      Without email, files on the network, network printers, whatever corporate apps you have, internet... what good is that PC?

    15. Re:1996 called, by poetmatt · · Score: 2, Insightful

      you missed one group: users can fight it (bitching from every group in the company).

      It's all about the compelling argument. whoever makes it, wins. that's standard business practice anyway.

    16. Re:1996 called, by basscomm · · Score: 2, Funny

      Or in other words, the IT becomes "single point of failure." While PC can run without any infrastructure or IT involvement.

      Eh?

      Without email, files on the network, network printers, whatever corporate apps you have, internet... what good is that PC?

      Solitaire.

      --
      http://crummysocks.com
    17. Re:1996 called, by peragrin · · Score: 1

      then it was rolled out wrong. with the wrong network, wrong software choice, etc. as I have seen hundreds of thin clients connected for programmers, And not only was their no lag, but this was in 1996.

      Using windows as a thin client is like driving a Hum Vee to work in a downtown city building. Sure it works, but damn is it overkill.

      --
      i thought once I was found, but it was only a dream.
    18. Re:1996 called, by petermgreen · · Score: 1

      The organisation I work at (it's a university) spends about a million quid a year because people fail to turn off PCs overnight.
      Could you tell me what data and assumptions were used to calculate that or are you just taking someone elses word for it?

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    19. Re:1996 called, by Monkeybaister · · Score: 1

      Without email, files on the network, network printers, whatever corporate apps you have, internet... what good is that PC?

      Everyone can set all that up at home, it'll just run itself!

      Right?

    20. Re:1996 called, by Anonymous Coward · · Score: 0

      It isnt completely unrealistic. The company I work at claims that over 1700 stores, simply having the monitors go into standby after a half hour is saving them $500k/yr in energy costs. The only reason the computers dont turn off at night is that many of the stores have a night crew that needs access to a system to locate product to stock it when its something they havent seen before. The crappy part to all of that though is also the funny part. Someone "suggested" it in the company wide idea program. Said person got $1000 on his check as a bonus. Someone else recommended zippers instead of buttons to cut costs on people replacing vests, and she got $5k. All in all, the vests cost more now, and we replace them just as often for being dirty and unprofessional, so in all she didnt save a huge value to the company.

    21. Re:1996 called, by Anonymous Coward · · Score: 0

      Or maybe it's because the CIO likes to have the option to use the computer on the plane and in other places with no broadband.

      The thin client is only a good idea if your device is meant to be more or less stationary.

    22. Re:1996 called, by Attila+Dimedici · · Score: 1

      If they are hooked up to the network there are several utilities available that can be used to automatically shut down all of the computers on the network at a pre-set time.
      I worked for a company that could have used thin clients instead of PC's. The problem was that the cost of setting up thin clients for all of our users cost more than buying and deploying the cheapest PC's we could find. The cheapest individual thin clients we could find cost about 25% less than the cheapest PC's we could find, once we paid for the Server the total cost was about 50% more than just buying a PC for each of the users. Now this was a small company, but it should theoretically be possible to do it for at least the same price as individual PC's

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    23. Re:1996 called, by tenco · · Score: 2

      Edit a local file. When files on the network become available again, import from your local file into a file on network. Was it really that hard? I know, a reason to procrastinate in case of network failure just went out the window. And license servers are a bad idea anyway.

    24. Re:1996 called, by 1u3hr · · Score: 1
      Because if you live in Word and type 90+ words per minute most thin clients can't keep up.

      And I remember speed demon touch typists using Unix terminals back in 1980. No lag. How much eye candy does the latest version of Word need?

      An 8086 PC-XT at 3.77 MHz could "keep up" with any typing. Now with literally a thousand times the speed and RAM, performance is no better, thanks to bloat.

    25. Re:1996 called, by SanityInAnarchy · · Score: 1

      We also export pictures of our data to users, not the data itself, which is quite a bonus.

      How so?

      Last I tried this, I found that for the vast majority of things you'd like to do, sending a picture of the data (even a compressed picture) is likely to be much larger than the data itself. The Slashdot homepage is 108 kilobytes. A PNG image of the Slashdot homepage was 220 kilobytes, and even when compressed with 'pngcrush -brute' (which takes something like 30 seconds on my machine) only gets it down to 173 kilobytes.

      So even if you have unlimited time and power to compress the image, if you're going to deliver it perfectly, it's going to be 65 kilobytes more -- and that's just for what's visible within the frame. If I scroll, even if you use some sort of brilliant delta-compression, you're adding to the count -- again, compared with 108 kilobytes.

      It's hard to imagine what kind of file is going to be larger than a picture of that file.

      Maybe I'm missing the point? Maybe it's some sort of poor-man's DRM -- you don't want someone to be able to just walk off with the original data, but it's not as bad if they walk off with a screenshot?

      --
      Don't thank God, thank a doctor!
    26. Re:1996 called, by Phil_At_NHS · · Score: 1

      Two simple answers to that question. 1) If my network connection goes down, on a PC I still have a Word Processor, Spreadsheet, etc. There is still SOME work that I can do. On a thin clent, I have a brick. 2) A small corporate setup will have certain things that users rely on, like email, word processing spreadsheets, corporate databases. A setup baseds on a thin client will also have the servers for those thin clients. If an email server goes down either way, users have no email. If a word processing program goes bad: At My company, with PCs, ONE of my users is SOL, until I get it fixed. If the world is ending, he goes next door and uses a coworkers machine to get his job done. At my wife's company, EVERYONE is SOL, until the the problem is fixed, and there is no alternative. Yes, this happens at all companies with SOME things, like the corporate database. If the Oracle machine dies, everyone is out of luck. However, with a thin client, that is true about EVERYTHING, every application, every bit of data, etc. At A 60 user company, My assistant and I ARE the IT department. My Wife's is off site, and the number of times I hear about the company being brought to a complete standstill, or some process being halted, is ridiculous. The problem is always either, something went down like an Application server, so no one can log in and do anything, or something broke with an application, and it took them an hour and a 1/2 to fix it. That hour and a half at MY company this stops 1 1/2 man hours of processing. At her company, it stops 45 people times 1 1/2 hours of processing. I could never see operating that way.

    27. Re:1996 called, by Anonymous Coward · · Score: 0

      As the OP stated (in his OP). the cheap thin clients, frankly, suck. He was asking where all the competent ones are so expensive. We went through the same thing; purchased an entire system, only to find that the cheap thin clients were horribly slow, and having already gone through budget approval, purchasing, and deployment of the back end, we were married to the system and forced to "upgrade" to the better-performing clients at over twice the price.

    28. Re:1996 called, by couchslug · · Score: 1

      That PC is plenty handy when you can produce what you need for use in the immediate area.

      For example, USAF exercises routinely shut down local networks to see how workcenters cope.

      Those with local copies of important files can continue with mobility processing (scheduling the movement of people and gear), keep printing manifests, HAZMAT paperwork, and so forth. There are plenty of local printers, and if needed we could grab a cable, move the network printer, and run it locally. Unclassified data can be moved by sneakernet if necessary. (So of course can classified, but with more safeguards.)

      A system should be designed for limited use without LAN connectivity unless there is a compelling reason (security) and that reason is more tolerable than the consequences of shutdown. A Scud destroying the network operations center isn't common in civil life, but backhoes lurk waiting to strike...

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    29. Re:1996 called, by Vancorps · · Score: 1

      With traditional thin clients you were right, with XenDesktop or most VDIs out there now you can even watch full 1080p video provided the thin client supports it. CAD is easy to do inside a virtual desktop. I'm currently in trials with XenDesktop and it's pretty terrific, users also like being able to just go to their phone and login to their corporate desktop as well. They have access to their stuff whenever and wherever they want either with a thin client or with a traditional desktop. Support costs are a lot less now especially since for my trial purposes at least, XenDesktop is free.

      The limitations of the past are gone, with USB pass-through you can use your webcams or connect almost any proprietary device you've got. I haven't found any hardware yet that the thin client can't pass to the VM. This is more of a logical next step, it won't end regular computers for certain applications but the vast majority of office workers out there don't need special hardware. For me, the beauty of the whole thing is the simple ability to add physical hardware on the back-end to boost performance so I don't have to upgrade all the thin clients because an application has become sluggish. This also means if physical hardware dies on the back-end the users don't notice and I just replace the one server. This is nice compared to all the times I've had hard drives fail on me on office computers. All the support calls that their computer has slowed down disappear. Thin clients being without moving parts is a big benefit, they will indeed last much longer and there are only limits means of which the user can screw up their access.

      I'm deploying a 4 monitor 10zig rig to a test group of people that need high resolution work. If it passes their tests then I'll go company wide with it. A VPN connection and a Citrix receiver is all that is needed for users to then have their full corporate desktop experience whether they are in the office or across the pond on vacation. Most of them seem to like the idea and with location-based policies I can control security accordingly. Things like USB pass-through I probably wouldn't want enabled for all remote users for instance.

      I'm sure there are downsides to virtual desktops, I haven't encountered them yet though. I'd love to hear about actual limitations as I'm in the process of identifying pros and cons, right now I haven't really seen any cons. New user provisioning is a snap as you just clone from a template and you're done. Makes remote administration much much simpler as I then have easy access to the console of the VM which means keeping everything up to date is easy. Regular snapshotting makes backups a snap.

      Seems like most people have feelings about thin clients dating back to when they were complete bullshit with WYSE green screens not able to do anything on their own. Modern thin clients have a sweet of utilities on the machine itself so if you enterprise infrastructure fails you, you can also use the onboard office suite and web browser. Building back-end infrastructure seems much easier to me than ensuring all end-user machines are well maintained and replaced as warranty status demands.

    30. Re:1996 called, by closetpsycho · · Score: 1

      I believe it's more sending a copy of the data, and only letting users modify that copy as opposed to the stored data. So yeah, missed the point a bit. This makes it so users can only wreck the copy that they have, rather than the database.

    31. Re:1996 called, by Vancorps · · Score: 1

      And what about the cost of replacing the workstation once its off warranty? Or when the hdd breaks? Or the site visits to clean up all sorts of software messes users get themselves into? Those costs put it back into the court of the thin client since they have no moving parts. Keep in mind that shutting off a computer over the network is rarely a good idea as users probably left something open and of course didn't save!! Thin client side you shut off the thin client and the VM is humming away in the server room where it uses more efficient power at least here in the U.S. at least.

      And of course I can power down my server hardware during periods of low activity as well with monitoring software powering up more hardware as needed. Naturally you would start up your daily required hardware probably two hours before the morning rush but you end up saving a ton of electricity. Combine all that with a DR site using different SAN hardware and you have a highly available infrastructure that is more flexible for users, not less. Thin client notebooks are great for the users that are away as well as it will cache a local copy of the image. It's not super fast that way but you can still work on that office document or connect to hotel wifi to browse the web.

      With workstation hardware failures causing downtime for users I don't see how it's possible for all but the smallest shops to find it cheaper, the cost of the time to troubleshoot alone over the course of a year easily equals the cost of a server or two, nevermind the fact that a server failure doesn't result in downtime for any users since it's all in a pool, the vm will just be migrated to hardware that is working, automatically.

      I think a lot of people are just afraid of giving up local control and I understand that, it's the same reason that I tread slowly with cloud services. You make sure you can handle your critical services on your own and use the cloud to scale out. At least that's the approach I've taken, I can handle quite a bit of usage on my own and it's only a few times a year that I have a few orders of magnitude more usage. For those times the cloud is potentially the perfect solution as I only have to rent out VMs for the length of time that I need them.

      There are only a few applications these days where a thin client isn't appropriate just like there are a few applications in the server world that don't make sense to virtualize. My security servers recording 5megapixel resolution are far too IO intensive for it to make sense to virtualize for instance.

    32. Re:1996 called, by Vancorps · · Score: 1

      The thing you don't quite get is that a picture is the same size for a given resolution. Yes it will go up and down depending on how many structures are in the image but you have an upper limit. Contrast that against the need to download that 1gig powerpoint presentation over the Internet over ATT 3G spotty speed and you quickly realize how much faster it is to just transmit the pictures of what you are seeing. This is why RDP is much faster over the Internet than directly managing the machine.

      Now most Internet services can handle the bitmap transfer. Local software will cache bitmaps so common things like the start menu aren't redownloaded, this means that image size drops the more you use it.

      I don't believe this is a more secure approach, but it is definitely faster. Scrolling only requires downloading enough of the screen to cover the new info to be displayed, usually the process of scrolling gives the machine enough time to download it. Smooth scrolling isn't always perfect, but over a LAN or at least a decent Internet connection it's great, it will also tolerate temporary disconnects so you rarely ever lose your work.

    33. Re:1996 called, by BitZtream · · Score: 1

      1970 called, ditto for everything you've said.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    34. Re:1996 called, by SanityInAnarchy · · Score: 1

      I believe it's more sending a copy of the data, and only letting users modify that copy as opposed to the stored data.

      Erm, what?

      First: How can this not be done with a Samba mount? And second: How can this be done at all with an RDP connection?

      --
      Don't thank God, thank a doctor!
    35. Re:1996 called, by SanityInAnarchy · · Score: 1

      That's actually a good point... sort of.

      Contrast that against the need to download that 1gig powerpoint presentation over the Internet over ATT 3G spotty speed

      Well, first of all, this only makes sense when we're actually talking about that 3G connection...

      But also, consider that the PowerPoint document can be cached locally, and even worked on offline. Also, any intelligent network filesystem should allow you to transfer pieces of a file, so if you're writing software that could conceivably have to deal with files that huge (seriously, I don't think I've ever seen a 1 gig PowerPoint presentation), you can write it to only load what's needed for the moment.

      So, sending pictures makes sense in that it's a constant, predictable rate, even though it's going to be more on average:

      Scrolling only requires downloading enough of the screen to cover the new info to be displayed, usually the process of scrolling gives the machine enough time to download it.

      Yet it's still additional information -- if you scroll down an entire screenfull, you've at least doubled the amount of information needed -- and the original picture of a webpage is very likely larger than the entire contents of that page as HTML.

      --
      Don't thank God, thank a doctor!
    36. Re:1996 called, by Belial6 · · Score: 1

      It always amazes me when system admins suggest that the company spend huge sums of money to keep good employees instead of spending dramatically smaller sums of money on supporting them using the PCs already on their desks.

    37. Re:1996 called, by Vancorps · · Score: 1

      We routinely work with 1gig PPT files, powerpoint doesn't allow streaming of the file so you can't work with it until the machine has downloaded the whole thing. It doesn't really matter though since the same concept applies to any files of any real size. Few people that use RDP on the regular see it as remotely slow. I have a problem with one of my coworkers who likes to run RDP sessions full screen. He often forgets he's directly on a server and then attempts to pull up a site like Hulu and subsequently finds flash not installed only to go ahead and install it. Fortunately he doesn't fill a role where he logs into servers anymore so its no longer an issue.

      Then there's this idea that screen scrolling would require an entire redownload of a frame which is simply untrue. Slashdot for instance is mostly white background which wouldn't have to be redownloaded. Then of course the task bar and firefox menu are unchanged and thus not redownloaded.

      The software involved has had more than 15 years to mature and is quite efficient at this stage which is why you saw MS enable 3d acceleration inside RDP for Windows Vista and Server 2008. Super high framerate stuff becomes a problem on slow connections, but most connections are just fine and most of the processing gets done on better hardware than typical end-user hardware. This doesn't make sense for all scenarios, but it does for a lot of them.

    38. Re:1996 called, by westyvw · · Score: 1

      Oh it will. Companies that dont use a thin client model are just burning money. I cant work without a network connection (for file storage, email, or the licenses my software requires from a server). And we loathe our users saving anything on a local machine both for backups and for accountability.

      Besides, I like having true roaming profiles and 3D desktops, dont you?

    39. Re:1996 called, by jpcarter · · Score: 1

      Without email, files on the network, network printers, whatever corporate apps you have, internet... what good is that PC?

      I'm nervous about those, too, but at least those are all parts of the whole. When the Citrix Farm fails while the only Admin is on vacation, everything is down.

      Different when you have a larger IT Dept., though.

    40. Re:1996 called, by jon3k · · Score: 1

      Who the hell has network failures that are anything more than tiny isolated incidents where a switch fan failed and you lost a block of 50 or so people for 15 minutes while you swapped it out? This isn't 1994.

      Network uptimes are in the 5 9's these days. We have 4 hour guaranteed MTTR on our WAN (they're actually under 2 in practice, but guarantee 4). Not to mention we've got backup WAN circuits (broadband VPN).

    41. Re:1996 called, by jon3k · · Score: 1

      That's a pile of shit. I type over 120 wpm and use the entire office suite via Citrix ICA and it runs flawlessly.

    42. Re:1996 called, by gedhrel · · Score: 1

      The university in question has been hauled over the coals in the past after laptops containing confidential information were sold. It's not the only one.

      (That was about a decade ago; our DPO still has to make regular court appearances to update on the process of contacting the people affected and mitigaion of the damage.)

      Encrypted laptops, etc, are all well and good; however, there'salso a cost in convenience when someone can't get at their data because rather than slap it on some robust bit of network storage that's properly backed up, they've kept it on their desktop for the last three months and everything has gone up in smoke.

      The bonus is that the data stays on-site where it can be properly curated. And doesn't wind up on J.Random User's home laptop that then gets nicked going through customs.

    43. Re:1996 called, by SanityInAnarchy · · Score: 1

      It doesn't really matter though since the same concept applies to any files of any real size.

      Minor nit -- no, it doesn't, it applies to any files of any real size which cannot be streamed. Counterexamples are videos, at the very least, and while I suspect OpenOffice loads the entire document, the design of an odp file is inherently seekable -- it's just a zipfile, so it can load each needed picture on demand. (I'm not sure if it does, but it's possible.)

      However...

      I have a problem with one of my coworkers who likes to run RDP sessions full screen. He often forgets he's directly on a server and then attempts to pull up a site like Hulu and subsequently finds flash not installed only to go ahead and install it.

      So it basically boils down to what kind of applications you're running. In the Hulu example, the video stream itself would've been fine to send over the network -- if there was a video file in question, it could've been streamed -- it's just impractical to send the raw frames.

      So, it seems to me that something like RDP usually provides a more reliable upper limit on the rate of data sent, while something like Samba can theoretically be much more efficient when applications are written with it in mind. Then again, the Hulu example proves that applications written without RDP in mind can also be a problem -- so it boils down to which protocol is more likely to have that kind of problem.

      That is, do programs more frequently assume that the filesystem is local and fast, or that the screen is?

      A few more nits:

      Then there's this idea that screen scrolling would require an entire redownload of a frame which is simply untrue.

      What I said is that once you've scrolled down a full page, that is a full frame.

      Slashdot for instance is mostly white background which wouldn't have to be redownloaded.

      At some point, yes it would. The sides would've been left alone, but where you actually have content, the fact that the background is white isn't really relevant -- it makes the image compress better, but a page full of text and white background is still going to end up as an image, which is larger than the original marked-up text.

      --
      Don't thank God, thank a doctor!
    44. Re:1996 called, by Anonymous Coward · · Score: 0

      only if you can get your users to understand that they can still edit local files when the network is down.

      "whats a local file? i dont have that icon on my desktop..."

    45. Re:1996 called, by Anonymous Coward · · Score: 0

      > ... but this isn't not a completely incredible approach.

      I couldn't quite stop myself from avoiding erring when refraining to prevent my failing to not misunderstand what you were saying ...

  9. economies of scale by petes_PoV · · Score: 2, Informative
    development costs, tooling, bespoke firmware, safety testing, promotion and the cost of supporting another range of kit.

    All these costs are largely independent of the number of units produced, yet must be recouped from their sales. By buying a dedicated thin client, you have to bear your share of the product development. Since thin clients sell far fewer units than PCs these costs are higher.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
    1. Re:economies of scale by RAMMS+EIN · · Score: 2, Insightful

      I don't think that argument holds water. After all, the parts that go in thin clients are the same parts that go in PCs, so that can't be the difference. Then there are some custom things, such as the case, but if you consider the countless PC cases, motherboards, etc. etc. already out there, I think that, even though total volume for PCs may be higher than total volume for thin clients, the volume for a given combination of parts that make up a PC isn't necessarily higher than the volume for a given combination of parts that make up a thin client. I think thin clients cost more simply because their target market will bear higher costs (if you are a large company or government agency, spending a hundred dollars more or less on your thin clients isn't such a big deal).

      --
      Please correct me if I got my facts wrong.
    2. Re:economies of scale by Anonymous Coward · · Score: 0

      Since thin clients sell far fewer units than PCs these costs are higher.

      i struggle with this arguement. yes, thin client devices sell fewer units than PC devices, but the components are the same/similar and in the thin client many are lower spec or removed. look at the netbooks, they sell them cheaper than a desktop PC but are relatively niche in comparison. even then netbooks have more processor, memory and storage than the thin client needs, yet are still cheaper.

      makes no sence unless there is some highly specialised, expensive, non-commodity hardware components in a thin client, which as far as im aware there isn't. if there is, why has no one said so as this would be the explaination the OP seeks?

    3. Re:economies of scale by Chris+Mattern · · Score: 1

      I don't think that argument holds water. After all, the parts that go in thin clients are the same parts that go in PCs, so that can't be the difference.

      I don't see where the parent poster even mentioned the cost of the parts as being part of the cost difference.

    4. Re:economies of scale by petes_PoV · · Score: 1

      Yes you're right. I specifically omitted the cost of parts for exactly those reasons.

      --
      politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  10. Smaller is cheaper by delirium+of+disorder · · Score: 1

    I find many aspects of smart phones compelling, with one exception: the cost of the phones, which typically exceeds that of a traditional box. I understand all of the benefits of smart phones (and the downsides, thanks) but I'm very hung up on spending more for less.

    You have to pay more to fit all that technology into a smaller package! If you don't care about space, just run a virtualized desktop on traditional desktop hardware.

    BTW I would recommend diskless workstations for thin clients. They may not be the cheapest, but they are full featured, fairly affordable, and well supported.

    --
    ------ Take away the right to say fuck and you take away the right to say fuck the government.
    1. Re:Smaller is cheaper by delirium+of+disorder · · Score: 1

      Bah...meant to title it smaller != cheaper...o well.

      --
      ------ Take away the right to say fuck and you take away the right to say fuck the government.
    2. Re:Smaller is cheaper by itsdapead · · Score: 1

      I find many aspects of smart phones compelling, with one exception: the cost of the phones [google.com], which typically exceeds that of a traditional box [system76.com].

      ...perhaps you should look at media players that do nearly everything except phone and GPS for 1/3 the price. (e.g. c.f. the price of an iPhone vs. an iPod Touch - or the HTC Hero vs. the non-Apple media player of your choice).

      One does wonder whether the prices of phones are kept artificially high to encourage people to get them on contract...

      --
      In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
    3. Re:Smaller is cheaper by wayland · · Score: 1

      > Take away the right to say fuck and you take away the right to say fuck the government.

      Bonus!  We increase the intellectual level of the political debate at the same time!

      (Yes, this was supposed to be funny :) )

  11. You're not missing anything by symbolset · · Score: 0

    $200, $300 is missing the point. If you've going VDI, most of the money will be spent in training the end user, in the displays and their mounting. In most cases the deployment costs more than the thin client. The thin client is a trivial part of the cost, and you might as well get a good one.

    --
    Help stamp out iliturcy.
    1. Re:You're not missing anything by OolimPhon · · Score: 4, Informative

      Eh? Don't know what you're on about. I'm sitting here posting this on a thin client. I have a standard PC keyboard, monitor and mouse. I am looking at a normal PC session (in my case Gnome on Linux, but whatever). No retraining required, either for software or hardware. My hardware is an old PC with nothing but the motherboard left in it, running LTSP client. Cost me effectively nothing.

    2. Re:You're not missing anything by OolimPhon · · Score: 1

      Oh, and boots in 35 seconds.

    3. Re:You're not missing anything by drinkypoo · · Score: 2, Informative

      $200, $300 is missing the point. If you've going VDI, most of the money will be spent in training the end user, in the displays and their mounting.

      You can regularly get quite decent 22" LCDs for under $200 now. So, no, the thin client is a massive part of the cost, and the whole point of moving to them is that the maintenance costs decrease.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:You're not missing anything by symbolset · · Score: 1

      Yeah, I do this too. I have an LTSP server set up in the house for guests to use, so they don't compromise somebody's normal computer. Boots fast and works great. Bulk lots of corporate desktop pulls work great too and these days you can get them with a 3GHz processor and gigabit networking for about $130, including shipping. That's plenty powerful for the task.

      I thought you were talking more about the commercial thin client PC's, which are tailored to this task and come in form factors so small some of them mount on the back of the monitor.

      --
      Help stamp out iliturcy.
  12. use hybrid. SUNRAYs rock by Anonymous Coward · · Score: 0

    slim hardware, no moving parts. Hot desking is wicked.

    1. Re:use hybrid. SUNRAYs rock by alexandre_ganso · · Score: 1

      I was thinking about this, as we have some hundred of those.

      Then I remembered how crappy their "java desktop environment" is and how slow the whole thing is in general. Actually, it sucks hard.

    2. Re:use hybrid. SUNRAYs rock by Moxon · · Score: 1

      I'm much more happy with ours after we moved the servers to RHEL (and ~5 years more recent hardware).. We even get proper Gnome now :)

  13. Slow news day? by hairyfeet · · Score: 2, Insightful

    Well here you go a 1.7GHz off lease Compaq desktop for a whole $75 with shipping. That is pretty much the only choice if you don't want to DIY, because thin clients are a niche that will cost you $$$ that it doesn't sound like you are willing to spend. This is small, can fit under a monitor, and has 20Gb of local storage. Perfect for a thin client.

    The simple fact is that is as cheap as you're gonna get, because PCs have economies of scale and thin clients don't. If you just have to have an OEM thin client be prepared to shell out the $$$ buddy.

    --
    ACs don't waste your time replying, your posts are never seen by me.
    1. Re:Slow news day? by moonbender · · Score: 1

      Comes with 1 "monitor" output, which I assume means D-BUS. Not a very good solution. Not to mention driving more than one display, or running Linux. It is cheap though, I'll give you that.

      --
      Switch back to Slashdot's D1 system.
    2. Re:Slow news day? by Anonymous Coward · · Score: 0

      Thanks but no thanks. That is the equivalent of a Hummer: Big, ugly, slow, loud and consumes energy like no tomorrow. It will cost more in electricity in one year than you paid for the hardware.

    3. Re:Slow news day? by hairyfeet · · Score: 1

      So you add a cheap PCI card, in this case an 8400GS for a whole $42. You could go even cheaper, but if you want to drive multiple monitors and have decent resolution this would be the best bet. This is the best one for Linux as well, due to the fact Nvidia drivers are better ATM. If you would prefer something with open drivers (I heard the older Radeons are well supported now) you can save a couple of bucks by going with a Radeon 9250 instead at $40.

      Adding the $42 to the $75 for the machine you come out at $117 which is still far below the $200 that the poster said he wanted to spend. With a 1.7GHz CPU, 512Mb of RAM (expandable to 2Gb) and 20Gb of offline storage I still think this is the best thin client candidate for the $$$. Where else are you gonna find a thin client that can drive multiple monitors, has enough power for decent video resolution without stutter, and plenty of offline storage, all for less than $120?

      And if he wants to spend a whole extra $20 he can nearly double his CPU to a 2.4GHz, double his offline storage space, and even have a copy of XP Pro to use when the network is down, all for less than $160 with the extra video card. I doubt VERY seriously he is gonna find a better deal on a PC usable for a decent thin client any cheaper.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    4. Re:Slow news day? by Anonymous Coward · · Score: 0

      I had one of these under my desk, briefly. Don't get these if you care about noise. Video uses shared memory, and rendering almost anything requires CPU power. The fans on the hot P4s ramp up at the slightest provocation. They sound like vacuum cleaners.

    5. Re:Slow news day? by moonbender · · Score: 1

      Fair enough, didn't realize it's extensible using PCI cards.

      --
      Switch back to Slashdot's D1 system.
    6. Re:Slow news day? by hairyfeet · · Score: 1

      If you need a good cheap computer you really can't go wrong with Surplus Computers. I have been buying off lease equipment, both client and server for my customers from them and they really are top notch. Excellent prices, quick shipping, great service, and unlike most places they clean image them before shipping them out..no crapware like you would get from the factory. I have also bought several of their 1.6-2.2Ghz SFF clients and made them into excellent DVRs Just slap a good PCI capture card along with a cheap PCI video card and you are good to go.

      So considering the requirement laid down in TFA (under $200, no DIY) I'd say that a good off lease from Surplus Computers is just about the only way to go. I don't think I've ever seen off lease thin clients for less than $300, they are just too small a niche. And with Speedstep enabled these SFF machines are actually quite quiet. So I would have to say that Surplus Computers is the place to go. Oh BTW, if you ever need a kick ass server cheap check out their dual Xeon deals, totally crazy prices.

      --
      ACs don't waste your time replying, your posts are never seen by me.
  14. Do you need an actual thin client? by gadget+junkie · · Score: 1

    I found out recently a reseller here in Italy distributing the Ncomputing client, which strictly speaking is not a computer, rather a screen repeater; I've had the occasion to try it , and it worked fine for a small office, especially if there are security considerations involved, since there's an actual box that does not have an USB port; there' s no way to take data out except via email.
    The price is quite reasonable, and for the vast majority of office work it's vastly simpler than virtualization via the usual suspects.

    --
    "If a boss demands loyalty, give him integrity. But if he demands integrity, give him loyalty." (John Boyd, 1927-1997)
    1. Re:Do you need an actual thin client? by cr_nucleus · · Score: 1

      there' s no way to take data out except via email.

      And maybe using a camera. Guess you forgot all those spy movies from previous century :)

    2. Re:Do you need an actual thin client? by Jonah+Hex · · Score: 1

      Reasons? Citations? News Articles? Peer Reviews?

    3. Re:Do you need an actual thin client? by mofojones · · Score: 1

      We use NComputing for a number of clients, both large and small. Not just the large enterprises that everyone keeps talking about in this thread. They are very economical, provide a usb port for the local user, and we only have to maintain one pc. We can recycle old monitors and keyboards, and one good dell optiplex running winXP can run a lot of 10 of them. You have to pay careful attention to windows updates - there have been a few that will break ncomputing. But other than that, it's pretty worry-free.

  15. What's missing by Anonymous Coward · · Score: 0

    The bandwidth requires to drive multiple thin-clients at full resolution.

    1. Re:What's missing by eharvill · · Score: 1
      --
      At night I drink myself to sleep and pretend I don't care that you're not here with me
    2. Re:What's missing by level_headed_midwest · · Score: 2, Interesting

      I'll second that. I currently am doing a stint in a place that uses newer WYSE thin clients accessing a Citrix server, hooked up to 22" monitors for their computers. The maximum resolution the thin clients can handle is 1024x768, which is horribly limiting for those who have to use something even as mundane as a spreadsheet, let alone the complex electronic medical records system that is the real reason that the computers even exist there. EMR systems use a ton of screen real estate as they are generally full of tabs and sidebars and pack a LOT of information into each screen. Using one of those at 1024x768 is roughly analogous to viewing a typical optimized-for-1024x768-and-above website on an an average smartphone. You're looking out through a porthole and scroll and scroll and scroll just to view the entire page. I have used identical EMR systems (also running a remote instance over Citrix) at other places that have low-end PCs that can drive monitors at 1280x1024 or 1680x1050. I'd be willing to bet that the loss of productivity with people fighting with the low-resolution thin client screens is greater than the amount the place "saved" by using thin clients instead of the low-end PCs.

      --
      Just "gittin-r-done," day after day.
    3. Re:What's missing by Lectoid · · Score: 1

      I used to work for a hospital where I implemented WYSE thin clients. I also set them up for PACS x-ray viewing. Since those needed better resolution and color depth, I installed cheap video cards in them (I don't remember the model number of the WYSE, this was in 2002-03). They had one PCI slot in them and used a VIA processor. Worked great.

      --
      Is it just me, or do you hate it when people say "Is it just me..."?
    4. Re:What's missing by pnutjam · · Score: 1

      ROTFLMAO, you are hilarious. I've supported a think client infrastructure and everything you say about higher resolution is correct, however, at least 70% of my users insisted on 800X600 (not a typo). It drove me insane, I guarantee my eyes are worse then every one of them and I work with a higher resolution, but they insisted the could not see the screen.
      Never mind that the monitor is pushed back to the far corner of the desk (why do people do that?).

    5. Re:What's missing by level_headed_midwest · · Score: 1

      I don't doubt you. I have seen a bunch of the 22" screens being run at 800x600 because people said that the text is too small even at 1024x768. Several people begged me to drop the resolution down to 640x480 because they "had trouble seeing things on the computer" at higher resolutions. I wondered what the heck was going on as text on those screens at 800x600 was about 1 cm high, so they must be damn near blind if they couldn't read it, since they were all sitting right in front of the monitors. I ended up being pretty much right as those individuals were older and farsighted and didn't want to have to put on their reading glasses to use the computer.

      --
      Just "gittin-r-done," day after day.
  16. I'm Confused by fm6 · · Score: 1

    What are the benefits of desktop virtualization? As they apply to you, that is. Every user of this technology that I know of is a big company or school that needs to deploy hundreds (sometimes thousands!) of desktop systems, and often can't afford to have an IT guy at every site. That's why they're willing to pay a premium price for the thin clients — it's more than offset by lower "cost of ownership".

    Even if do have a use for DV that isn't obvious to me, you might as well do it with PCs. The only catch with them is that you have to install the client software on each PC. Thin clients are for people who don't want to do that.

    1. Re:I'm Confused by Anonymous Coward · · Score: 0

      If you think that anyone has to install anything on each PC, despite PXE booting being mentioned in the question, you are indeed confused. You can roll your own "thin client" and have all the same central management comfort that a "real" thin client system gives you. You need a very low end PC minus the hard disk, set the BIOS to boot from the network and the rest is server-side.

    2. Re:I'm Confused by i.r.id10t · · Score: 1

      Also groups like this have an overall budget, but it is split into portions- purchase of physical goods, purchases of services, and payroll money. Which is why a local university is fighting with the budget guys to stop paying $300k a year for licenensing their learning management system/course delivery system, adopt a F/OSS solution, and spend an extra $200k per year on a couple of developers to make customizations, etc. Sure it looks like an overall savings of $100k per year, but the $200k people money comes from a different pool than the $300k license money...

      --
      Don't blame me, I voted for Kodos
    3. Re:I'm Confused by drinkypoo · · Score: 1

      What are the benefits of desktop virtualization? As they apply to you, that is.

      No desktops to screw up

      Hardware failure? Replace the hardware from a spare, which takes less time and effort because the hardware is small and has few attached cables.

      No data on the user's desktop which must be managed and backed up, ever

      One big PC is actually cheaper than a lot of small PCs, though not very much cheaper. Still, a difference is a difference; I have yet to see a PC under $600 actually worth buying for corporate use, every attempt I've made in that direction has been disappointing if not disastrous. Thin clients, of course, are a bit different.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:I'm Confused by larien · · Score: 5, Informative
      There are varied benefits, but some highlights:
      • Desktop breaks? Ship out a new box, they plug it in and away they go. You don't need to worry about what software they need as it's all on the server.
      • Security - no hard drives on desktop which can be stolen.
      • Patching/maintenance. Would you rather maintain patches on 1000 desktops or 10 big boxes in the data centre?
      • Power/cooling/noise at sites. A "real" thin client (as opposed to a PC masquerading as a thin client) will have minimal power requirements which leads to less cooling and noise (no fans or crunching hard drives)
      • Portability. I don't care which desk I sit at, my virtual desktop will automatically have all my apps. If you have a solution like Sun's Sunray, you can even log out of your Sunray half way through writing a document, move to another desk (possibly in another city) and pick up the doc where you left off.
      • High bandwidth apps run in the same data centre as the database server/whatever and you only get the screen updates down the wire which can be more efficient.
    5. Re:I'm Confused by obarthelemy · · Score: 2, Insightful

      Most of that can be achieved with a well-designed "fat client" network:
      - standard PCs, swap if broken
      - no local data storage via user policies/right
      - patching: frankly, i don't care, 1000 identical desktops can be automated
      - power/noise: i'll grant you that one, hsouldn't be much of an issue though
      - portability: can be done on fat clients too
      - bandwidth: i'll grant you that one too

      On the flip side, fat clients give you more responsive UI, less network load/dependency, less peak-time cpu cycles starvation...

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    6. Re:I'm Confused by Anonymous Coward · · Score: 0

      Additional point of security --- thin-clients are of limited usefulness without the network behind them. Makes them a less attractive target for employee theft versus a full blown PC.

    7. Re:I'm Confused by Anonymous Coward · · Score: 0

      You missed one additional benefit: durability. Power requirements, durability, and centralized maintenance were the big factors that drove my company to buy 500 thin clients at $125 each ($200 retail) three years ago. In the intervening time we've only had four machines fail, one of which got dropped down a concrete staircase, and all of those were replaced under the three year warranty. The thin clients draw only 10 Watts compared to the average 80 Watts of the desktops we replaced. In New England, where power is expensive, we calculate that saves us $35/device/year. And yes, our data center power costs went up, but by much less than the 40 kilowatts those 500 desktops drew.

    8. Re:I'm Confused by BitZtream · · Score: 1

      Desktop breaks? Ship out a new box, they plug it in and away they go. You don't need to worry about what software they need as it's all on the server.

      You can do this with disk images and a standard hardware package.

      Security - no hard drives on desktop which can be stolen.

      I've never heard of a hard drive being stolen. If you're refering to data theft, that still happens on the flash drive or the encrypted zip they email out of the office.

      Patching/maintenance. Would you rather maintain patches on 1000 desktops or 10 big boxes in the data centre?

      When you have 1k machines you are maintaining you have automation for patching, you don't patch by hand. If you keep your systems consistent its no different patching one or 100k.

      Power/cooling/noise at sites. A "real" thin client (as opposed to a PC masquerading as a thin client) will have minimal power requirements which leads to less cooling and noise (no fans or crunching hard drives)

      The most expensive components from a power perspective are CPU and video. Fans and hard drives are trivial in the grand scheme of things, and the performance increase you get from havin ga local system far outweighs anything you're going to shave off here.

      Portability. I don't care which desk I sit at, my virtual desktop will automatically have all my apps. If you have a solution like Sun's Sunray, you can even log out of your Sunray half way through writing a document, move to another desk (possibly in another city) and pick up the doc where you left off.

      What OS can you not do that with? What OS doesn't support networked home directories?

      High bandwidth apps run in the same data centre as the database server/whatever and you only get the screen updates down the wire which can be more efficient.

      You haven't actually used this stuff have you? What takes longer to get, several megabytes of pixels or the first few rows of a cursor on a database?

      I sit at home, using a database 1300 miles away, using a local app because its FAR more responsive and FAR less annoying than the lag of doing a remove viewing session.

      Nothing you've specified is actually a benefit. Its not that you've stated anything untrue, its just that everything you've said really doesn't actually apply when you compare to a standard desktop.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    9. Re:I'm Confused by BitZtream · · Score: 1

      Yea, and keniston locks are a pretty effective measure as well.

      But seriously, how many PCs a year get stolen by an employee? And of those that get stolen, how many of those employees are going to realize that its a thin client before they get it home?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    10. Re:I'm Confused by CAIMLAS · · Score: 1

      #
      # Patching/maintenance. Would you rather maintain patches on 1000 desktops or 10 big boxes in the data centre?

      This, and it's corollary, is what I always come back to as the main/biggest weakness to thin clients. That corollary is: would you rather have 1 user down due to his malware stupidity, or 50 users?

      I'm all for thin clients, and i think the other disadvantages of thinclients are easily avoidable/marginalized by the benefits (given most environments).

      I'm not saying it's a red flag for me, but it does give me pause. When Norton will hose a system (it it won't allow any logins, normally or in safe mode) infected with Internet Security 2010 or similar, I question how much 'system recovery' I'd end up having to do, vs. simply wipe-and-recover.

      Now, if your infrastructure is large/organized enough that you've got all storage on a SAN, FC host, or similar, you've got another environment variable which aides the ease of a thinclient migration.

      From what I've seen, hospitals are probably the organization type which could benefit the most from thinclients, both short and long term. The environmental factors alone should be enough to sell them even at an increase in cost, but there are a bunch of other reasons as well.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    11. Re:I'm Confused by Anonymous Coward · · Score: 0

      In a shop floor environment; you might be surprised. Coupled with zero moving parts, thin-clients do have uses that are hard to match with a standard PC.

    12. Re:I'm Confused by fm6 · · Score: 1

      You're quite right about the bureaucratic difficulty of hiring people versus paying some other cost, even if the other cost is actually higher. Though I think it has less to do with "a different pool of money" than with the fact that modern organizations tend to be dominated by numbers dweebs who like to keep head counts down.

      But I really doubt that these issues have much to do with the use of thin clients. It's an objective fact that you can save a lot of money if you don't have to hire a lot of IT people to babysit your desktop systems. (Plus, the kind of IT you need for centralized system can be shipped overseas.) By contrast, it's a lot harder to convince people that hiring people to customize OS software is cheaper than paying license fees. It might save money on paper, but it's not unheard of for a project to require more work than anticipated.

    13. Re:I'm Confused by fm6 · · Score: 1

      Sigh. I can understand not having the time or patience to read a post in detail. But you didn't even look past the first couple of sentences.

    14. Re:I'm Confused by fm6 · · Score: 1

      Another guy who can't be bothered to read the whole post. I was not arguing that thin clients are useless. I was arguing that thin clients have a specific use case, and this guy isn't it.

    15. Re:I'm Confused by loners · · Score: 1

      Here is the solution for the local university:

      1) combine the OSS into one single project
      2) start making necessary customizations
      3) license usage to the uni for 250k
      4) profit!

  17. Re:what the fuck are you on about. by koekepeer · · Score: 1

    I don't see how this topic is related to having sexual intercourse with your mother.

  18. Go home brew by bragr · · Score: 1

    Personally, I don't see a problem with the home-brew solution. When you want something very specific, its often your only choice. Any it wouldn't be that hard either, you get a Mobo/CPU combo, case/PSU combo, and a stick of ram, it takes you 4 screws, and plugging 3 things, and 2 or 3 minutes in the BIOS.

    1. Re:Go home brew by zippthorne · · Score: 1

      Yeah, except ditch the cpu fan and get a custom one. The typical "included" cpu fan is annoyingly noisy.

      --
      Can you be Even More Awesome?!
    2. Re:Go home brew by Bazman · · Score: 1

      If you really think you can do this for less than the price of comparable commercial thin clients, then I suggest you quit your job and go into the thin client business.

    3. Re:Go home brew by SmoothriderSean · · Score: 1

      Mod parent up, anyone? There are so many +5's in this thread talking about how thin clients are priced as they are because "it's chump change for business", etc. If someone came along with equal thin clients for $100 less, plenty of people (like our thread starter Mr. Ginter) would buy them. And since there's plenty of companies wading into manufacturing various low-power hardware all the time, where are the cheap thin clients?

  19. Pipe down, this is a grownup conversation by fm6 · · Score: 1

    I have two suggestions: grow up, and learn to read. The guy is pricing new hardware. The system you found is a remanufactured out-of-production unit; even if it were brand new, it doesn't appear to meet his specs. A brand new system from the same manufacturer runs $350 or so.

    1. Re:Pipe down, this is a grownup conversation by Anonymous Coward · · Score: 0

      Where'd he say he's pricing new hardware?

      What he does say is he's looking for stuff that can drive a 22" at full res.

    2. Re:Pipe down, this is a grownup conversation by Anonymous Coward · · Score: 0

      Where'd he say he's pricing new hardware?

      What he does say is he's looking for stuff that can drive a 22" at full res.

      Fair. So in that case quoting from your original link:

      - Microsoft Windows CE Operating System
      - Industry-standard operating system. Delivers simple integration of legacy systems with Windows 2000
      - Two USB ports, 10/100 BaseT Fast Ethernet

      Yea, and this device can't even do that.

  20. Re:what the fuck are you on about. by citizenr · · Score: 1

    Sorry motherfucker, but WYSE 3200LE cant run 1680x1050, has 233MHz and is refurbished CRAP.

    --
    Who logs in to gdm? Not I, said the duck.
  21. Market Segmentation by RAMMS+EIN · · Score: 4, Insightful

    I think the explanation may be market segmentation. Thin clients are aimed at large organizations, where a few hundred dollars for a machine is chump change. They will happily buy greatly overpriced thin clients, because even the cost of an overpriced thin client on a desk is still dwarfed by the cost of the employee at the desk.

    For home users, the picture is different, because they tend to see the computer in isolation. But the vast majority of home users wouldn't want to buy a thin client at any price, because they wouldn't know what to do with it.

    If you want a cheap thin client, I would recommend to either buy one second hand (you can get them for under 100 dollars), or to just get whatever box you can and pretend it's a thin client.

    --
    Please correct me if I got my facts wrong.
    1. Re:Market Segmentation by Anonymous Coward · · Score: 0

      A sensible remark. Since the volume is relatively low, there are few suppliers which enables the manufacturers to charge higher prices than for a mass market item. In general the price of a manufactured item bears little relationship to its manufacturing costs unless the market has many suppliers and and consumers.

      Its simple minded to think goods are priced at cost plus markup. Instead the equation is more like what is the price that maximizes revenue?

    2. Re:Market Segmentation by Anonymous Coward · · Score: 0

      Thin clients are aimed at large organizations, where a few hundred dollars for a machine is chump change. They will happily buy greatly overpriced thin clients, because even the cost of an overpriced thin client on a desk is still dwarfed by the cost of the employee at the desk.

      I don't think I believe this. A large organization, rolling out (say) 1000-10,000 "desktops" would seem to have strong motivation to minimize the cost of each desktop. If they can get a thin client for anywhere close to the actual value of hardware - say $150 - instead of the boutique TCs currently on the market for $300-$400, they could save upwards of $1M. That's not chump change.Even going to diskless thick clients ought to save $50 * 1000 = one employee salary. Plus centralized administration.

      There's zero motivation for a home user to consider TC, because they'd have to get a high(er) powered server to host and learn to set the whole thing up. Even somebody looking his, hers, & kids terminals would be looking at $1200 of TCs + $5k server, vs $2000 of PCs. Why bother?

    3. Re:Market Segmentation by RAMMS+EIN · · Score: 1

      ``I don't think I believe this. A large organization, rolling out (say) 1000-10,000 "desktops" would seem to have strong motivation to minimize the cost of each desktop. If they can get a thin client for anywhere close to the actual value of hardware - say $150 - instead of the boutique TCs currently on the market for $300-$400, they could save upwards of $1M. That's not chump change.Even going to diskless thick clients ought to save $50 * 1000 = one employee salary. Plus centralized administration.''

      The thing is, you have to calculate what they would save per seat. With the discounts a large organization can get, that probably isn't a whole lot. Say it's $100. So that's $100 saved for the one employee that is going to be working with it. The total cost of that employee can easily be 40 times that in a month. So if the investment in the PC or thin client is written off in 2 years, that $100 difference is about 0.1% of the cost of your employee. I call that chump change.

      --
      Please correct me if I got my facts wrong.
    4. Re:Market Segmentation by Anonymous Coward · · Score: 0

      "Even somebody looking his, hers, & kids terminals would be looking at $1200 of TCs + $5k server, vs $2000 of PCs. Why bother?"

      to annoy an angry god. forget i said that.

  22. stand of the shoulders of others by seringen · · Score: 2, Informative

    Dave Richards is well known in the Gnome community for working with thin clients, specifically for the city of largo, florida. if you wanted some input on the subject you might want to ask him. he's on gnome's planet, or http://davelargo.blogspot.com/

  23. Sun Ray's work well and are cheap by therus121 · · Score: 4, Informative

    Have a look at the 'Sun Rays' from Sun - they've been around for years; they are cheap and very reliable: http://www.sun.com/software/index.jsp?cat=Desktop&subcat=Sun%20Ray%20Clients The prices shown on the Sun site are list-price - we get a Very healthy discount off of this, which brings the prices down even further.

    1. Re:Sun Ray's work well and are cheap by up4fun · · Score: 5, Interesting

      I agree with this, too. The sunrays are excellent.

      But I think the OP is still missing something here. The transition to VDI is not just about replacing one box with another doing the same old same old. It is also an opportunity to start to transition away from local storage, login, screen savers, etc. While there are many many advantages at the back end, there are also some significant gains at the front-end, too.

      As an example, the sun rays have card readers that allow you to authenticate to the back-end very quickly. Using this feature you can roll out always-on desktops that let your users sit down at a desk, any desk, pop their card in and get their desktop, just as they left it, anywhere. As they get up, their card goes with them. No need for screen savers and the whole thing is very very fast. This kind of facility is a big win for our users. No more logins! No more password resets!

      So perhaps consider VDI as a way to seriously improve the end-user experience of computing.

      D

    2. Re:Sun Ray's work well and are cheap by Skapare · · Score: 1

      With the right hardware present, the rest of this is all software. A fast-boot thin Linux on an SD card can run in 1GB ... 4GB might be nice to help X do more caching. That should be doable right inside the monitor case these days (use COTS keyboard/mouse).

      --
      now we need to go OSS in diesel cars
    3. Re:Sun Ray's work well and are cheap by Anonymous Coward · · Score: 0

      We experimented with SunRays for customer service teams at my last job, and found them to be excellent front ends for VDI, even with Windows for all the reasons the parent mentions ... the problem is, when you factor in the cost of running Windows instances either on their own VMs or via Terminal Server, it gets to be nearly as (or possibly more) expensive as running a cheap PC. Microsoft's licensing costs are prohibitive when it comes to virtualization, or at least they were three years ago when we were doing this.

      This killed the project for us, because our organization was more interested in capital expenditures than TCO.

    4. Re:Sun Ray's work well and are cheap by BrianRoach · · Score: 1

      Chalk me up as a fan as well.

      I have a 1g sitting right here on my desk. There's also one in the kitchen (It's nice for recipes, looking up stuff before leaving the house, etc), and there's one hooked to the 42" LCD HD TV in the living room. All of these run off my v20z in the basement.

      You can get them for between $15 and $50 on eBay. The 1g is an older model but has DVI out and supports up to 1900 resolution.

    5. Re:Sun Ray's work well and are cheap by Glasswire · · Score: 1

      I find it interesting that in the two or three Sun Microsystems offices I've been in the receptionist has a SunRay but all everybody else is using Mac (or other laptops - often running Solaris tho) .
      There's a curious elitism in that everyone participating in these discussions may think that the 'workers' they condescend to are appropriate candidates for thin clients but probably NO ONE here thinks THEY could iive with a locked down, limited environment a TC represents. No that's for the little people.
      Combine this with the revelation that the economies of scale make PCs (which with good management can be locked down and run softclient stacks to do any kind of centralized management a TC supports) about the same price. The perpetual wishful thinking around TCs is delusional because it's based on the belief that because OEMs COULD buiid a decent TC for $75 that they WOULD sell it for $90. That kind of margin represents a sufficient profit on a $400-500 PC but isn't a good enough business at the TC level.

    6. Re:Sun Ray's work well and are cheap by jon3k · · Score: 1

      You're crazy I love my virtual desktop. I have 10x the computing power I ever had with a desktop PC and when I vpn in from home everything is exactly where I left it.

  24. 32x32 by WGFCrafty · · Score: 1, Troll

    (give me non-vaporware that will drive a 22" LCD at full resolution)

    K.

    Will 32x32 (1024) pixels be enough? We can use a TI-83, not even silver, to accomplish this!

    Oh, you mean you wanted a non-stupid resolution. As far as I'm concerned "full resolution" means the maximum native resolution a monitor can output.

    1. Re:32x32 by Jerry+Smith · · Score: 2, Insightful

      (give me non-vaporware that will drive a 22" LCD at full resolution)

      K. Will 32x32 (1024) pixels be enough? We can use a TI-83, not even silver, to accomplish this! Oh, you mean you wanted a non-stupid resolution. As far as I'm concerned "full resolution" means the maximum native resolution a monitor can output.

      Erm, yeah, I guess he expected non-stupid reactions, from people who'd automatically assume a 1920 × 1080 resolution.

      --
      All those moments will be lost in time, like tears in rain. Time to die.
    2. Re:32x32 by Gadget_Guy · · Score: 1

      Erm, yeah, I guess he expected non-stupid reactions, from people who'd automatically assume a 1920 × 1080 resolution.

      Really? My 22" LCD monitor has a native resolution of 1680x1050. It just shows how stupid it is to talk about screen size when you really mean resolution. That was the point that grandparent post was making.

      I have to buy another LCD monitor soon, and it will run at 1920x1200 and not 1920x1080. This is why I won't just ask for a size in inches.

    3. Re:32x32 by Anonymous Coward · · Score: 0

      Erm, yeah, I guess he expected non-stupid reactions, from people who'd automatically assume a 1920 × 1080 resolution.
      Why would anyone would mod this guy up? I have a couple of 22" monitors, some won't provide more than 1280x1024 screen resolution (the really old ones - 4:3 aspect ratio), the new ones, are around 1920x1200 (which in fact is the highest resolution achieved by single link dvi).

      Let me tell you a story about bosses here buying screens, they started to compete to buy the biggest screen. One end up buying 30-inches and all of them followed, one guy said "screw it, I'm buying a bigger one", so he bought a 37" LCD. Turns out of course there are no 37" PC screens, he got a big TV that wouldn't show more than a 720p could. No need to tell, if was funny to see him watching his big pixels on the screen

      So 32x32 seems like a reasonable funny answer to someone asking to get "full resolution" for a screen size.

  25. Re:what the fuck are you on about. by revengebomber · · Score: 1

    The client you linked to is about 10 years old. It offers "integration of legacy systems with Windows 2000," and comes in attractive beige plastic. It even carries a Win___ name! Considering that a throwaway cellphone you get from Verizon has about twice as much CPU power as this thing, it's definitely not "cheap" for $100.

    ...shit bitch motherfucker.

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  26. We've been here before... by CaptainOfSpray · · Score: 1

    The "thin client" meme goes back to well before 1993 (when the phrase was coined), and has never caught on. All the reasons why it did not catch on still apply. Mostly, the saving on hardware cost gets lost in the overall cost of the project, plus, the flexibility of conventional PCs (tuning the client installation to the needs of the specific department, and retuning every time the business need changes) has a value that massively outweighs the saving in hardware cost. Those who do not understand history are condemned to repeat the mistakes of the past (yes, I know it's a paraphrase).

    --
    "Cock Up Your Beaver" does not mean what you think. This sig is intended to clog filters and annoy do-gooders
    1. Re:We've been here before... by Anonymous Coward · · Score: 0

      Everybody claims they are special and need tweaks but in reality that is not really true. Some need tweaks, so here's a worst case scenario: a if you actually need to tweak things for each department as you said, (assuming 100 employees per department, 8 departments) you still only need twice as many servers as departments; 16 machines is is a nice improvement from your previous 800 machines.

      I would like to raise another voice for SunRays that is mentioned elsewhere. They work like a charm and run forever.

    2. Re:We've been here before... by cyber-vandal · · Score: 1

      In 1993 there weren't several virtualisation solutions that the thin client can use. We use thin clients at work connecting to VMWare servers and they're just as good for the average employee as a desktop without all the aggravation that goes with having several hundred corporate PCs to maintain.

  27. Thinnish thick clients. by SharpFang · · Score: 3, Informative

    A minor computer firm is subcontracted to assemble cheapest PCs. They build normal self-contained PCs running the cheapest OEM Windows available. These are $80(+OS) machines running on parts that are a storage surplus after they went out of sale. Then they install the "thin client" software which is some kind of Telnet or VNC or a web browser with intranet connection, pointed at a PHP web app.

    So basically the employee boots up the computer normally, starts the app fullscreen and does most of the work remotely.

    This has several advantages. The workstations can be troubleshooted locally. They can back up your work if network connection goes down. They allow for custom PC hardware (card readers, barcode scanners, webcams for teleconferencing and so on). They can be upgraded if the need arises, and fixed using off-the-shelf hardware (unless it went so obsolete it's unobtainable). And due to economy of scale, they are cheaper than dedicated thin clients despite being way overpowered.

    I've seen quite a few markets and institutions running a system like this.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    1. Re:Thinnish thick clients. by characterZer0 · · Score: 1

      And they take up way more space and use way more energy than is necessary.

      --
      Go green: turn off your refrigerator.
    2. Re:Thinnish thick clients. by SharpFang · · Score: 1

      If space taken up by the PC is of concern to you, your employees are cramped in way too little space anyway.
      As for power, downclocked CPU, the hdd set to spin down pretty fast and such mitigate most of the problem. In my climate, over most of the year power-hungry appliances mean just that much savings on heating anyway.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    3. Re:Thinnish thick clients. by drinkypoo · · Score: 1

      They allow for custom PC hardware (card readers, barcode scanners, webcams for teleconferencing and so on).

      Card readers and barcode scanners are keyboard devices. You can get them with USB these days. In fact, I've got a USB CueCat.

      Webcams are a bit tricky, but they should be highly doable with the new FUSE character device support. That is a good point, though.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:Thinnish thick clients. by aix+tom · · Score: 1

      That is true for traditional "office" settings.

      It is however very nice that we now can use the space that was take up by the standard size pc for additional storage space in the information points on the sales floor where we deploy them. They are also much easier to move around when we re-decorate since they are fixed to the back of the monitor.

    5. Re:Thinnish thick clients. by nabsltd · · Score: 1

      It is however very nice that we now can use the space that was take up by the standard size pc for additional storage space in the information points on the sales floor where we deploy them. They are also much easier to move around when we re-decorate since they are fixed to the back of the monitor.

      Dell has "standard" PCs with that exact same form factor, as well as ones that are more like an iMac (i.e., all you see is a keyboard and display, but it's an entire computer).

      This link should get you there. If not, go to the Dell business site, and under desktop PCs, click "All-In-Ones".

    6. Re:Thinnish thick clients. by Anonymous Coward · · Score: 0

      How easy are they to find warranty replacement parts for?

    7. Re:Thinnish thick clients. by Anonymous Coward · · Score: 0

      Dell has some slimline PCs that combined with a LCD screen and a bracket that offers locking functionality for both units, even with a cage that covers the rear with the cables, to prevent insertion of stuff. In my experience, they worked well in an academic environment and offered decent performance.

      If I were recommending PCs for use as terminals, I'd probably recommend these. Combine them with something like DeepFreeze (so even someone managing to get administrator can't have changes past a reboot), use the onboard TPM chips and enable BitLocker (to ensure that even people who bypass the BIOS are unable to alter anything with boot media), and use Active Directory profiles to complete the rest of the lockdown. Another advantage is that if one wants to use the PCs as standalone desktops, it would just take some adjustments of group objects, and perhaps removal or disabling of DeepFreeze to make this work.

      However, there is one immense advantage of terminals over PCs acting as terminals. A terminal, if it breaks, I can take off a desk, swap it with a model out of the box, and depending on how well the network autoconfiguration is, the user is back and working with his or her desktop in short order. PCs, this is harder to do, as one has to find what hardware is wrong with it first.

    8. Re:Thinnish thick clients. by SharpFang · · Score: 1

      Well, you can swap a PC-as-terminal just as well, then troubleshoot the faulty unit and store for replacement when fixed.
      If a terminal breaks, you swap them just the same then send to manufacturer for replacement or discard if the warranty has expired, because they are usually not serviceable.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    9. Re:Thinnish thick clients. by SharpFang · · Score: 1

      Usually quite easy, minus no 1:1 replacement.

      Likely if the HDD fails, a bigger model will have to be installed. If RAM fails, possibly second-hand/refurbished will have to be used as replacement. Considering the price of the whole setup, even if the whole motherboard-CPU-RAM combo has to be replaced with a "current" model, it's still doable and not very expensive.

      Note the customer has no business asking what's inside that thing as long as it works to the specs, so whatever the subcontractor puts inside that still performs, is okay. The boxes may even vary wildly between each other, but as long as they are capable of running the "client app" okay, that's not a problem to anyone except of the warranty service guys.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    10. Re:Thinnish thick clients. by Anonymous Coward · · Score: 0

      Until a virus or internet worm spiders through the LAN making a random set of the PCs inaccessable over the network and causing other random problems. A Ghost DVD kept on site helps with this.

      Your idea has a lot of merit - in fact that's basically what most banks and similiar businesses use, PCs with just the OS, a broswer and telnet or OS/390 clients and maybe some Java Web Start apps.

      But the security of Windows is the weak link. It can be secured if you try, but it doesn't take much to leave it wide open to attack.

  28. I know where they are by Josh04 · · Score: 1

    In the bin behind somewhere which realised how useless they are. That's where I got my three SunRay 1's :P

  29. virtualised setup even by gedw99 · · Score: 2, Interesting

    I agree fully.

    With the KVM & the new spice drives, you can virtualise even your HTPC !!
    It does HD quality video over my network with no problem.
    This is in the basement.

    So all i need on All dekstops is a very simple thin client.
    100 mbit nic
    hdmi.

    1. Re:virtualised setup even by gedw99 · · Score: 2, Informative
    2. Re:virtualised setup even by Anonymous Coward · · Score: 0

      it does htdv quality?
      you sure?
      spice works mostly with lossless compression, but has algorithms to detect areas with lots of updates.
      it compresses those updates with mpeg, so it's a lossy compression.
      so you're not really having hdtv quality :)
      you need a gigabit for a 1440x900 video when using remote X connections.
      add some lossless compression and differential algorithms if you want (basically: spice), but a 100mb will hardly support a full-screen hdtv video.
      not to mention, full hdtv is 1980x1080, so even worse.

  30. CapEx vs OpEx by Krokant · · Score: 5, Insightful

    Don't forget that the biggest cost in a client is not necessarily the purchasing of the hardware (which is obviously the most visibile cost). Various studies (Gartner, IDC, ...) indicate that a PC that is purchased for $500 (one-time cost) in fact costs somewhere between $1500 and $4500 per year (!) to manage. These hidden costs are mainly into the backend infrastructure supporting these PC's in corporate environments, people managing them, deploying software on them, ... Google for desktop TCO and you'll find plenty of information. Sure, you might disagree with the exact numbers provided by a Gartner /IDC /Forrester but at least it gives an indication.

    For thin clients (and desktop virtualization for that matter), this is also where the cost savings are. No serious VDI vendor will tell you that the CapEx (investment in hardware, licenses,...) is cheaper with thin clients and virtual desktops: you need to buy additional licenses, you're going to run desktops on server hardware (ok, 100 at a time on the same box) and then I still didn't start about the licensing galore (Microsoft VECD, Citrix XenDesktop or VMware View or...). The real cost savings are in the fact that it's much easier to manage, and being able to let your very expensive system administators do something else than troubleshooting a desktop (which costs you twice for the end-user downtime and the sysadmin troubleshooting it).

    The same goes for thin clients: the up-front investment is larger, but they are very easy to manage (plug into the network and the thing autoconfigures itself, pointing you to your virtual desktop -- which means fewer expensive sysadmin interventions on-site for replacing hardware!), they live longer compared to traditional desktops (these used to have three-year lifecycles whereas thin clients typically have a five-year lifecycle -- roughly speaking you'll need to buy two traditional desktops for one thin client in a 5-year desktop lifespan; I'll concur to the fact that with the economic situation, you'll see prolongued lifetimes for both thin clients & desktops but the idea remains the same, numbers might differ today).

    So is the thin client cheaper? In most situations and looking at the total picture, sure it is. Even despite a higher up-front investment. The real problem is not really the price of a thin client but whether your applications and IT environment support thin clients/server based computing (TS/Citrix/VDI).

    Sidenote: I work for a consulting firm where I work a lot with VDI & Server Based Computing in general; we strive to be independent as possible (trying to nuance the vendor claims as much as possible for our clients) but that might mean I am a bit biased towards using SBC if it works ;)

    1. Re:CapEx vs OpEx by jra · · Score: 1

      As a very *very* rough estimate based on 20 years of doing this: your runtime support load is going to be proportional to the number of operating system installs you have to deal with.

      If you have 100 people running 100 copies of Windows on 100 PCs, you're going to have a lot more work than if you have 100 people running 1 copy of Windows on a virtualized server.

      The leverage is made even higher by the "just swap the box" and "sit down anywhere" factors.

    2. Re:CapEx vs OpEx by Anonymous Coward · · Score: 0

      you're a fucking tool.

  31. Refurbished? by Anonymous Coward · · Score: 0

    P4/512megs/XPpro/20gighhds business class refurbs for $60 plus a $60 15" lcd monitor and strip out what you don't like. I looked around and got an off lease IBM full of bells and whistles for $120. But I could have pulled all the excess parts, closed the holes and been left with a P4 3.0 with HT, 1gig memory, 10/100/1000 LAN, ATI graphics and onboard sound, four usb 2.0 ports, front mounted mic and headphone ports. That would be more than enough to boot a image off the network and use it for light duty.

  32. That's because thin clients are PCs... by itsdapead · · Score: 3, Insightful

    "I find many aspects of desktop virtualization compelling, with one exception: the cost of the thin clients, which typically exceeds that of a traditional box.

    Thing is, if you're using office productivity apps or database front ends (the usual applications for desktop virtualization) then the most computationally intensive part of the job is probably rendering the user interface - so your thin client needs to have pretty much the same CPU and GPU clout as the desktop it is replacing. The Flash RAM costs as much as 10x the amount of HD storage and (since most people expect Thin Clients to be Thin) you're probably paying a premium for laptop-class components. The only real saving is DRAM - which is dirt cheap.

    Also, since the main market for these is corporate, any retail prices you see will be inflated so that corporate clients can be offered a nice "discount".

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
    1. Re:That's because thin clients are PCs... by Anonymous Coward · · Score: 0

      Good points, except that a a maximally thin client does not need any local storage. They PXE boot a small OS (Windows PE, or Linux from scratch), set up to automatically launch VNC, an RDP client, or whatever is desired, pre-configured to connect to the correct server.

      From the Computer Engineers perspective, the thing is identical to a desktop except it comes with no hard-drive, or at best a small flash drive. So the simplest way to get a thin client is to order a low end desktop without a hard-drive. Any Linux admin worth his salt could cook up a PXE image for the computer. (It may take them a few days if they are not familiar with this, but it is well documented enough that they should all be able to do it).

      The only reason to go with the commercial offerings is for external support with the set-up, and a thinner system profile. Don't underestimate that set-up support. The vendors probably have pre-cooked boot images for many configurations, and if you want to have a thin client that can expose a local CD drive or thumb drive to the VM that does add to the complexity of the setup, similarly if you want smart-card login handled locally (rather than using Window's support for smart cards by exposing the local reader to the remote machine) that adds complexity, that the vendor may be able to help with.

  33. Thin clients, a dime a dozern by Anonymous Coward · · Score: 1, Interesting

    My suggestion:

    Step 1: Realize that almost nobody wants a laptop that has a busted screen, as it is often more expensive to replace the screen/backlight than it is to get a new laptop
    Step 2: Hop on eBay and purchase fully functional laptops with busted screens, with the intent of using the ubiquitous vga-out for your LCD monitor
    Step 3: If they have their hard drives pulled, boot them from SD or PXE.
    Step 4: Pat yourself on the back. You saved money, you recycled, and you basically have a mini-UPS system built into each machine.

    1. Re:Thin clients, a dime a dozern by Skapare · · Score: 1

      You just ruined it for me by spilling the big secret. Now the prices for all those busted-screen laptops are going up. And I was working on building a super computer cluster of the bottoms.

      --
      now we need to go OSS in diesel cars
    2. Re:Thin clients, a dime a dozern by shitzu · · Score: 1

      And that will very efficiently render all positive aspects of thin clients to ashes. Almost all of the reasons (in the way of TCO savings) of deploying thin clients in the first place rely on *the same hardware* running same configuration and system image. Running 200 broken laptops from ebay would be a fun sight, but would probably increase the cost ten times over traditional desktops, let alone thin clients.

  34. VDI and regular computer by AbbyNormal · · Score: 1

    Could do what we are planning and use existing workstations with VDI (http://www.vmware.com/products/view/features.html). Depending on your seat requirements, you may want to try pricing out a homegrown box of your own.

    --
    Sig it.
  35. ...cheaper? by Anonymous Coward · · Score: 0

    a nice computer costs 1000+$
    a good computer is 500+, usable 400+.
    you get clients for less than 200.
    that is *already* cheap, compared to the option of a full computer.
    it's already less then half of what a full computer would cost.
    if you want t3h ceapest, probably used computers are the only option.

    a full 22" monitor usually means that you'll need at least a gigabit lan, a graphic card of at least 64mb, or a good cpu if you don't have enough graphic.
    that's not so "thin" when you think about it.
    now consider that the market is small compared to the pc market, and i don't think thinclients costs so much anymore.

  36. Thin clients aren't fat enough for the cloud by jabjoe · · Score: 1

    The very people who think the cloud is the future, think everything will be written in .NET or JIT'ed javascript. Last few times the thin client idea failed it was because of control, but it seams like each time it comes back there is more over head (more than you might expect from Moore's law). This time I'm not convinced a thin client will cut it. What you need is native apps from a database, one safe place to find apps, and everything kept up to date......Wait that's a repository! Compare the two side by side, mmmmm, I'll use fast native apps from a repository please, especially on a crap machine!

    1. Re:Thin clients aren't fat enough for the cloud by jon3k · · Score: 1

      We've been using thin clients and Citrix at over 40 locations for over 6,000 employees for almost 9 years now.

      The "one safe place" to find apps is using Published (/Streamed) Applications to Virtualized Desktops. Citrix has been delivering published apps for a decade. Not exactly what we'd call a small, under-the-radar company.

      I don't think everything will be written in .NET or javascript.

      Thin clients never "failed".

  37. PC Overt IP aims at that problem. by maitas · · Score: 1

    But remember that retail price below 100 USD is extremely difficult becouse of shipping cost from Chine, retail space, etc.

    I bought an ASUS Eee PC 900A refurbished for 149 USD from Ebay, so add a VNC client (or the Goole remote desktop software they have just opensourced) and you have a pretty decent solution.

    The thin client idea is not about low price, is about beeing stateless. Here in Argentina I work with an ensurance company that has 100% of its apps web based, so they dont need and remote desktop solution, just a plain and simple browser (they can even use a chumby!).

  38. It's all about TCO and maturity of client/server. by Anonymous Coward · · Score: 0

    We are going towards thin clients and virtualized desktops at my workplace and I must say the price of the units are not that bad.
    If you get some volume the actually cost quite a bit less than a SFF PC, at least the entry level ones.
    I've been trying many of them (HP, Fujitsu, WYSE, Igel) out for quite a while and all of them can support 22" & 24" monitors at native resolutions.

    One thing to bear in mind when talking thin clients are total cost of ownership (TCO)
    The TCO of a thin client is far less than that of a PC.
    Not only because the user can't mess it up and because it rarely breaks down, but mainly unit installation and systems management costs.
    No need for endpoint security and expensive and complex distribution and inventory systems.
    If you work in a large environment with many branch offices you see the advantages immediately.
    There is basically no need for on site technicians what so ever.

    For an organization they become cheaper to own in the end, which is why they are compelling.

    The energy savings can also be substantial!
    I have been running scans on our few thousands of PCs for a while and the actual CPU utilization is about 15% average (this is on four-five years old HW, mind you), and yet the users scream for new HW.
    The real issue is network latency basically, which is why a centralized desktop solution with thin clients is perfect.
    To be able to streamline the performance of the server cluster to the actual usage of the clients saves our medium business ten's of thousands dollars each year.

    Couple this together with the fact that users get almost no network latency what so ever to databases and application servers and you have a sure business case.

  39. They're being eclipsed by cheap traditional PC's by intrico · · Score: 1

    You already included a link to $249 PC in your blurb, for example. $249 is dirt cheap when you look at how far prices have fallen over the past several years, and not far at all from the sub-$200 price point that you speak of. If the cost of a full-blown PC is already dirt-cheap, there will naturally be little economic incentive for a separate genre of thin client PC's.

  40. Right here baby by Anonymous Coward · · Score: 0

    Here you go: http://www.norhtec.com/products/mctc/index.html

    You're welcome.

  41. Not about cheap hardware by Anonymous Coward · · Score: 0

    The savings you can do with a thin client solution is not in the hardware, but in a more stable environment with less hassle for the user as well as support. I expect you to know this already, so what you need to do is to try to estimate total cost for a fat client solution compared to a thin client one and see if its profitable for you. The difference of a client for $200 or $90 every 4 year will not be what makes it viable or not.

  42. Easy. by Anonymous Coward · · Score: 0

    > Am I missing something here?

    Yes, a little thing called "mass production".

    First, TCs are cheaper on the whole -- e.g. it's harder for a thief to steal a TC (because they suck without servers), replacing is basically zero-configuration etc. etc. The cost of the TC itself (the equipment) can be more expensive and yet the whole solution be more economical (there's a plethora of other economies not mentioned).

    But, TCs are different -- which means they're not the commodity desktop PCs came to be.

    If you want really cheap, buy mass-produced PCs (I believe we've seen them reach USD$200 in recent times). BTW, depending on a series of factors, your current PCs might turn cheaper or not -- but surely they would avoid an initial investment.

    BUT: TCs are worthy as much as the central maintenance team. If you can't manage it well, TCs will flop...

  43. Elementary, my dear Watson by Ullteppe · · Score: 1

    Basically, the basis for thin clients making sense is the supposition that computing power is expensive (just as in the old mainframe days, when the premise was that making lots of terminals and then one big machine made economic sense). Guess what? That doesn't hold true anymore. Computing power is cheap. The "nicities" of good graphics support, decent I/O etc is more expensive than the processor. So why not include some decent processing power in the "thin client". In this case, it is just a regular low-end PC (stationary equivalent of a netbook) running terminal software.

  44. The Ultimate Thin Client by kurt555gs · · Score: 1

    I think this has been missed, but Android, and Chrome OS are really thin clients to Google's cloud with minor local functionality.

    The true NX type thin client, though good, is going the way of the Neanderthal.

    --
    * Carthago Delenda Est *
    1. Re:The Ultimate Thin Client by Anonymous Coward · · Score: 0

      Android, [...] really thin clients to Google's cloud with minor local functionality.

      My rooted apps to SD G1 running Debian would beg to differ on that limited part.

  45. Why HTPC? by Junta · · Score: 1

    'Thin-client' goes a bit far there. My HTPC is a diskless client that netboots a MythFrontend. This way, I transfer the pre-compressed streams (which will always be able to be more efficient than any real-time compression) to my box. The box has no storage and the computational complexity required is sufficiently low to avoid overly loud noise.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  46. Acer Aspire Revo AR1600-U910H by _LORAX_ · · Score: 3, Informative

    http://www.newegg.com/Product/Product.aspx?Item=N82E16883103228

    $200 and should drive a 22" monitor no problems, can't confirm PXE bootable, but with 160GB HD it should be easy enough to load up a netboot stack.

  47. A thin client or a web browser? by Anonymous Coward · · Score: 0

    With the inevitable move to web-applications and 'the cloud', wouldn't the ideal 'thin client' be an inexpensive nettop with a decent web browser?

    And if your organisation "is not yet ready for that move", install the thin client software on those computers so they still work in your old environment.

  48. www.devonit.com ($129 thin clients) by Anonymous Coward · · Score: 0

    I haven't seen anyone reference the firm we use. Devon IT (www.devonit.com) sells thin clients for $129. They aren't perfect, but they work well, they have no moving parts, and they can be centrally managed.

  49. See: "Network Computer" "Web TV" by DoninIN · · Score: 1

    As others have pointed out, the volume, among other factors have conspired to make the whole thin client network terminal a dead horse in the race for the last, what? 20 years? More like 30 probably. Not that there aren't applications for them, or that they don't have their own virtues. Just that since they remain a niche product for whatever reason, they remain more expensive in terms of bang for buck, than a traditional PC, which helps keep them a niche product. Rinse Repeat.

  50. You're looking at the wrong cost by Anonymous Coward · · Score: 0

    While there are some sub-$200 products out there, they all seem to cut corners (give me non-vaporware that will drive a 22" LCD at full resolution). I can PXE boot a homebrew Atom-based thin client for $130, but I'd prefer to be able to buy something assembled. Am I missing something here?"

    With thin clients, the biggest savings isn't in the cost to acquire. It's in the cost to operate and maintain. Compare a thin client to even a low-spec PC with a full OS that can have apps/viruses/spyware/etc installed.

  51. Long Term Costs by kibbey · · Score: 1

    It's not about the cost of the hardware. A large organization will want the cost of management and support to be low as that is an ongoing expense. A thin client that costs double what a PC costs can return that upfront cost over a couple of years worth of much cheaper support costs.

  52. choose any hardware and a good Thin Client OS by GurneyFox · · Score: 1

    Some Atom based Thin Clients are great machines, e.g. Foxconn's Qbox - though not fan-less which is a problem for some users. Most of the Thin Client operating systems are for certain boxes only (and seem pretty outdated), I'm very happy with LISCON OS which is Ubuntu based and runs on a lot of machines, e.g. the Qbox as far as I know. You can evaluate a demo version: http://www.liscon.com/lmd cheers

  53. We're building some by AppComp · · Score: 1

    SoC parts that can deliver such high resolutions have become available only recently, thanks to the HDTV boom. Before that, ARM or MIPS graphics were usually limited to portable LCD or NTSC resolution. We at Thinvent are building such thin clients, using ARM processors. Using the TI OMAP3505, we deliver up to 2048x2048 resolution. Using the TI OMAP L138, we can deliver up to 800x600 resolution, for screen sizes less than 10". Especially interesting is the market for all-in-one thin clients, where the thin client is built into the LCD monitor, allowing quick installation.

  54. Buy the cheapest Dell system and.... by gooneybird · · Score: 0, Flamebait

    1) Go out and do a volume purchase of the cheapest Dell system that meets your needs.

    2) Remove hard drives

    3) Sell hard drives on ebay to offset (reduce) cost of systems

    4) Use as thin clients

    5) Look for new job, after you got fired when the company you work for realized that thin clients suck and you had to go back and purchase hard drives for all of the systems

  55. We build ours by markdavis · · Score: 4, Interesting

    We use over 150 "thin clients" on our network, all Linux based and all controlled by a single (large) Linux [xdm] server. We used to use "real" thin clients (Xterminals) by Tektronix, but as their prices rose and the price of cheap, fanless, low power, small, VIA boards dropped 8-9 years ago, we decided to start making our own.

    We have not regretted the decision. Now we have complete control over the hardware and software. We have the ability to run real local clients when necessary.

    Right now, we are in the process of upgrading to fanless Atom 270 based motherboards from Jetway. Total cost- about $250/ea.

  56. + Volume Discounts by xzvf · · Score: 1

    Plus these same corporations buy in bulk. If you buy in 10K lots, you'd be surprised how low the cost per seat can go.

  57. I see it like this by garaged · · Score: 1

    It all comes down to "green technology", and I don't think I'm very wrong about it.

    --
    I'm positive, don't belive me look at my karma
  58. Why pre-built? by John+Pfeiffer · · Score: 1

    Anything 'pre-built' is going to cost too much or be otherwise unsuitable. It isn't hard to find Atom-based Mini-ITX systems for like $150. There's also things like that piece of hardware MSI was putting out that is basically the guts of a netbook in a package that mounts to the VESA mounting plate on the back of an LCD and has its own stand...though I don't know what that was supposed to cost. I would think a good Atom machine would be cheap, and more than suitable. (Perhaps even overkill.)

    Speaking of thinclients though, I actually have an old IBM hardware x-windows terminal. It's very cool. :3

    --

    Friend: "The NIC is misconfigured..." Me: "No prob, I'll just telnet in and fix it." *Silence*
  59. IMHO - they are a joke by pjr.cc · · Score: 2, Insightful

    I have two thin clients from either 1990 or 1991 sitting in my roof, and generally speaking that was the last time they were actually useful.

    The reality is that dropping a cheap desktop pc on peoples desk, having a data policy, and having file servers is alot cheaper than thin clients. The simple fact is that the market is mostly driven by joe blogs with his home pc and he has no use for thin clients (despite many attempts to make thin clients relevant in the home). When you talk about thin clients its always business and enterprise which instantly adds a 1000% mark up of any hardware. Joe blogs buys so many home pc's in fact that their prices are so competitive, unlike thin clients.

    Want to pxe boot some atoms? your not going to beat that price, but be prepared for some pain, because licensing thin clients (even your own) is ridiculously expensive at the backend.

    There has also been alot of hot air released into the IT world about "centralising data into the datacenter" which sound great until you actually do it. WAN optimisation does help, but only so much.

    On top of this, thin clients are a perpetual network nuisance. They seem like a good idea until you get 50 or more clients on the same network segment continuously sending tiny little video updates and realise "holy god my network is being flogged to death". It sounds great but the truth is that sporadic write from clients to a shared file server consume much less bandwidth (people will scoff, but you'd be surprised how much different the network profile is for x number of desktops vs x number of thin clients, even with the rather thin rdp protocol).

    There are places where thin clients are used however and heres why:
    1) Compliance - i know one place that uses them exclusively because they just cant afford for their data to sit on desktops. I.e. the data itself has to be in some central secure location
    2) POS/Kiosk type work - i.e. people at windows servicing clients
    3) people who bought into the concept and now regret it... I know too many of these.

    There are advantages to them, but when viewed with an eye to what people are trying to achieve they mostly become irrelevant when people realise policy (cheap) can easily dictate fixing the problems they are trying to fix with a technical solution. One great one i love hearing is how user X can login to any terminal (or even remotely) to the exact same desktop. How many of your users ACTUALLY need that? Can you seriously say that a terminal server for vpn with access to the same file shares and mail server cant give you what you need? Are your users running around random desks every day they come into the office? The truth is (assuming your on windows at work) that profiles will give your users pretty much all they need - a pre-configured outlook and the network shares they're used to seeing.

    The second one is data, stopping users from saving data locally where it might be lost. Well, this is were policy can save your bum. It'll cause some pain now and then (though rarely) when a user looses a bit of documentation cause it was saved on his desktop (Despite the bleedingly obvious file server sitting next to them on the network) and his drive failed but the reality is this is so very rare the cost of a thin client solution becomes rediculous in comparison.

    Thats my $0.02 anyways. Thin clients i find quite interesting, but they are rarely useful at solving any real problems except in niche and very specific scenarios.

  60. About your hangup... by Eric+S.+Smith · · Score: 4, Interesting

    I'm very hung up on spending more for less.

    Stay away from "enterprise solutions," then — or, rather, make very careful comparisons between the cost of buying a ready-made thing and a DIY effort.

    Am I missing something here?

    That the thin clients you've been looking at are priced for fat organizations (with, possibly, thick decision-makers).

    1. Re:About your hangup... by bill_mcgonigle · · Score: 1

      Exactly. Thin clients are an economic win if your environment fits them, even at their inflated hardware price. So, if you have an actual budget and need service and support, you buy the $400+ thin clients. If you don't have the budget you build them (pfft, snap-together is more like it) and have a half dozen spares on a half a bookshelf. You probably don't bother fixing ones that die, but they're all solid-state so they don't very often.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  61. The client is not the expensive bit by Anonymous Coward · · Score: 2, Informative

    Not just the cheap thin client, it is the data centre side where you really pay.
    From experience, thin clients save neither money nor power cost once you have taken the hit on the data centre side server, storage and networking capacity they will take and then the huge bill for the virtualisation management software. (assuming you are using Windows type thin clients, if you use SunRay and Solaris yes you can save some serious cost but most users will WINE until you connect the SunRay to RDP off a Windows server and giver them their familiar environment back)

    1. Re:The client is not the expensive bit by hoggoth · · Score: 2, Insightful

      > users will WINE ...
      > ...Windows server and giver them their familiar environment back

      I see what you did there...

      --
      - For the complete works of Shakespeare: cat /dev/random (may take some time)
    2. Re:The client is not the expensive bit by Anonymous Coward · · Score: 0

      "(assuming you are using Windows type thin clients, if you use SunRay and Solaris yes you can save some serious cost but most users will WINE until you connect the SunRay to RDP off a Windows server and giver them their familiar environment back)"

      it's pretty sad that you went anonymous thought i understand why. your ad for microsoft has been noticed. yes i consider your entire comment as a windows advertisement. anon as well,

    3. Re:The client is not the expensive bit by newdsfornerds · · Score: 1, Funny

      Users will whine. Then they will go home and drink WINE.

      --
      Damping absorbs vibrations. Dampening is caused by moisture.
    4. Re:The client is not the expensive bit by lordtoran · · Score: 1

      With your advertisement for expensive proprietary software you do one thing exceptionally well: totally miss the point.

      The article author wants to boot an operating system via PXE, with no OS actually being present on the client. Even if he were to do it the traditional "remote login" way, the OS on the clients doesn't matter, nor is it visible at all, only the server OS.

      --
      Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
  62. HP Thinclients by nukem996 · · Score: 3, Informative

    HP has their own Debian Linux based client client OS called ThinPro. If you want to add more packages all you have to do is add the standard Debian repo's to /etc/apt/sources.list and your good to go. They're pretty flexible if you know some basic Linux. The best part is they have a much fuller Linux base then many other Linux thin clients. They support even more advanced features such as multimedia redirection(video and USB) as well as the basic XDM, ICA, RDP connections. All of them can drive almost any monitor from a standard 17" LCD to dual 30" LCDs. The cheapest model is ARM based. Its basically a Marvell OpenRD or Netplug with a video card and smaller disk space. All the others are x86 based and vary in speed and price.

    1. Re:HP Thinclients by yacc143 · · Score: 1

      And the pricepoint of the cheapest is about a 4x 3.0GHz Phenom with 4GB, the prices of the more expensive are slightly more expensive than a Quad Phenom with 8GB RAM.

  63. Options by rwa2 · · Score: 4, Informative

    They're getting there, just be patient!

    I'm about the evaluate the Fit-PC2 for work, which can be had in diskless forms for under $250. http://www.fit-pc.com/

    And I'm currently posting from an EeePC 901 running eeebuntu, which is actually quite a bit better and can be had for under $200. Plug in an external monitor, and rig up the built-in LCD and peripherals as a fancy KVM switching interface for your various VNC, RDP, VMware, NX, etc. backends. I'm really impressed by the Compiz desktop performance, so you can still get pretty slick transitions between various sessions on different virtual desktops.

    And I'm really looking forward to the explosion of new nVidia ION netbooks and nettops, which will actually give a real nVidia 9400 GPU and dual-core Atom processors to these "thin clients", which means they can actually be used more or less like a real box in terms of running web-based interfaces and things without stuttering and pausing occasionally.

    So with a dirt-cheap nettop, unfortunately you'll pay a little bit more than your target, but at least you get extra features (like a small SSD, built-in speakers, keyboard/mouse/multitouchpad, and maybe even a webcam, etc. that you could probably put to good use with a bit of creativity.

  64. Why they never caught on... and what might change by Anonymous Coward · · Score: 1, Interesting

    There's little incentive for the traditional desktop makers to deliver cheap thin clients. It further erodes their already thin margins for desktops, reduces revenues, and puts a whole support industry out of work.

    There are a handful of companies making low-end computing devices based on highly integrated chipsets with some processing power. Freescale has some that aren't bad, and TI's OMAP 3530 series (see http://beagleboard.org/) is a good candidate. The definition of thin client will need to change, too - it'll become a diskless device that can run a virtual desktop off a server *or* a centrally managed browser using web-based apps (where rendering, playback is local.)

  65. Thin clients for under $200 right now by mrslacker · · Score: 2, Informative

    HP's offering: http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12454-12454-321959-338927-3640405-4063703.html - $199
    This is ARM-based mind.

    From Dell:
    http://www.dell.com/us/en/home/desktops/inspiron-zino-hd/pd.aspx?refid=inspiron-zino-hd&s=dhs&cs=19
    $250 right now, but was about $200 during black friday

    From Acer:
    http://www.frys.com/product/6054148

    $200, has been $180.
    To be fair, all these products are very recent, and I wouldn't expect anyone to be aware of them.
    There are others too, but they tend to cost more.

    1. Re:Thin clients for under $200 right now by Anonymous Coward · · Score: 0

      Ummm, did you look at those items? Only the first one is a thin client, the others are just very small computers running regular windows.

      HP's offering: http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12454-12454-321959-338927-3640405-4063703.html - $199
      This is ARM-based mind.

      From Dell:
      http://www.dell.com/us/en/home/desktops/inspiron-zino-hd/pd.aspx?refid=inspiron-zino-hd&s=dhs&cs=19
      $250 right now, but was about $200 during black friday

      From Acer:
      http://www.frys.com/product/6054148

    2. Re:Thin clients for under $200 right now by Anonymous Coward · · Score: 0

      Hi and please see following site for your information, Thin Client less than $150 at www.sunde.co.uk
      This is the new generation of multi user network computer terminal unit, Which effectively allows many users to share the untapped resources of a single host computer, while providing full PC experience.
      the revolution of Network Computing, it is a computing ready device. “The ultimate IT going green solution” means you enjoy the benefits of reduced hardware costs, energy costs, Air-conditioning cost, maintenance and support costs. And reduces the carbon foot print hence eco friendly.
      . There are many advantages to use this Thin Client:

      * Share a 1 PC with up to 40 users.
      *Save 70% on your hardware cost
      *Save 80% on maintenance.
      *Save 95% on electricity
      *Generate 95% less e-waste
      * Reduce CO2 emissions
      * Save time, Easy to set up
      * No hardware maintenance

  66. Re:They're being eclipsed by cheap traditional PC' by rdebath · · Score: 2, Insightful

    That's exactly his point, he wants that PC without the hard disk, CDROM or OS.

    What do you think that should cost? Maybe $150 ? Why aren't there any tickboxs to do it ?

    Why is there a separate genre of thin client PC's that cost so much more?

    Who is being conned here?

  67. Virtualization not the be all, end all... by Anonymous Coward · · Score: 1, Interesting

    For sake of this argument, let's assume that in your shop your users are running applications that benefit substantially from local CPU power. In that case, it makes a lot of sense to give the user a real CPU, not a shared, virtual one. You could use a stripped down PC as the "thin client." The cost of these devices are at the commodity level, and you can be assured that your getting what your paying for.

    Now, keep in mind, you can still leverage some the benefits offered by virtualization by using some of the abstraction/encapsulation techniques that are de-rigueur in virtual environments. The first step is to remove local storage from a standard PC and require that all of your remote clients will use PXE boot and network storage only (iSCSI or similar). Now, you will get the benefits of using network storage, without sacrificing CPU power. Specifically, this solution encapsulates the user's OS and application licenses in a single place. It provides increased reliability by giving every workstation RAID protected storage.

    This design which uses "virtual" disks only gives some benefits from a TCO perspective. For example, you can assign software to individual users, not local hardware. Users may use any available or job-appropriate workstation, and gain access to their licensed software, etc.

    I admit I haven't tested this extensively under Windows, and may be more picky about activation/licensing issues when moving to different local hardware. Linux would have absolutely no trouble with this mode of operation.

  68. Total Cost of Pnwership ! by redelm · · Score: 1

    As others have said, low volume of thin-client sales keep the price high -- high fixed costs per unit outweigh the savings in electronics & licences in a full PC. Note the unsharp competition.

    What you are missing is that first-cost (equipment purchase) is a very small part of TCO. The biggest cost is for user time doing maintenence/downtime. This has always been MS-Windows achilles heel, requiring ~10% user time for stability/security.
    At $10+/hr, it doesn't take too many hours to pay any differential in HW cost. This (and paranoiac security) have been the drivers for TC.

    Personally, I'm intrigued by the underlying concept of stateless computing. Of course an oxymoron, the idea of minimizing or focussing state is attractive. The anti-indirection. Starting with /etc and progressing (or regressing to .REG), others have also found the idea compelling. Very low state made IBM mainframes relatively unattractive compared to PCs, excessive state makes MS-Windows (and some perversions of Linux) hard to maintain. An optimum is still to be found -- on a clear disk [no goals] you can seek forever.

  69. SunRay by Greyfox · · Score: 1

    You can find a 24" flat panel SunRay for about what the 24" flat panel would cost. If they're on a decent network their performance is actually pretty nice. Check ebay first as you might find a bunch from a company that was testing them or has a deploy and is upgrading or something.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  70. Wyse for $219 by chemi392 · · Score: 2, Interesting

    From CDW: http://www.cdw.com/shop/products/default.aspx?edc=1199380&enkwrd=ALLPROD:(902114-01L)
    Wyse S50 for $218.99

    Supports RDP and Citrix ICA

  71. Economics 101 ... by smpoole7 · · Score: 1

    The retail price of something is rarely based on the cost to make the unit. This is a common fallacy. The retail price is primarily determined by what the market will pay for the unit. It's just that simple.

    The demand for thin clients is much smaller than the demand for full-blown, self-contained computer units (primarily driven by home sales).

    --
    Cogito, igitur comedam pizza.
    1. Re:Economics 101 ... by Eric+Smith · · Score: 1

      The retail price is primarily determined by what the market will pay for the unit. It's just that simple.

      Actually it ISN'T that simple, and Economics 101 will teach you that. The retail price isn't determined by what the market will pay. It is determined by the INTERSECTION of the supply and demand curves, and the cost to make a product is usually a major factor in the supply curve. If the demand curve doesn't change, but the cost of making the product changes, the supply curve will change, thus the intersection of the supply and demand curves will change, thus the retail price will change.

      The next step in refining the analysis would be to consider elasticity of demand. The PC market is fairly elastic, but not so close to perfectly elastic to render the cost of product completely irrelevant.

  72. Do you mean cheap or inexpensive? by diefuchsjagden · · Score: 0

    Cheap or inexpensive? to me cheap is crap and inexpensive means the value exceeds the cost

  73. I used to buy thin clients, but no longer. by CFD339 · · Score: 1

    Initially, these made sense for my application. Today, it makes much more sense to pay 30-40% less for a netbook that has faster processing, better graphics, twice the ram, much more storage, and doesn't need it's own keyboard and monitor. On top of that, power consumption is very similar and reliability is much higher.

    Nobody seems to see a netbook without the screen and keyboard for less money. Seems stupid, but for that kind of hardware that isn't in a netbook configuration, you pay over $500, while the netbook runs $300.

    --
    The problem with quotes on the internet, is that nobody bothers to check their veracity. -- Abraham Lincoln
  74. Shuttle X27D by Captain+Damnit · · Score: 1

    From Newegg: Shuttle X27D

    Add in a 2GB stick of RAM and you're looking at around $210-230 per seat. They PXE boot, work great with LTSP and Ubuntu, and they drive a Samsung 22" LCD at full resolution. How cheap are you expecting?

    If you want to go below that, you're going to have to start salvaging old machines and converting them to thin clients. But then, you're only saving the purchase price, and the real compelling savings with an Atom-based thin client is the 50+ watt power consumption savings.

  75. Why not this? by Anonymous Coward · · Score: 0

    Why not just buy used ex-corporate PC's that are already licensed for XP Pro and buy a couple of pallets of them for $40-$65 each? Add a couple of used laptops, say $100-$120 bucks, again licensed with XP.

    And have them running RDP to the terminal server and lock down the OS, including USB ports, etc.

    If one breaks, give it back to the computer recyclers and get another one from the pallet, clone the drive and away you go. Hire an admin for under 50k yr, and have him admin 150-200 PC's.

  76. Desktop virtualization is just dumb. by BitZtream · · Score: 1

    Why are you adding a layer of overhead?

    Really, why? Every 'feature' of VDI can be done without VDI, equally as well. VMware and the like didn't invent net booting, drive imaging or anything else like that, they just add an extra layer.

    There isn't anything you can do with VDI that I can't do with out it, equally as well, assuming that I buy standardized hardware, which is pretty much what you're doing if you're buying a bunch of prebuilt 'thin clients' anyway.

    Your thin clients for VDI have to have EVERYTHING that a full PC has, except a disk if you don't want to cache locally, its kinda hard to save a bunch of money on hardware when you are essentially using the same hardware, minus a $50 hard disk.

    You use the same processor, the same memory, the same mobos, mice, keyboards, video, sound, all of that is still there and is still standardized in your thin client. The difference is you're paying more for it being a 'thin client' for no apparent reason.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    1. Re:Desktop virtualization is just dumb. by jon3k · · Score: 1

      Well if I can put 100 users on a single dual socket quad core server + VMware View (or Citrix XenDesktop) and roll out 100 thin clients, is that less expensive (including management costs) than rolling out 100 desktop PCs?

      It's close to the same hardware but requires a lot less horsepower. I think we're using sub-1Ghz Via Eden CPUs and maybe 1Gb of RAM. We pay about $100-$200 less per seat compared to the cheapest desktop PC Dell sells, looking at the desktop hardware alone.

      Managing thin clients is much less expensive. They also use less power. Not one solution works everywhere, but there's definitely instances in which the TCO is much better for thin clients. For example, we have lots and lots of sites, but only a few dozen users per site. These sites are also spread all over the southeast US. It makes much more sense to roll out thin clients and centralize the desktops than have 50 or 60 network techs scrambling between buildings.

  77. $53 in China by franticek · · Score: 1

    Chinese webshops supply thin clients for as low as $53 w/free shipping worldwide.

  78. There are significant savings to be made. by Colin+Smith · · Score: 4, Interesting

    I think the savings in deployment and long term maintenance of these terminal units are just an illusion.

    1: Unix/Linux systems[10] use copy on write. You load an application or library once and use it for the many users who are running the same application. The application runs significantly faster because the CPU cache and even more significantly, disk I/O cache hit rates are far higher than on a desktop system which is running half a dozen unrelated apps. This means you don't need 1000 servers to handle the load of 1000 desktops, or even 100. Your system utilisation goes from ~3% to ~90%.

    Desktops. No maintenance. No 3 year upgrade cycle. The money can be spent adding business value instead.

    Your desktop support problems switch from a linearly increasing management headache to the logarithmically increasing infrastructure management headache which you already have anyway.

    2: You need a service desk anyway. You don't however need a desktop support guy for every floor, or local mail and file servers with the additional storage and management cost that implies. With a centralised infrastructure, distributed filesystems like AFS actually make sense, and can reduce or eliminate data duplication and duplication of business processes.

    3: In what way is a remote desktop one size fits all? 95% of business users barely need more than email. Those who do need more can be provided workstations/whatever if the advantage is obvious enough.

    4: You run a redundant distributed compute cluster. See Condor, GridEngine etc. The nodes are independent. Killing one, or even some of them just means others get used. You lose the network or network services? Exactly how useful is a standalone PC anyway?

    although terminals are able to a certain degree to deliver these, it is often awkward and demands more than a cheap disk-less unit.

    The cheap diskless units are bog standard PCs without disks. If you can stream it to a PC, you can stream it to a PC running as an X-term. ESD just isn't that difficult to set up

    [10] Windows terminal servers are another matter.

    --
    Deleted
    1. Re:There are significant savings to be made. by Jon+Anhold · · Score: 1

      Who still deploys desktops? I haven't had a work-issued PC that wasn't a laptop in more than 10 years.

  79. I've got mine. by hey! · · Score: 1

    It's in the trunk of my flying car.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  80. $0.02 by nietsch · · Score: 1

    That 2 cents must be in elbonian zlotys or such, as you advocate a straight windows solution on Slashdot. You could at least try to put some OpenGL over ip on Ubuntu servers and clients in the mix. D-

    --
    This space is intentionally staring blankly at you
  81. That's what I was wondering by zogger · · Score: 2, Insightful

    I didn't think a thin client was anything other than a diskless PC connected to a server. Seems like if someone needed a lot of them cheap, they could look for pallet loads of recent vintage/good enough specs off lease whatever computers from some corporation, where they remove the hard drives for destruction, and just use those. I bet you could get a bunch for fifty bucks apiece that way if you shopped around.

    With that said, some company that already had full workstations could just remove the drives themselves, then add some servers, etc to achieve this thin client goal.

    I guess I am just not understanding why less hardware has to cost more money, or is hard to find. Heck, my local rural town whitebox shop sells entire *bundles* of refurbed old business desktops plus crappy old monitors if you can live with a 15 inch one and keyboards, etc for 99 bucks, add 20 bucks for a 17 inch monitor. Pull hard drive, insert ethernet cable, add a server in the closet some place with some switches, etc. Just not seeing the problem here outside of the actual case might need to be tiny or something. If the guy found a deal for pallet loads with the hard drives and optical drives included, they could yank those and ebay them, then put the money towards more RAM maybe or setting up the servers, etc.

    There's always barebones deals, too, for "brand new".

  82. netbooks by Stephen+Samuel · · Score: 1
    I just played with a friend's netbook, while fixing it (turned out to be the PS cable).

    It's small, and simple. It netboots, has 1GB of ram and drove my 19"monitor just fine without any special work. For the price, you can just ignore the 9" screen.

    Don't bother buying the latest and greatest. Get machines that are near the end of their sales life. It's cheaper and they'll probably last just as long.

    --
    Free Software: Like love, it grows best when given away.
  83. Tech standard obsolescence forces upgrades by billstewart · · Score: 1

    My last major desktop upgrade (other than disk and RAM) was when the bright purple flash let the magic smoke out of my P266 machine - I replaced it with a 2.4GHz Celeron. I'm about to have to upgrade again, because I want a better display, now that you can get high-resolution LCD screens for under $200. The problem is that my current graphics card can only drive 1280x1024 VGA, so I'll need a new card, but most cards that can do more than 1400x900 use PCI-Express, not AGP. So if I want a new screen, I'll need a new motherboard. Alternatively, if I want a new internal disk drive, they're all SATA these days, so I'll also need either a new SATA card, or just a new motherboard. And of course if I'm getting a new motherboard, that'll need a new CPU :-)

    The alternative is that there are some little $200 Atom-CPU boxes that have HDMI; the problem is that they typically come with 1GB RAM and don't say if you can upgrade that (and sorry, 1GB isn't enough for Firefox these days, much less fancy video stuff.) They also need external disk drives to add any significant storage, but that's tolerable.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  84. The elephant that no one has mentioned. by sgt101 · · Score: 1

    Well on Score 5 to be honest - because I don't read below that unless moderating or following a thread I won't say for sure!

    BUT : CELLPHONES

    cheap internet clients by the millions, or billions.

    There you go. The elephant in every room.

    I wish I worked for Vodaphone, there would be nothing to worry about.

    --
    --------------------------------------------- "In the end, we're all just water and old stars."
  85. I am investigating thin clients... by Hymer · · Score: 1
    I am working on the same problem, we require min 1920x1200 in 32 bit color and max. 50W power consumption. I've looked at following boxes:
    • MSI WindBox2 (Atom n270, Intel graphics): OK
    • HP t5735 (AMD Turion, Radeon graphics): OK but no PXE-boot.
    • eBox-4860 (VIA Esther): OK
    • FitPC2 (Atom): Resolution only 1600x1200

    All of those are capable of LTSP either as PXE-boot or disk-boot (HP only disk-boot). The HP is quite nice but I can't get good sound quality out of it, none of them can deliver full screen video in good quality (HP is best due to the good GPU) All uses std. PC keyboard and mouse, std. laptop RAM and got either 44-pin PATA (HP & eBox) or SATA interface for flash/ssd/harddisk. Right now we are using them as semi-thin clients, they got OpenSuSE 11.x with KDE but with all user applications removed except

    • Citrix client
    • rdesktop
    • VMware OpenClient
    • VNC client
    • Firefox
    • VLC (We want people to be able to use the Internet directly from the thin client with full multimedia support.)

    There are some funny features like: 10+ levels clipboard (from OpenSuSE), Alt-Tab changing between client task instead of server task, mounted USB-drives are not at the root of the drive on Citrix server, they are in a directory. We do not have any graphic-heavy applications (we are a financial business) so it is woking quite well. I've recently read that SAAB (no, not the almost killed by GM car company) are testing CAD/CAM on thin clients... ...and they are quite sure now that it will work.

  86. minimums by Eil · · Score: 1

    Well, it's kinda like hard drives. There's a minimal cost to make the drive no matter how much space you make available on it. You pretty much never see a brand-new hard disk selling for less than $40, even if it can only hold some absurdly small number of gigabytes.

    Same goes for computers. Even if you use old technology, you have to price the unit to cover the up-front costs of design and licensing as well as the ongoing costs of manufacturing and logistics. By the time you get your unit out the door, it's $150-$200 retail and most of your prospective buyers will look at it and say, "Heck, we can get second-hand Pentium 4 desktops for $99 a pop. No thanks!"

  87. Yes, you are. by ogl_codemonkey · · Score: 1

    Am I missing something here?

    Perhaps the 'sort by price' option in the link you provided?

  88. Thin clients are not cost effective by bbasgen · · Score: 1

    We did an extensive study and pilot of thin clients recently. Even at $260/thin client, when you consider the back-end servers, storage, VM licensing (on both the server and thin client), and recurring costs -- thin clients worked out to be about $710/unit. We currently buy desktops for $650/unit, and this actually gets worse over time due to licensing costs.

    1. Re:Thin clients are not cost effective by n2art2 · · Score: 1

      If you only count hard costs, your mostly correct.

      Soft costs however have huge savings. *If your soft costs don't see savings, then your IT people are bloating their work load or need retrained or fired.* Guess what the install and build out time of a thin client is compared to pushing an image over the network or even done locally? Grab a USB drive with the master image for the terminal. Connect it to the terminal, boot up the terminal, and hit Y twice. 20-30 seconds later, pull the thumb drive and reboot. Multiply that times 200 or 500 or 1000 or more PC installs, and image builds.

      That's initial build out time savings, that is huge. Now look at what happens going forward. Software installs, OS updates, security updates. No matter how automated you think you have it with your desktop pc's, it's still much quicker using terminals.

      Now look at large companies with multiple desktop support specialists on staff. Install terminals, and get rid of half of those positions. More costs savings.

      Again, if your not seeing the soft cost settings, then someone is not doing their job right.





      Disclaimer: CCA, and CCSP (If you don't know what those are, then your using the wrong software to effectively support your terminal/server infrastructure.)

      --
      Self proclaimed wannabe geek. You know how it is. Most of us who read this stuff probably fit in that category.
    2. Re:Thin clients are not cost effective by bbasgen · · Score: 1

      Actually, we find something even more problematic occurs: the workload has increased to our more valuable staff. Server and desktop virtualization has added time to our sysadmins work load, where before they had exactly *zero* involvement in desktop management. Now they are a key piece. While there are offsets in terms of helpdesk time spent on the thin clients, it is a failing trade-off to save the time of field technicians by giving sysadmins more work.

    3. Re:Thin clients are not cost effective by jon3k · · Score: 1

      Then it's poorly implemented. Once a virtual desktop solution is setup, they basically run themselves. You should just be using less helpdesk technicians to support the same workload, those same (but fewer) techs should just be able to do it without leaving their desks, for the most part.

  89. bullshit topic by Werrismys · · Score: 1
    a working X11/RDP thin client costs under 200 euros.

    A typical workstation costs 500-600 euros.

    WTF was this about again?

    --
    'Once scientists, even the dim-witted social scientists, get muzzled, the Western Civilization is finished.' - oldhack
    1. Re:bullshit topic by jon3k · · Score: 1

      A sub $200 thin client is either awful or includes no management software and I can buy brand new HP desktops for $300.

  90. Pano cube by Anonymous Coward · · Score: 0

    We've had good experience with the Pano cubes.... they run vmware images, so it's easy to push out templates. And the unit is soooo small. No fans, nice performance. I think it's 2.5x.2.25x2.5inches, small AC adapter too.
      Only problem is that it will not do dual monitor without a weird adapter ( and it's VGA, not DVI ) And the video card is crap ( but you're limited to VMware's compatibility there anyway )

  91. The economics of less-than-worthless trash... by evilviper · · Score: 1

    Want a thin client? To hell with hardware variation! A default Linux kernel, out of the box, can boot damn near anything, and access every network card I've come across in years, and X11's VESA driver can handle just about every display out there. Keyboards and mice and a no-brainer.

    Setup a working PXE net boot environment with all your thin-client apps, and go. Drop in any old surplus PC, found in any dumpster, anywhere. 98% chance it'll work. If it doesn't, write it off as trash and spend $30 on the next forklift pallet of 'em, or in my case, point the supervisors to the pile...

    Old PCs are hazardous waste. Even if they work, companies actually have to pay people to take them away. Every company that's been around more than a decade has them, and they're just warehoused somewhere. Drop them in and go. If you're a new or expanding fast enough that this won't work, you literally can find off-lease equipment in bulk for under $50/each.

    Buying a thin client is akin to buying bottled water...

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:The economics of less-than-worthless trash... by jon3k · · Score: 1

      Yeah and I'll only have to hire 15 guys to scrounge around for old PCs all day in classified ads and pick them up in trucks. Not to mention transport, clean, test and maintain them. Oh and what's the failure rate again? How often do I have users sitting around twiddling their thumbs because their $30 dumpster PC caught fire in the middle of the day?

      Sounds like a brilliant way to run a business.

    2. Re:The economics of less-than-worthless trash... by evilviper · · Score: 1

      Yeah and I'll only have to hire 15 guys to scrounge around for old PCs all day in classified ads and pick them up in trucks.

      Spoken like a true idiot. Off-lease and surplus PCs are purchased by the forklift-pallet load, from companies who specialize in this.

      Not to mention transport, clean, test and maintain them.

      You do not clean, test, or maintain them. They are throwaways. You plug them in where they need to go, and when the ~5% don't work, you throw them away and swap with another.

      How often do I have users sitting around twiddling their thumbs because their $30 dumpster PC caught fire in the middle of the day?

      Out of hundreds, we've never had one catch fire. And users don't just sit around if their terminal dies, they stand up, take two steps to another one, sit down and start working again.

      Sounds like a brilliant way to run a business.

      This is how real businesses work. The fact that you're convinced it can't work just proves that you know practically nothing about the subject.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  92. As someone who has recently worked in the TC biz by Anonymous Coward · · Score: 0

    I have recently worked in the Thin-Client (TC) enginering division of HP, so I can tell you, with some authority, that what you're looking for is not a TC. You're looking for a cheap desktop.

    A TC focuses on security, simplicity, and low energy consumption / heat generation. A TC company spends a LOT of money on engineers who work very hard locking down a TC's OS and physical access ports to make sure it is secure, making it simple to use and maintain, and making them run at as cool and at as low a wattage as possible (23W TC vs. 250W desktop).

    Security is important because a company that uses TCs uses several hundred at least, and usually thousands or tens of thousands. When an IT department is looking to buy TCs, they're for users who don't know a lot about computers, like car rental agency reps or hotel front desk reps who just need to check what cars/rooms are available, process your reservation, etc. Another major use for TCs is for grocery store checkout lanes, including self-checkout lanes. That's why security is so important. Most of these employees know just enough about computers to cause problems through their ignorance, and when the anyone has access to these machines, via self-checkout lanes, you need to make sure they are secure from hacking.

    Maintenance is a huge problem because these companies may have only 5-10 units at any one branch, but multiply this out to hundreds of branches, and maintaining them becomes a massive problem. You don't want to pay for IT personnel to travel around the country, and outsourcing the maintenance to local companies is also cost prohibitive (as well as impractical). TCs are attractive in this scenario because you can simply have the branch manager mail a broken TC to your IT HQ, and mail a replacement back. Anyone can plug in the replacement, and it's immediately good to go. Doing this with a desktop computer costs several orders of magnitude more, because special care has to be taken to make sure the moving parts, which a TC doesn't have, are secure, and the whole thing is padded well. Desktops are also much heavier, and directly cost more to ship as a result.

    Lastly, you have to remember that the initial cost of a computer is often less than the cost of energy to run it over the device's lifespan. Cooling a device, when enclosed in a grocery store self-checkout system, also costs energy. Now that many grocery stores, hotel front desks, etc., are open 24/7, the total energy cost is significant.

    So what you are looking for, my friend, is a cheap desktop. A TC is not what you're looking for.

  93. containing virus outbreaks is FAR easier. by logicassasin · · Score: 1

    Problem: desktop user downloads email attachment "Happy Birthday from Nigerian Banker.exe", virus/trojan is unleashed on your network and attempts to spread.

    Solution: In a VMWare View/thin client environment, you take any infected user's virtual desktop offline and push a fresh, clean version to them. Reprimands will be in order for the person resposible, but work stoppage will be reduced to a minimum AND the effort can be handled by one person instead of a team of people to clean up the aftermath.

    --
    Fifty watts per channel, baby cakes.
  94. HP t series by jantman · · Score: 1

    The HP T-series thin clients are quite nice. I have one in production driving a wall-mounted display. It's a t5000 series, specifically the t5735. It has DVI, VGA, parallel and serial, audio, USB, everything that a normal desktop has, AMD Sempron 2100+, 512MB RAM, 1 GB internal flash, and runs Debian Linux 4.0. By default, it has a stripped down Debian install, but has Gnome and gives you root access - I just added the packages that I needed and was ready to go (though it also has software for Citrix and RDP, etc. HP lists it for around $500, I got an open box demo, with full warranty, for $130.

  95. You are missing some things, this is certain by Anonymous Coward · · Score: 0

    SymbolNOBODY:

    You said what's quoted below from you, here -> http://slashdot.org/comments.pl?sid=1476008&cid=30428430

    "It's tolerated (perhaps encouraged) in part because these annoying actors are otherwised engaged in improving Linux. Major Debian and BSD contributors, for example, use slashdot as a workspace for their human-machine interaction side experiments, of which APK is probably one. In addition many of these trolls post links which, if you follow them, will completely hose a Windows machine. This is part of the game. - by symbolset (646467) on Monday December 14, @01:15AM (#30428430) Journal

    I took offense to the BOLDED part... & ALL you EVER seem to have is "ad hominem" based attacks on people, not the points they make. So, my reply in the URL below was simple (and logical):

    http://slashdot.org/comments.pl?sid=1476008&threshold=-1&commentsort=0&mode=thread&pid=30428430#30430244

    Additionally, "symbolNOBODY"? Well - the day you can make something like this (& that got you PAID for it, & that has done as well for others online):

    http://www.tcmagazine.com/forums/index.php?s=b861a743aa23c4568b7d73e07ef7ecec&showtopic=2662

    That's also gone over 250.000 views worldwide in 1++ yrs.' time online, & across 15 forums where that guide for Windows Security has been made either an:

    1.) "Sticky/Pinned" thread
    2.) An "Essential Guide"
    3.) Rates 5/5 stars (etc.)

    AND, gets "feedback" like this from users that have applied it:

    ----

    http://www.xtremepccentral.com/forums/showthread.php?t=28430

    PERTINENT QUOTE/EXCERPT:

    "...recently, months ago when you finally got this guide done, had authorization to try this on simple work station for kids. My client, who paid me an ungodly amount of money to do this, has been PROBLEM FREE FOR MONTHS! I haven't even had a follow up call which is unusual. Now I don't recommend this for the average joe, but it if can work for a kids PC it can work for anything! Now, i substituted OpenDNS and activated the Adult Content filter with them for this kids computer. I know its not perfect, but will catch over 99.5% of said sites."

    and

    http://www.xtremepccentral.com/forums/showthread.php?s=10f9ba9ad5ff990aaae1e7ec91f593a2&t=28430&page=3

    "Its 2009 - still trouble free! I was told last week by a co worker who does active directory administration, and he said I was doing overkill. I told him yes, but I just eliminated the half life in windows that you usually get. He said good point. So from 2008 till 2009. No speed decreases, its been to a lan party, moved around in a move, and it still NEVER has had the OS reinstalled besides the fact I imaged the drive over in 2008. Great stuff! My client STILL Hasn't called me back in regards to that one machine to get it locked down for the kid. I am glad it worked and I am sure her wallet is appreciated too now that it works. Speaking of which, I need to call her to see if I can get some leads. APK - I will say it again, the guide is FANTASTIC! Its made my PC experience much easier. Sandboxing was great. Getting my host file updated, setting services to system service, rather than system local. (except AVG updater, needed system local)"

    Thronka - forums member @ xtremepccentral.com

    ----

    THEN, when you have done so, on THAT account? THEN, you can talk!

    Also?

    When you have done all of this as I have over time in this Art & S

  96. the point by itzdandy · · Score: 1

    I think you are missing the point on thin clients. A PC for a basic client has a pretty limited lifespan and tends to require in-the-field support. It also requires antivirus software, some level of routine maintenance, and has a substantial failure rate in either software or hardware. A thin client lasts a very long time and needs basically zero in-the-field support, no antivirus(server side A/V instead), etc etc.

    When you licenses office or terminal services use, you tend to get better pricing than standalone versions and with software assurance you can stay with the most up-to-date versions for a reasonable price.

    The Thin client costs as much as a PC up front but will last 2-3 times as long, which in a big picture thought process means they cost 1/2-1/3. Less IT guys in the field saves money in wages.

    Thin clients typically burn 20-30W where a PC will typically burn 180-220W. A single PC can cost $160-200 per year in electricity and a thin client just $13-15. if you have 200 stations thats a difference of $32,000 vs $2600. If you design to have servers run desktops and separate server run apps then you can likely get 200 users into maybe 4 servers (An RDP server and 3 Application servers) and have a nice thin-client system with web and office.

    Other benefits are that every user runs the same version of software. Every user has access to the same storage for documents. much more confidence in security settings being applied as there is no local PC to hack on. Have a user with special software needs? You can assign a user to a Hyper-V instance running the OS and software they need. Need to help a user to do something? RDP allows you to share there desktop easily without another package and at reasonable performance.