My first `real' job was at a printing company in my hometown. When I started there, my job was to take a bunch of old 286, 386, 486, and Pentium systems and shuffle them around so we only had 486s and Pentiums. In the beginning, almost everyone (except the programmers and network admins) had diskless workstations that booted off the network. It put a heavy strain on the servers, though, because each person had their own copy of Windows 3.1 (oh, before I forget, this was in 1997). Many of the workstations (the ones out on the floor, for instance) just ran DOS and a scripting system called Metaview.
The irony of it was that even though we were moving forward by installing hard disks and putting a (mostly) 32-bit operating system (Win95) on these computers, we were in fact taking a large step backwards in the ease-of-administration department. Since most of the systems were similar, you could log into almost any of them with your regular username/password. When we installed the OS locally, that was no longer the case. Well, you could do some stuff, but you didn't have your familiar desktop and other configuration information.
In businesses and other large organizations, we see the same problem. There are people out there trying to fix it, such as Sun and IBM, with their thin-client systems, but I don't think enough people are seeing these problems in their proper light. Microsoft seems to be ignoring the problem, but then again, I don't really like to keep watch over what Microsoft is doing (besides, it's a pretty huge company at this point).
I'm not sure if Linux is the solution, at least not the Linux we see today. IMHO, the Unix user/group model is a little too simplistic. I think a larger hierarchy system might be in order. Of course, the more complex your user/group system, the less likely people are to use it. Hell, the Unix user/group system is usually not put to its fullest potential. Beyond that, I think a good caching network filesystem would be good for client systems (for example, when you run Matlab, it would copy the files it used to the local disk, so they will load up quickly the next time).
Well, it all depends on how much money and time people want to spend dealing with this stuff..
Update, a few hours later
Hmm, maybe I'm really looking for Plan 9 or a similar OS. I remember that I gave Inferno a half-hearted try a few years ago, but it would seem to me that it would be best to use an operating system that has been largely designed to work with the C programming language (well, plus others, but..)
It seems there are some really good ideas out there regarding distributed computing.. Makes Beowulf look really lame, IMHO..
Linux has been a really good system for me. However, I started using it because it was stable, 32-bit, and because it supported my SoundBlaster 16 (when OS/2 did not). That's not enough of a reason for me anymore. I want an environment that helps me to collaborate with others by allowing me to easily and securely share data and messages, keeps my data, documents, and media files organized, and helps me remember when I have homework due ;-)