Initial Thoughts

In assessing the value of Windows Home Server, for even a "simple" product like it with only a handful of core functions, there are a number of variables that really need to be taken into consideration. We can't give a blanket recommendation on WHS as a result, as the decision to use WHS rests on the variables to take into account for each user/household that a server would be installed in.

The chief variable is cost, and even this is in several forms. WHS is a new product, not any kind of upgrade, so using it is a matter of either buying an OEM box, or building one yourself, which can dramatically affect the actual cost. For enthusiasts with suitable hardware practically collecting dust, WHS is the cost of the OS plus minor costs for additional parts such as a gigabit switch. For more normal home users or enthusiasts without the spare parts, WHS means making an investment in new hardware. WHS has very low system requirements, so high-end OEM configurations will be well below the cost of a high-end computer, but it will still be in the neighborhood of a low-to-mid range computer.

Then there is the issue of the price of the WHS software, which we don't have. We're confident it will be between $100 and $200, but that's a very large range. We do know what the pricing will be outside of North America, and after converting currencies we are seeing $175-$200 in most regions. Microsoft's software is seldom more expensive in North America than in other locations, so this is a solid cap, but as they do charge less in North America on some pieces of software, it's not a solid floor.

The final element in the cost equation is the number of computers in a home. If you count WHS solely as a backup suite, in a house with the maximum of 10 computers the per-computer cost for having a top-tier backup suite is at most $20. This is more than competitive with other backup suites sold at retail. And then there is everything else WHS can do too; what's the value of an easy to configure file server? A web server? Various Linux distributions come close in some features but don't offer an equal feature set overall, so we can say WHS is overpriced compared to a free operating system, but...

And then we need to ask if WHS is even ready for use yet. HP says no, and they're holding back the launch of their WHS products from a September ship date, towards November and later. In doing so they're citing their desire to wait on third-party add-ins, on which development started much later, to catch up to WHS. Furthermore the WHS team is already at work on some unspecified updates that HP wants to wait for.

As a matter of opinion - and we're not disputing HP on their own choices - we think it is ready, especially for the enthusiast crowd that is the main audience here at AnandTech. We haven't encountered any noticeable bugs in using a WHS server even with the release candidate (although undoubtedly there are some lurking beneath) and the interface is more than easy enough for any enthusiast user to deal with. WHS is ready for the enthusiasts that want it.

We're a bit more tepid on recommendations for typical users however, some of which is due to our own inability to measure what counts as "average" computer knowledge these days. WHS is not caveman-simple, then again neither is Vista if you go far enough off of the beaten path. A bare minimum amount of computer knowledge isn't enough to properly operate a WHS server if we're talking about how it comes in the default Microsoft configuration; OEMs will be adding their own spice to the out-of-the-box experience.

But on the other hand Microsoft has done a great job simplifying the controls for what is really Windows Server 2003, and someone doesn't need to be an enthusiast to use it. With a level of knowledge above the bare minimum it's very possible and easy to make a WHS server work. And frankly, actually using (as opposed to configuring) a WHS server is extremely easy once it's set up; this is something even users with minimal amounts of computer knowledge could handle if a big box electronics store set up the server in the first place.

The next issue then is the feature set, and if it justifies the effort and the price. WHS is a file server/NAS, it's a backup suite, it's a webserver, and more. We really, really like the folder duplication feature (even if it is really just a poor RAID 1 knock off) because of the excellent ability to select what does and doesn't get extra protection. Most of these features work quite well, and we have no problem justifying WHS when two or more features are going to be used, since other devices WHS is in direct and indirect competition with are limited to only one function. A critical mass of computers is still required, but a couple of computers that receive heavy use would but enough to reach that critical mass.

Finally, there are the issues that have cropped up in our time with WHS that are outright design/feature problems. We speak of course about the nagging integration between WHS and Media Center functionality. If you have a full suite of Microsoft products (Xbox 360, MCE, and normal Windows computers) and want to use WHS as a media repository, it's simply an ugly mess. It can be made to work for the most part, but it's not a smooth experience out-of-the-box, and should be a lot better. There's going to be a lot of people - ourselves included - taking a hard look at WHS 2.0 to see if Microsoft has done a better job at integrating MCE and WHS into one box. This isn't a problem that kills WHS, but it does present a problem.

Particularly as enthusiasts we like WHS and consider it a product that justifies the costs of adding an entirely new device to a home environment. It has its flaws, but what it does well it does well enough to overcome those flaws; Microsoft 1.0 products have a bad reputation (and not for the wrong reasons, either) but this is one product where Microsoft has come out and managed to get things right enough on the first try. Starting with WHS it can seem to be a schizophrenic product, but in the end it comes together once you know what you want to use it for.

Our only caveat here is that it will take some time for most people to figure out just what those uses are. Microsoft will be releasing a 120 day trial of WHS soon, and we'd highly recommend trying it out and discovering the variables for yourself before purchasing the software or hardware for a server; not everyone will find it useful enough to purchase. It's also worth noting that while Microsoft doesn't officially support this, as a server product WHS works particularly well in a virtual machine since there's no need for high graphical performance. A virtual machine can be a good way to go through a WHS trial without taking any other risks.

Performance Data
Comments Locked

128 Comments

View All Comments

  • Aileur - Tuesday, September 4, 2007 - link

    Nice articule!
    First of all, a typo (im guessing)
    Page 7: Simply put, there is no integration between the two. By default WHS and MCE are completely //obvious// to each other.
    Im guessing that should be oblivious?

    And a question:
    On page 6 it is mentionned that there is a solution for non domained networks and all that. Fine, but what if i DO have a domain? Is there any way to integrate it without using that bypass method?
    Can it (whs) be my domain controller?

    Thanks!
  • Ryan Smith - Tuesday, September 4, 2007 - link

    Unfortunately WHS does not have domain controller support. I haven't seen a reason why, but it's a safe assumption this is so there's a greater difference between WHS and 2K3SBS.

    It also doesn't support joining a domain.
  • yyrkoon - Wednesday, September 5, 2007 - link

    Does not even have software RAID support, at least the last time I ran the beta . . .

    cannot believe you guys are just_now writting an article on it, but, I suppose maybe you guys had a NDA in effect ? Anyhow, I have a hard time embracing *any* OS that is supposed to be a server product and does not implement software RAID period, but I supose they think their backup scheme is better ? No reason to 'force' it onto others.

    The main reason I think it does not have a DC is that this is meant for home storage only. I.E. a very limited form of Windows 2003. I ran it on my secondary system for a few days, and decided I would probably rather run XP Pro, or Win2003 datacenter(or one of the other variants, maybe even Linux) at this capacity.
  • PrinceGaz - Wednesday, September 5, 2007 - link

    Just a wild guess from me here, but I think most home-users would be put off by the US$ 2,999 price-tag of Windows 2003 Datacenter edition.
  • mino - Tuesday, September 11, 2007 - link

    Good guess :)

    Anyway, Win2000 is pretty much enough for any home serving and 2nd-hand licences goes pretty cheap (especially when security support is likely to match even extend currently sold XP licences...).

    Just my 2 cents.
  • mino - Tuesday, September 11, 2007 - link

    Win2000 Server, of course.

    Also, as a sidefect of standard win200 kernel it usually does not have problems with TV tuners...
  • tynopik - Wednesday, September 5, 2007 - link

    > Anyhow, I have a hard time embracing *any* OS that is supposed to be a server product and does not implement software RAID period

    1. it's a HOME server, not a corporate server
    2. it is better than RAID (at least for it's intended audience)

    disks of any size can be added or removed at any time, yet files are still physically duplicated on different disks, that is very flexible and powerful

    i love this feature so much i wish they would include it in regular windows
  • leexgx - Tuesday, September 4, 2007 - link

    nothing stopping you seeing it on the network still

Log in

Don't have an account? Sign up now