***Note: Before deciding to purchase or build your own Windows Home Server machine, make sure you read this article on the serious data corruption issue that Microsoft is currently working to fix.  I believe they will have it fixed very soon (they say June 2008), and I have no reason to doubt it can be fixed, but I feel I should put this warning out there for anyone planning to purchase.  I guess I am plunging in because I am a glutton for punishment ***

Be sure to visit Part 1, Part 3 and Part 4 of this series as well.

In Part 1 of my series about Setting up my Windows Home Server, we looked at the un-boxing of the retail Velocity Home Server machine I ordered.  In this segment, I would like to cover installation of the Windows console …

After setting up the box itself, I needed to connect it to the network and plug it in.  Because I knew I was going to add hard drives, I decided not to tuck it away on top of the home Armoire just yet.  I should also mention that I have chosen the CyberPower 850AVR UPS system to ensure I don't lose data with any power surges (I honestly don't care if I lose the music or the DVD catalogue, but I have every picture we took of my kids during the last four years as well as family video on there, and this would mean certain heartbreak - and divorce - if I lose them.  More about my backup plans in a later part).  With the WHS and the TV plugged in, it tells me I get around 18 minutes of up time on battery power should we lose power.  And when I connect it to the WHS with a USB cable, WHS add-ins like GridJunction will allow the unit to do a safe shutdown if necessary.  BTW I've applied to be a beta tester for GridJunction.  We'll see.

My wife would like me to mention at this time that she would NEVER allow a rat's nest of cables like the ones in back of this armoire to be seen in public.  However, in the interest of knowledge sharing, she is allowing it … for now.  On a side note, I made sure I had 3 separate electrical circuits coming to the wall behind this Armoire to so I wouldn't blow a fuse with all of the components.  On the top of the armoire you'll see the D-Link Xtreme "N" wireless router that I am using.  Both the WHS and my "main" media center machine are connected to this via hard wire (Cat 6).  So the data transfer speeds should be blinding … or at least that's the plan.

So on with the Connector/Console:

The Microsoft Connector software keeps all of your computers communicating with the Windows Home Server.  It allows WHS to monitor the health of your network ("health" is measured by things like whether or not all computers with Connector installed are running anti-virus and are currently virus free, that each computer with the connector software has been backed up successfully according to schedule and that your WHS has enough space to store your files (especially where duplication is concerned)). 

Note: I think it is important to point out that if you don't have a computer running this Connector software (i.e. work laptop that you bring home nightly), you may not be getting the "full" health picture, so always follow best practices in terms of network security and don't let WHS become a crutch.

Another component of the connector software is called the "Console".  This is the interface that allows you to administer your Windows Home Server with such tasks as adding user accounts, creating shares and determining who has remote access to the network through WHS, among other things.  Every time you install the Connector software on one of your home's computers, the console gets installed with it.  However, MSFT does not intend for everyone on your network to have access to this console.  Once you create a password to use the Console, you should protect it with your life.  You don't want to let little Suzy (or Timmy) give remote access to their friend so he can help fix her desktop.  Obscurity/complexity is no longer an element of protection.  The console makes things very intuitive, and you don't need an MCSE to configure access to your network anymore (sort of the point, I suppose).

OK - so to install the connector software is very easy.  Simply put the CD in the disk drive on the computer you want to connect.  If this is the first time to install this on your network, you will have several setup steps to get through.  Follow the install wizard.  You will be prompted several times for input.  This is where it is a good idea to have already thought out your network so you don't have to make certain decisions on the fly.  One of the first prompts asks you to enter your product key.

One tip here:  you don't have to enter your product key to finish the installation, but you will have to go into "settings" and enter it there in order to activate your OS.  If you don't, things stop working after a certain amount of time (I believe 30 days).  The funny thing for me was, even after entering the key on this screen, I later found that the OS was still considered "un-activated" by WHS in the settings dialogue box.  After I entered it again it showed that it had been activated.  Now I may have simply typed it incorrectly the first time, but I would suggest you check for yourself when you are done. 

You will also be asked to create a name for your server and a password.  MAKE SURE YOU WRITE THE PASSWORD DOWN.  This is your "administrative" password and if you lose it you will find life has become very difficult.

It's important to come up with a unique name as well.  As you add computers and devices to your network (and even additional servers?), you want to be sure you know which is which.

Another question you will be asked is whether or not you want to have your Home Server automatically protected.  This refers to the "Automatic Updates" that you most likely already have running on your other XP and Vista computers.  My recommendation is to turn this ON.  Especially right now, when we are waiting for the fix on data corruption.  And with the technology being as new as it is, you want to be sure you are getting updates as soon as they come out.

Once you have completed the setup information, the console will reboot the WHS remotely and then ask you for the password you entered in the steps above to re-enter the console.

Interestingly enough I was prompted by Automatic Updates to download and install Explorer 7 after I logged back into my console for the first time … I wonder why that wouldn't have already been loaded?

Once you are completely into the console, you should see a screen like this, along with the green icon in the icon bar at the bottom of your screen.  You can right click on that icon at any time to get into the console, or to perform actions (such as backup) on the local computer.

You are now ready to begin administering your new Windows Home Server.  Of course, you'll want to install the connector software on each of the additional machines in your network that you would like to monitor (and that should be all of them, if possible).

Now - I'm sure, like me, you took a look at that initial set of hard disks and said "there's no way that'll be enough!"  So you'll want to add a couple more.  Well I will show you how I did it in Part 3 - Load it up!.

Happy networking!