I thought it was about time I started to get some hands-on experience of Windows Home Server (WHS), especially now that the first service pack (sorry, ‘Power Pack’) is available for the platform.
Of course, I could have followed the easy path and got hold of an HP Mediasmart Server, or one of several other ready-made products now available. But that would have been too easy, and wouldn’t have provided a full insight into the software and how it ticks. So, instead, I opted for the do-it-yourself route and built a server of my own, which proved an interesting experience.
Soft and hard issues
The first hurdle to overcome was getting hold of the software, which comes on
three discs a server installation DVD plus CDs for client setup and recovery
of crashed PCs. However, unlike other Microsoft products, you can’t get these
via MSDN or Technet, which is where most developers, enthusiasts and journalists
like me would start.
For most people, that means spending money to get the software. A 120-day trial version of WHS is available for the cost of postage (£4.58) but eventually it has to be activated, otherwise it stops working. Ignoring illegal activation hacks and other workarounds, a full 10-user licence costs around £90 to £100, depending on where you buy it.
Fortunately, I’m a member of Microsoft Connect and take part in a number of product evaluation programs, including Home Server, so I got an evaluation copy that way, which just left me with the hardware to sort out.
Now, the temptation with a product like Home Server is to recycle an old PC rather than buy a new one. That’s a temptation I admit I succumbed to, starting first with an ancient Pentium 4 machine that readily booted the server DVD, but proved not to have enough hard disk space to go any further; at least 65GB to 70GB is required (note to self must read manuals first) and my PC only had a 40GB ATA disk. Still, undaunted, I fitted a Sata Raid adapter left over from a r eview, plus a new 120GB hard disk and rebooted from the DVD.
Unfortunately, Home Server (effectively an implementation of Windows Server 2003 with Service Pack 2) didn’t have a suitable driver for the new adapter. As it uses its own Drive Extender technology (more on this shortly), it turns out that hardware Raid is frowned upon. So, I eventually gave up on that PC and tried another.
All Software Applications Tags: Networks
