For years, we’ve relied upon servers, both Linux and Windows, in our businesses to back up our data, store shared documents and E-mail as well as provide 24/7 access to these materials from wherever we might be. As time has progressed, however, the same people who rely on dedicated servers at work are coming home at the end of the day…and they’re in need of the same kind of reliability and accessibility with their computers at home. That need is growing exponentially because more and more things are being created and stored on the computer; be it homework, finances, hobbies, E-mail or entertainment.
Not only are these individuals, like myself, in need of a dedicated machine to keep their data backed up but to keep that data accessible whilst at home or on the road. Microsoft’s Windows Home Server fulfills these scenarios and more. Based off of Windows Server 2003 SP2, WHS (due in the latter half of 2007) provides an easy, intuitive setup giving your “home admin” a painless way to accomplish all of this.
The Setup
During the initial setup, WHS provides the user with a customized domain: yourname.livenode.com. (As of yet, no other domain options are available…you’re stuck with livenode.com.) You’ll also be given access to a tool that supposedly seeks out your router and automatically enables it for remote access…this didn’t work for us and we had to configure it ourselves. ‘Twas no problem as we got directions from a post on the WHS forum on which exact ports to configure. We’ll get into Remote Access/Web-based administration here in a bit but, for now, let’s get back to the setup of your home server. After you’ve gotten your domain, you’ll be configuring the Windows Home Server Console. This console is where you’ll be overseeing all aspects of your home network from here on out including: computers, users, shared storage and backups.
Managing Your Computers
Once you’ve got the administrative console configured on your new home server, you’ll want to add the other computers in your home to your network. This is accomplished by installing the Windows Home Server PC Console (provided with the WHS DVD) on each of the computers. Not only does the PC console automatically add your computer to the newly-configured network, it also automatically ensures the files on this PC will be backed up, on a pre-determined schedule, in the event of a disaster. (The schedule can be modified in the application settings…and by “disaster,” we mean your 17-year-old teenager visiting spyware-ridden music lyric or gaming sites.) The PCs you just configured will begin showing up on the “Computers & Backup” tab of the WHS console.
Managing Your Users
Now that the computers themselves are backed up, the next step is to add the users that are on each of your PCs to the network. From within the User Accounts tab in the console, you add the names, usernames, and passwords currently being used on each of the PCs. As a side note, some of you may not be using passwords with the account you initially created when you set up Windows XP. However, passwords are a requirement in order to add these users to the WHS network. In this case, there’s an option in Windows XP to allow automatic logon with a password.
Is this process even necessary? Well, if you want to be able to grant users 1) remote access to their computers and/or files or 2) configure which shared folders on the network to which they’ll have access then, yes, it is necessary…and highly recommended.
Managing Shared Folders and Server Storage
Another area of convenience that Windows Home Server offers is the Shared Folders feature. By default, shared folders for music, photos, videos and more are created for you. When you ran that console setup on each of your computers, not only was a shortcut to these Shared Folders created on the desktop, but a new shared folder for that particular user’s documents was created as well. If your kids or your spouse clicks on that shortcut, they will only see the files or folders they have permissions to see…very similar to a setup you might have at work. These permissions are configurable at the console in either the Users or Shared Folders areas. Overall, the setup of Shared Folders is very simple and the shared folders that are created by default or that you created will also be accessible via the Web at your livenode.com address. Again, we’ll get into the Web-based access of your home server in just a bit.
Along with the added convenience of instantly granting your family access to common, easily accessible resources, Shared Folders and Server Storage also grants you the option of Folder Duplication. You might think of this as a simplified, GUI-based mirrored RAID array. (If you have no idea what I’m talking about, read a paragraph or two describing this process.) Essentially, WHS makes use of additional server hard drives or attached storage to make duplicate copies of your folder. If, for some reason, any “duplicated” files become corrupted, WHS can restore from a duplicate version on a separate hard drive.
That said, if your corrupted Shared Folders are on the same drive as your Windows Home Server operating system, there’s a chance that the entire hard drive (including the WHS operating system) might be hosed. In that case, you wouldn’t be able to access the Folder Duplication feature to restore from another drive. Granted, WHS automatically breaks up the default drive in your server into two partitions, one for the OS and one for storage, but you might still want to invest in a separate hard drive to begin with in the event of any type of physical damage/wear to the drive. This way, you may have to run the Windows Home Server setup again but at least your data will remain safe.
It is within the “Server Storage” area that you can add new hard drives to your Windows Home Server and/or view the health of your existing drive(s).
Windows Home Server Settings
As you might expect, the “Settings” area is where you’ll be configuring more of the technical aspects of the server itself. General: configure server time and region, automatic updates, error reporting and Microsoft’s “Customer Experience Improvement” program. Backup: tell WHS when to backup the folders and/or computers you’ve specified and how long to keep those backups. Passwords: you would change your password here or even configure the minimum requirement for passwords (weak, strong, etc.) on your network. Media Sharing: here you can enable music or movie sharing for any Windows Media receiver you might have in your home. Remote Access: as you might guess, this is where you’d configure remote access to folders and/or computers on your network. The self-tests offered here are especially useful in making sure that you’ve got everything configured properly. The router configuration utility can also be found here but, as previously mentioned, doesn’t appear to be quite ready for prime-time. Add-Ins: here is where you would install any available WHS add-ins. Much like add-ins for Internet Explorer (or extensions for Mozilla Firefox,) WHS add-ins provide advanced functionality that wasn’t necessarily included in the core operating system. In the screenshots we’ve included in this article, you’ll see one add-in already in use: “Wake-On Lan.” This particular enables us to remotely shut down a computer in our network, get the MAC address of that computer, and even wake one that’s already been shut down, all with the click of a button. Resources: here you’ll find information about the version of the OS you’re using and the hardware powering the machine (i.e., processor speed, amount of RAM). Basically, this is pretty much the same information you’d find if you hit Ctrl+Break on your existing Windows machine.
Remote Access
Now we get to, what we feel anyway, the feature that will be most the beloved of all: Remote Access. (We gave it away with the header above, didn’t we?) Currently, here at Fans of Tech, we’ve tinkered with enough settings on our existing Windows Server and router to enable us to remotely access our files and even our computers on-the-go. However, it’s certainly not a fun, or even easy, process. Windows Home Server, on the other hand, makes it painless. As we mentioned in the very beginning of the article, setup takes you through getting your own customizable URL to use with Remote Access: yourchoice.livenode.com. Afterwards, WHS can even automatically configure the router in your home to enable access from the Web.
While it didn’t work for us this time, we presume that, by the time the final release is out later this year, this feature will be more dependable. (Just look at the progress made from Vista RC1 to RC2…huge, in our humble opinion.) After our router was configured, we were able to access our test network with incredible ease. By accessing our LiveNode domain, we arrived at the following:
Upon logging in, we now have access to the computers and shared folders on our network. Permissions are once again applied here so you can only view the computers/folders you’ve been granted access to.
Entering the Computers section of Windows Home Server Remote Access gives you an overview of the computers in your network. If you have the appropriate permissions, you can remote desktop into any of the computers and even your home server.
Before I forget, Remote Desktop connections to computers are not supported in Firefox. [Post your gripes in the comments section at the end of this article.] I might also add that connections are dependant upon the version of Windows that the computer is running. As you might already know, Windows XP Home/Vista Home/Vista Home Premium does NOT allow incoming connections via Remote Desktop, as indicated in the screenshot below. For that particular functionality, you’ll need to upgrade to Windows XP Pro or Windows Vista Business/Ultimate. Honestly, these are two things we feel Microsoft should work around. Perhaps an extension or plug-in for Firefox and WHS-specific access for remote desktop might be in order.
After clicking on the computer name, a customizable (in terms of size) remote desktop connection is launched within the browser window displaying your computer exactly as you would see it if you were sitting right in front of it. What happens, though, if you turned your computer off before you left the house? Well, if you have the proper access, you can log in to the server itself by clicking on “Connect to your Home Server” and, provided your computer is WOL-compatible, you can use the “Wake-on-LAN” add-in of Windows Home Server to wake your computer. Oh, how we do love technology.
This is pure speculation but I presume that Microsoft might embed the functionality of the Wake-On-LAN add-in to the WHS console before the final version ships.
Last, but not least, we shift our focus to the Shared Folders area of WHS Remote Access:
Here you’ll be able to access the documents on the network for which you have privileges. Not only can you see the documents and download them, you can also upload using the built-in file upload tool.
Here’s one helpful hint: you can change the location of your My Documents (Windows XP) or Personal folder (Windows Vista) to be mapped to a folder that has been created on the server. This way, your personal documents will be accessible no matter where you are. To that, my friends, I say “booya!“
Instructions for Windows XP users: http://support.microsoft.com/kb/310147
Instructions for Windows Vista users: http://www.maximumpcguides.com/relocate-a-personal-data-folder/
InD Summary
Whether you’ve heard about them or not, Microsoft has big plans for Windows Home Server and rightly so. They’ve already not only partnered with HP but have already announced the first product to use it: the HP MediaSmart Server powered by AMD, currently due this fall. (The fine folks at Gizmodo recently had some interesting news regarding what could be a more feature-rich incarnation of WHS than what we’ve been describing here.) For those of you curious about pricing, rumor has it that it should fall around that of your average PC today: between $500-$600.
As we said at the beginning of this article, a dedicated machine at home for backups, storage and data accessibility is going to be a necessary item in a very short while. There’s no doubt that any geek worth his/her own salt can download the latest version of the most popular flavor of Linux and get their own dedicated home server up-and-running in a few hours…and probably on a machine they had sitting in their closet. If you were to throw that task up to the average home tech user, however, it wouldn’t be worth the time or effort…nor would they have a spare machine lying around with which to “tinker.” Microsoft has done a great job in making sure that this task is easily accomplished and with little tinkering.
Hopefully we’ve answered a few questions for you about what Windows Home Server has to offer to the average household with tech. Granted, the majority of you reading this won’t necessarily need Windows Home Server but it would definitely be nice to have something simple in our lives for once…and to be able to recommend something simple to friends and family. Yet another payoff for our average reader.
Links:
Windows Home Server: Overview
Windows Home Server: List of Features
The Official Windows Home Server Blog
Windows Home Server Forums
Technical Notes:
For this InD article, we were demonstrating the Windows Home Server Community Technical Preview, released on April 18th, 2007, on a Dell Optiplex GX240 with a Pentium 4 processor running on 512MB of RAM.
