Review of Windows Home Server
Posted by sajuuk in Technobabble, tags: Windows Home ServerSo I finally got tired of having both my backup server and network share server down and decided to do something about it. Unfortunately, rebuilding both of them is not cost-effective at the time since completely rebuilding the Solaris Raid-Z server I used for backups and the CentOS 5 server I used for network shares would involve sizable expenditure of both money and time (which as we all know equals money). So I ended up looking around for something a little more budgetable and ended up finding the Acer Aspire Easystore H340, which Newegg.com sells for $379.00. The H340 runs Windows Home Server, which I used several times setting up home media networks for clients while I was in college. It’s essentially a stripped down version of Windows Server 2003, without all the fun that is configuring a Server 2003 installation from scratch (which I’ve done more times than I want to think about). Microsoft released it a few years back in the hope they could get people to start using central locations in their homes for backing up and storing media to play on their various computers and Xbox 360s. Of course, Linux did this ages ago and I’d been using Linux and Solaris servers to do backups and share media until their hard drives crapped out on me over the past year.
(Rundown and more details after the break)
The Rundown…
Overall, I give Windows Home Server a solid 9 out of 10. Comparable Linux distros get 9/10 as well. It should be noted that I have NEVER given an OS a perfect 10 and probably never will, there is always room for improvement.
Windows Home Server loses points for:
- Being the spawn of an evil, power-hungry, money-grabbing, corporate asshole system. Yeah, its a good product, but I just don’t like Microsoft’s business strategy and ethics (or lack thereof). Yes, this is the reason that any Windows OS loses points for in my book.
- Not having any form of notification that the initial automated setup/update process might take over an hour. This scares people who have never done something like this before. Heck, its only one line of text in the quickstart guide or even on the screen.
- Minor issue with exiting from a Remote Desktop session into the server. Sometimes this causes the WHS to think that your antivirus on the server has stopped running and immediately throws your network into Critical Health.
- Backup could use a little work. It would be nice to configure seperate backup times for seperate computers instead of a single backup time for all computers. Case in point, it would be nice to have CASTER3 (my gaming rig), backup while I am at work during the day, and have FATE (XP Netbook) backup at night.
Windows Home Server GAINS points for:
- Pre-installed on most new home servers. Saves time and makes it easier for newbies.
- Easy installation on custom installations. I didn’t have to do this for my own home server, but the times I have done it in the past its gone very smoothly.
- Ease of setting up remote (read — Internet, not LAN) access to the server. Microsoft did a very smart thing by providing this for free along with Windows Home Server via HomeServer.net. While getting the router (and possibly modem) configured correctly can be a bit of a challenge for some (including myself — the first time I installed WHS for someone they had a standard router, which fed into their vonage router, which then fed into their cable modem router, and all 3 needed to be configured correctly and getting into the vonage router was a massive pain), it is definetely worth it. Unfortunately, you can only have one HomeServer.net ID registered per Windows Live Account (and I made the mistake of using my Live Account for someone else’s server), this can be gotten around via use of DynDns.com and a correctly configured router.
- Expandability via addins. The core install of windows home server can’t do much aside from backup drives and locally share out media. There are addins to enhance its media sharing abilities, interface with home automation, provide enhanced monitoring of the server and drive usage details, the list goes on. The P80 addon adds a great way to remotely monitor your home computers (windows machines at least) and network health and status remotely. The WebGuide plugin also is far superior to the built-in media sharing over the internet as it allows for streaming of music and videos instead of having to download them. There’s even an addon for remotely managing your Windows Home Server from your iPhone or iPod Touch (haven’t used it though, you’ve gotta spend money for the iPhone OS app). A good source for addins is http://www.whsplus.com/.
The Review…
The Acer Easystore proved to be far more cost effective than comparable HP Home Servers, both in the short run and the long run. In the short run, there is the obvious fact that it comes with a 1 terabyte hard drive preinstalled. So basically you are paying around $280 for the hardware and the Windows Home Server license, which is a pretty good deal. Now, in the long run the Easystore saves money over the HP servers due to its low power usage. With the exception of the HP MediaSmart Server LX195 model, all of HP’s Home Servers run on either a Celeron or a basic new-model Pentium. The Acer and the Lx195 both run on the Intel Atom processor, which was designed for netbooks but is seeing adoption in some desktops and servers due to its extremely low power consumption, with the Acer drawing 200 watts of power at most. For comparison, my gaming rig (detailed out in my previous post, Se7en Days of Windows Se7en) draws 650 watts at peak consumption, and thats actually rather low for a modern gaming rig. The other advantage that the Acer has over the LX195 is the hard drive. The Acer has the 1 terabyte drive mentioned earlier, whereas the HP has only a 640 gigabyte drive. Considering the two are the same cost on Newegg, the choice is clear.
The Easystore comes with Windows Home Server (referred to from here on as WHS) preinstalled, as do all the HP models, so all you have to do is plug the server into your network and power it up. Of course, the servers are all what we in the industry call ‘headless.’ That is, they have no graphics cards installed on them. You either have to use remote connections in, which is how WHS was designed to be used, or use a USB graphics connection. All the times I had configured WHS before were repurposings of older computers so I actually had graphics on the machine I was working with, so this was a change for me. The server comes with a CD that has the WHS Connector Software on it, and you install this on a computer and use it to configure your new server.
Configuration itself does not take long, but the automated server setup that takes place BEFORE you can configure the server can take a while because it automatically installs updates on the server. Once that is done, you go through a wizard that sets things such as the administrator password for the server, the server name (I called mine NANOHA, in memory of my currently dead CentOS 5 file server). At that point, your server is up and running.
The next steps consist of actually setting up your server and computers to do what you actually want them to do. The first thing I did was add a second hard drive to server. One of the nice things about the H340 is how easy it is to install a new hard drive. You flip open the front of the case, slide out one of the hot-swap bays, install the drive in the tray (no screws needed!), slide it back in, and latch it shut. Then you go into the Windows Home Server control panel (via the software you installed to configure the machine) and use the Server Storage panel to add the new drive. WHS starts using it right away, and seems to prefer added drives over the one that has the operating system on it for storage.
Configuring your computer(s) to backup to the server is just as easy. In the WHS Control Panel, there is a section called Computers & Backup. Here you can see all computers on your network that have the WHS Connector installed. Right clicking one of them brings up a short menu that has the option of “Configure Backup.” The console will then scan the computer and give you a list of all the drives that can be backed up. You choose the drives you want backed up, and then if you want any certain things to be excluded from the backup (like temporary folders) and thats it. In the options panel for the server, you can choose when the backups are run and how long they are stored for. Restoring from a backup is something I haven’t had to do yet, but whats nice about the backups is that you can access specific files inside the drive backup (which I have done already) by choosing View Backup from the same menu that had Configure Backup, and then you choose the backup you want to open. From there, it acts just like browsing any other storage device.
The only major gripe I really have about Windows Home Server is not so much a gripe about it, its more of a gripe about how the Xbox 360 handles videos. The codecs included on the 360 for playing video amount to approximately nothing. Its something like AVI, MPG4, and WMV. No MKV support, no DivX support, and of course not XviD support. The way around this is streaming, which works fine for videos that either have the subtitles encoded into the video stream, have no subtitles, or have external subtitles. Translation: Most fansubbed anime isn’t going to work here. Not to mention there is barely any support for streaming from WHS to an Xbox, and the Atom processor immediately invalidates live transcoding as it would utterly kill the server’s performance. So, it looks like I’m stuck watching anime on my computer for the time being until I can figure out how to get MKV streaming to the 360 working properly or find some other solution.
If you have any questions about Windows Home Server, leave a comment and I’ll try to answer as best I can.


Entries (RSS)
[…] post by Major Arcana […]
[…] The guys give Home Server a solid 9 out of 10 and point out the products good points as well as its bad ones too, which you can read about here. […]
I don’t understand why you didn’t just spend the $300 on new HDDs, then slap them into one of the “dead” machines that you’ve got lying around. I’d much rather administrate a Solaris (or FreeBSD, now that ZFS support is production-ready) machine instead of dealing with Windows hassles.
Getting the old storage server back up and running would have required probably $300 in drives for a complete mirrored system like I previously had, not to mention at least $50 repairing and replacing the old coolant system, which entails at the very least a new coolant pump, tubes, and coolant. In the short term it would have been cheaper, but in the long term the old servers draw far more power than the WHS box does right now. I will eventually be repairing them for NAS useage in the future, but that probably wont happen until the spring when I don’t have to worry about combining the cost of keeping them up with the cost of keeping the electric baseboard heat on. At that point, the WHS will most likely get used as a gateway for remote access of my media and streaming the media to the Xbox, assuming I can ever get that working for subtitled videos.
As for the hassle of managing Windows, I have extensive experience with Server 2003 and 2008 (as well as Solaris and Linux servers), and when combined with the fact that managing WHS has been dumbed down the point where a trained monkey probably could do it, its no hassle at all. At most it requires maybe 5 minutes of management per day, mostly making sure that that the backup and storage balancing processes actually ran correctly. Beyond that, the only real hassle I’ve run into is the streaming problem, and I have found a solution to that, but the as I mentioned in the article, transcoding HD video won’t work well on an Atom processor.