A couple years back I rolled out a thin client solution for the billing department of a medical provider. Granted the back end was a Windows server but it was a great success. In our case we used some Neoware (now HP) clients. We did have a lot of old proprietary HP 120Mhz machines sitting around that we could have used but decided on new equipment. Some of the reason were we didn't want to support 5-8 yr old fat clients. For the old computers still being used fans, hard drives, power supplies, and the occasional mobo would die. We would scavenge parts where we could but the whole point was to move away from senseless jobs. A mini form factor that ran cool with no moving parts was a great move. We mounted the box on the underside of desks as well as set them on desktops. The clients and managers were happy to see such a small footprint. It may not be an important thing to a techie but the solution was for the client not for us. We also reduced the need for some licenses, a single TS server'a antivirus covered the terminal servers, while we still needed TS cals for Windows (argh) we did not need a desktop OS cal (they ran Linux w/RDP). Maintenance was non-existence, group policies locked the user's desktop, all-in-all a great solution. About the only thing I agree with on Bill's post is the need to centralize data. That should be part of any fat or thin roll out. These days I still roll out thin client solutions. On average I can replace 30-50% of desktops in new build-outs. It does depend on your environment though - I support mainly medical offices. And there are times where it is a complete crime to try to force a thin solution. Rich. »