Rosher Consulting

Software Consulting and Development Services

My ‘Franken-build’ Windows Home Server

I’ve just recently put together a Windows Home Server machine to backup all of my photos, music and so on as well as all of the machines around my house. It’s custom built rather than off the shelf, hence why it’s called a ‘Franken-build’, which is a term I first heard on the Home Server Show podcast to describe a custom build.

Why Windows Home Server?

If you see my post here you’ll remember that I purchased a NAS box about 18 months ago and have been using that to backup most of my content. Unfortunately I never really used it to its full potential as I had it waking up for an hour a day, doing the backup and then going back to sleep. I didn’t use any of the extra features such as the iTunes server or BitTorrent client and it was also lacking in a couple of areas, performance being the main one but also minor things such as not supporting Wake-On-Lan.

After upgrading my TV/File server again I had even more spare parts lying around so in the course of deciding what to do with all these bits I thought why not give Windows Home Server a try? There’s a free 120-day trial edition available from the Microsoft website, which is more than enough time to decide if you like it. It only took me a week to decide to replace my NAS.


Here’s the initial list of components I had to work with when I first setup with the trial edition:

  • Athlon XP 2000
  • MSI KM4M-V Motherboard
  • 1gig ram
  • Seagate 80gig IDE
  • Seagate 160gig SATA
  • Old 350w power supply
  • Random spare DVD drive.
  • Intel 1gig NIC

I also have a Sempron 3000 CPU lying around which I would have rather used for this build as it’s faster and more efficient, but unfortunately it’s not compatible with the above motherboard and the motherboard that I do have for it doesn’t support S3 standby whereas I know the MSI board works really well with S3 because it came from my old Media Center prior to the Quad Core upgrade.

I didn’t have a case to put any of the components in so I just laid everything out on the table and connected it up, using a couple of wires to bridge the power connector so I could start the machine up. Windows Home Server was then installed, which took about an hour and I then proceeded to setup and install various add-ins so that I could test to see if it would suit my needs, which mainly involved the ability to wake up and go back to sleep at a pre-determined time.

Once I was happy I then decided to order a licensed copy of Home Server, along with a case to house it in and a new more efficient power supply. I ended up ordering the following:

  • Asus TA-D31 case
  • Antec Earthwatts 380w PSU

The Build Proper

As per usual everything turned up nice and quick from eBuyer, so I shut down the Thecus NAS for the final time and removed the drives in preparation for the build. Here’s some pictures of everything prior to starting:

The parts arrive IMG_5044 IMG_5048


I put everything together in the new case, started her up and then proceeded to install the full licensed copy of Windows Home Server. Unfortunately with Windows Home Server you can’t upgrade the trial edition to a full licensed copy, you have to re-install from scratch, which I wish I had known about before spending the time to setup the trial version.

After finishing the install I noticed that there seemed to be some issues with the OS hard drive, every now and then things would appear to stutter and lock up so I decided I’d just use a different hard drive and re-install again. Unluckily for me the second hard drive I chose had exactly the same problem, so this time I borrowed a drive from the kitchen PC and used that instead, this time after over 3 hours spent installing WHS it was third time lucky and everything was working ok!

IMG_5060 IMG_5061 IMG_5064

Once everything was up and running, I could then proceed to copy all of my photos, videos and music over as well as installing the WHS connector on all of my PC’s so that they are regularly backed up, which is a nice added peace of mind considering that they weren’t backed up at all before.

Even with the low spec of the WHS machine I’ve been getting decent performance copying files to and from it, certainly much better than I ever achieved with the NAS. Write speeds have been around 40MB/s across the network and read speeds have been between 50-60MB/s.

The WHS has now been running for a couple of months and has performed flawlessly during that time, I’ve even purchased some new 1.5TB hard drives to up the storage to 3.5TB, which has meant that I’ve now got the space to back up my DVD collection as well as everything else. Overall I’m really pleased with the machine and would heartily recommend a Windows Home Server to everyone that has multiple computers in their house!

Creating drive image backups with DriveImage XML on Windows 7

I’ve been installing the release candidate of Windows 7 on most of my machines of late and since I didn’t want to dual boot the systems or lose the existing install of Windows XP I decided I’d try out some drive imaging software to backup the existing data on the drives.

I came across DriveImage XMLl which is a great little app for backing up your drives and would you believe it’s also free for personal use, can’t argue with that. Over the past few weeks this app has really saved me countless hours of re-installs as I troubleshooted problems with Win7 and then fresh installs of WinXP on the new server I was building. However I initially had some problems creating a successful backup on Win7 so I thought it would be useful if I document it for others and just generally gave an overview of DriveImage XML.

DriveImage XML uses either volume locking or volume shadow services to create a hot image of your drive while Windows is running, by default it tries to use volume locking first and if that doesn’t work it will try volume shadow services. In WinXP this all works fine, but in Windows 7 it firstly fails to lock the drive and the volume shadow service isn’t running so it can’t use that either. It will warn you and you can attempt to carry on, which is what I initially did and I managed to create a successful backup, but there’s a better way!

First we need to make sure that the ‘Volume Shadow Copy’ service is running, so open up the services control panel applet (start –> services) and scroll down to find the ‘Volume Shadow Copy’ service. As you can see from the screenshot it’s set to manual, so let’s start it up.

CropperCapture[1]I’m assuming that you’ve already downloaded and installed DriveImage XML, so either find it in the start menu or find the executable in explorer, either way we need to click on the app and choose ‘Run as administrator’ from the popup menu, this makes sure that it will be able to access all of our files.

CropperCapture[3]When DriveImage XMLl starts you’ll be presented with the following screen:

CropperCapture[2]Since we want to perform a backup, click the backup option.

DriveImage XML will then show you the hard drives installed in your system, select the OS drive and click next.

CropperCapture[4]Now choose where you want to create the backup image, ideally this should be on another drive and also you’ll need to make sure that there’s enough free space, then give the image a name, as you can see from the following screenshot I’ve named the backup Win7.

For the ‘Hot Imaging Strategy’ make sure you choose ‘Try Volume Shadow Services first’, I also uncheck the ‘Split large files’ option so that I end up with one large backup file rather than lots of small ones. Click next to continue.

CropperCapture[5]DriveImage XML will now start doing it’s thing, depending on how much data you have on your drive it shouldn’t take that long to create the backup, mine only took 5 minutes for an 8gig backup.



When it’s finished you should find you have a large ‘dat’ file and an ‘xml’ file:

CropperCapture[11]And that’s all there is to it, of course at some point you’re going to need to check that your backups actually work, for this I’d suggest using a spare drive if you have one and restoring the image there rather than testing it on your main system drive.

One thing I came across when doing the restore’s is that DriveImage XML expects you to restore to an equivalent or larger size disk to the one you created the backup from, which when the backup is only 8gig seems a bit strange. Anyway, I found a way around the problem by editing the XML file to say that the logical drive was actually smaller than it was, just edit the total space value to be equivalent to or smaller than the drive you are restoring to and also remember to adjust the free space value, after that all should be ok and I was able to restore an image from a 160gig drive to an 80gig drive without any problems at all.


Having now used a drive image backup application I can’t believe I’ve lasted so long without it and especially just how much time it’s saved me. It means you’re free to install drivers, apps and anything else without having to worry about whether it will screw up your system because if it does you just revert to the last image you took. Some people may be thinking isn’t that what System Restore does, but anyone who’s ever used system restore will tell you that it never seems to fully clean everything out and your system isn’t quite as it was before.

On a final note, if you want to run DriveImage XML from a BartPE bootdisc, there’s a Portable Edition download on the website and this is how I’ve been using it over the last couple of weeks.