Do I Want a Windows Home Server?
Ever since I first heard about Windows Home Server (WHS) I've been intrigued. After reading reviews like this one at Ars Technica I've decided that I need to try this server out. The review does a good job of describing what WHS is and is not. I'm going to document my thoughts and processes for putting a WHS server on my home network.
First, a description of the current setup. In the house I have 2 main desktops (1 for me, 1 for my wife), 3 laptops (1 for me, 2 are my wife's), and 2 servers (1 is basic file, web, print server and the other is essentially NAS for backups). What I want WHS to do is replace the 2 servers with 1 box. The main server provides these functions for me:
- Basic web sites. Mostly Picasa exports for photos.
- NT authentication protected Andromeda script for everywhere access to my music.
- Storage for my music collection.
- Runs SlimServer for the Squeezebox in the living room.
- File shares for Music, software, common documents, scratch area, etc.
- 2 connected printers that are shared for the workstations.
- Custom service to update my DNS entry when my IP address changes.
- Scheduled SyncBack SE job to copy files to the backup server
The backup server has a couple of jobs itself:
- Network shares so machines can copy files to it to back them up.
- Always has a user signed in and FolderShare up. This requires a little explanation. I use FolderShare to keep several directories sync'd between my laptop and desktop. The problem is that the 2 are seldom powered on at the same time. Enter the always on backup server to provide the link.
The question is: Will WHS fulfill all those services and add something compelling to make me change?
The answer: Yes, but probably with several unsupported "features". I'll elaborate in my next post.