A few weeks ago I debated with a friend of mine about what kind of consumer would purchase the upcoming Windows Home Server, which can be thought of as a file server for non-technical people. I’m am fairly certain that there is a market for people who own multiple PCs and recognize the need for a central location for their files and automated backup routines, but do not have the technical know-how to set up their own file server.

This friend argued that any knucklehead could follow a few simple instructions to get an old PC up and running as a file server using any flavor of Linux. Tonight, I have learned that this fairly straightforward task is beyond my skill.

I’ve got an old Dell Dimension (Pentium 3 550) that has been running Ubuntu for several months now. I was pointed to this tutorial which demonstrates how to turn an Ubuntu machine into a simple file server that can be read by a Windows PC. Imagine my surprise when I could not get this thing running; all of the other users who posted on that Digg page mentioned how easy it was and even that there were better soultions out there.

Now that I have wasted two hours trying to get this working, I have realized the genius of Windows Home Server. I buy a headless PC, drop a CD into my Windows XP PC, and run the install program. That’s it. No installing Samba or an SSH client. Not a single command line. No *NIX snob looking down his nose wondering why I’m too dumb to figure out how to get this running.

(Well, that’s the idea. We’ll see if it is really that simple).

The most frustrating part of this is that I work with this stuff every day. I’m no stranger to Linux, and I am quite comfortable on the command line. There’s just something about getting these machines to talk to each other that mystifies me. I suppose when HP rolls out their MediaSmart Server I’ll be first on line to pick one up.