Almost without exception, the first reaction when people hear that Microsoft is working on Windows Home Server is, "Why would I want that?" After they see it, the first reaction is much simpler: "I want that."
So set aside that first skeptical reaction and take a close look at the image gallery I've assembled showing the most recent beta release of Windows Home Server in action. The April 2007 Community Technical Preview (CTP) was released to the public last week. I've been running it and its previous beta release for more than two months now. In this post, I'll provide a high-level overview of why this new product has such potential for home Windows users who are drowning in digital media and typically unprepared for sudden data loss.
Let's start with a description of what Windows Home Server isn't. It's not a general purpose file/web/application server. It doesn't require high-end hardware (an old P4 with 512MB of RAM plus a Fast Ethernet card will do just fine). You don't need a technical degree to set it up or run it. In hardware terms, it's an appliance (no monitor, keyboard or mouse required, and the smaller the better) designed to plug in to a home network, where it's always on and available for a variety of useful activities. A nontechnical end user should have no problem installing the client software and walking through the simple seven-step setup, after which it requires virtually no ongoing management.
So what does Windows Home Server do?
Next –>





