I have been made a beta tester for the new Microsoft Windows Home Server system. I though I would give all of you DCoT readers a bit of a tour of the new system via screenshots.
Installation
Installation of Windows Home Server is basically the same as any other Windows operating system product. Boot from the DVD and follow the prompts. No real rocket science here (unless you want to run it using VMware).
Since I was not able to get the system installed in VMware, I created the installation in Microsoft Virtual PC.
A few things of note about the installation. First, it is quite obvious that this product is based of the Windows 2003 Server since there are still a lot of logos for that product in the installer.
Second, it looks like they are trying to incorporate some of the ease of installation that is a part of the desktop products since this is designed for the average home user. Yet, one things that will probably really confuse the average user is the designation of Disk0 (see Hard Drive Selection screenshot below). Unless you have some technical experience, you will not be familiar with anything other than drive letters. Could be confusing.
Third, an empty default administrator password? I sure hope they change that in the final installation!
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
First Login
The first time that I logged into the system, there were a couple of surprises.
The first surprise was that there was on option to not change the default blank password! You might as well put a sign on this thing that says, “Hack me!”
The second thing that surprised me was the warning about how the tools could break the system. I thought that this was a given for any operating system right back to DOS (format C: /Q anyone?). I’m assuming that this is to scare people away from using the system as an actual computer and getting them to buy an extra license.
 |
 |
 |
 |
 |
The Home Server Console
The Windows Home Server is completely managed by Home Server Console. This is essentially how you add users, set up systems, configure the server, etc.
The console is a bit of a mystery application to me. When I was getting screenshots of it, there were some hidden sections that the program was trying to grab and yet some of the other sections that I would have expected it to grab were not “grabbable”. I am definitely going to be giving it a closer look. My assumption is that it works like a web browser but that is only a guess.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Client Installation
The other part of the Windows Home Server is the client. This is software that needs to be run on every system so that it can connect to the Home Server.
In general, a pretty standard Windows application installation. The one thing that was a bit confusing was when it asked for the Home Server password. This is actually the Administrator password.
 |
 |
 |
 |
 |
 |
 |
Managing a System
There are a number of different things that you can do with the client software. In this set of screenshots, I connect in to the system, add a user, configure a backup and run that backup.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
To Do List
There are a number of things that I have yet to do with this system. Here are some that I am planning to work on in the future:
- Perform a recovery of individual files
- Perform a recovery of an entire system
- Analysis of the console application
First Impressions
Since I have not had a lot of time to work with the system, I do not feel it is fair to give it a complete review. But, I have developed a few opinions and ideas about this product.
First, I have to admit that I do like the product. I believe that there is a need for a product like this in the modern home. I do not thing that every home will have one of these devices as soon as it is released but I do think that there are a number of homes, especially homes with multiple computer systems, that could get a real benefit from this system.
If the backup and recovery features of this system work as they are supposed to, I think this could go a long way to keeping some home users’ sanity! This will probably what makes or breaks this product (along with price).
The ability to share files and folders is not really that big a deal. People do this now from shares just on their own computers. Not really all that earth shattering.
One thing that I did not notice was an ability to back up these shared folders on the server. I do know that there are all the same Windows backup tools available but if you are going to make it easier to back up the desktops, you had better make it easier to back up the server as well.
While this system is radically easier to set up than a regular Windows 2003 Server, it is still probably more difficult than the average user is able to tackle. This should immediately catch the attention of all you tech consultants out there. I think you could potentially have a really great all inclusive product here. Your product would include a Windows Home Server (hardware and software), installation of the server, and configuration of all the clients. For a nominal fee, you could also remotely monitor the server once a month for problems with the system.
Conclusion
I really think that this product has some good potential. But, there is definitely some work that still needs to be done and it is yet to be seen whether or not the system will be cost effective enough and simple enough for the average home user.
If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?
| Trackback link - http://www.dailycupoftech.com/windows-home-server-screenshot-tour/trackback/ |
|
March 13th, 2007 at 9:15 pm
How would this be set up? If it would be through soe kind of remote access software, like VNC, would the Server alow youto install extra software on it?
March 14th, 2007 at 10:20 am
Michael,
There are a number of ways that you could accomplish this. Tunnel VNC through SSH or LogMeIn.com com to mind immediately.
Tim
March 14th, 2007 at 12:01 pm
Hello-
If you don’t know blank Administrator password is the most secure thing since Windows by default rejects all SMB and remote connections to it. Only console logins are allowed.
May 2nd, 2007 at 11:18 am
How about an update: Thoughts on WHS after you’ve been running it for a while!
December 2nd, 2008 at 6:17 am
Beta Guy…
“blank Administrator password is the most secure thing” - False, wrong, stupid, caseless and.. on a more personal note go learn about security before giving people advise like that.
A blank administrator password is the most insecure measure possible. This does NOT stop remote connections as you will still be able to connect via tools just as PSExec.
The most secure way of protecting your Windows Home Server or indeed any Windows System is to Disable the Administrator account and use something someone wouldnt guess easily. This will mean that people can sit there all day long typing in the UID as Administrator but they’ll never get anywhere.
Good passwords are always a must, ie 3nclo$3d. is better than enclosed a router is always a good way of protecting your network from external threats as most modern routers have a very good firewall, anti virus is obviously a must as is anti spyware…
but blank admin passwords……….. no