Today came an announcement that represents a pretty big step in the identity space. Yahoo! announced they have rolled out beta support for OpenID v2.0 and that Yahoo! is now a provider of OpenIDs. In fact, anyone who has a Yahoo! account can quickly generate a Yahoo! or Flickr-branded OpenID to sign onto any web site that supports OpenID v2.0 for authentication. That's 248 million accounts at Yahoo! that can now potentially be leveraged across the Internet for sign-on.

OpenID is an important standard that came out of the open-source community, which will likely change the way we provide identifying information and gain access to secured web sites on the Internet. It allows its users to have a single identity that can be used across different sites on the Internet. It also allows users to have the proper level of control over how they identify themselves and who they want to trust with that process.

One significant key to success for OpenID as a standard is adoption by a set of trusted identity "providers" - or OpenID-issuing organizations that people are comfortable with when it comes to asserting their identity information. With Yahoo! a large number of regular, everyday people can use their existing accounts to perform OpenID logins on any site supporting the standard. In the future, the hope is that other consumer-trusted providers will see the value of brand recognition that goes along with being the OpenID provider for consumers. Yahoo has me as an OpenID client now, which means every time I log onto an OpenID-enabled site and use that ID, I am by default thinking on some level about Yahoo! -- Pretty smart. It's time for banks, other financial service providers, and similar industries to seriously start thinking this one through. It's coming, and now is the time to be on the bandwagon.

Where can you use your OpenID to log in? Lots of places. There's a list of web sites over at myopenid.com, a service provided by Portland company JanRain. The people at JanRain have created some great software and services around the OpenID standard that businesses can use to leverage OpenID, and that enable social networks around the standard. It's pretty cool stuff.

Here's some basic information about OpenID from the Yahoo! OpenID provider site:

What is OpenID?

In a nutshell, the OpenID technology makes life simpler by having only one username and password to remember.

Once you have enabled your Yahoo! account for OpenID access, you only need to remember your Yahoo! ID and password to use hundreds of websites... So bid farewell to password spreadsheets and stickies all over your desk!

When you are on a web site that supports OpenID login, simply look for a Yahoo! login button. Or if you see a text box with an OpenID icon, simply type in "yahoo.com". You will be sent to Yahoo! to verify your Yahoo! ID and password, and then you will be able to continue on.

You can find out even more at openid.net (the OpenID Foundation), and it's worth pointing out that you can also get an OpenID from a slew of other organizations - after all, it's all about making it your choice. The OpenID foundation keeps a list of providers on its wiki and at this link.

Via Jake at UtterlyBoring.com, the latest in the "Will it Blend?" series is here. Don't mess with Chuck Norris:

You'll find a bunch of humorous blender commercials at http://www.willitblend.com/. You can also buy the blenders there.

Here's another "what's my brain doing to me?" piece of weirdness for you to try...

 

Reads: “While sitting at your desk, lift your right foot off the floor and make clockwise circles. Now, while doing this draw the number “6″ in the air with your right hand. Your foot will change direction and there’s nothing you can do about it.”

Hmmm. If you keep trying can you eventually overcome the natural tendency to change directions? I can't seem to do that.

(via Fitz and Digg)

I'm going to go off on a bit of a (somewhat grumpy) lecture here in hopes that people will stop long enough to listen. A little Gestalt therapy, if you will. Ultimately I hope at least one person recognizes a need and acts on it.

If I had a dime for every time I have personally seen this one issue bite someone in the backside, I'd be a rich man. There are a zillion things that can go wrong on a mission-critical network, but of those things there are actually just a few that account for a substantial portion of the issues that typically bring critical services down.

So, if you run a network and have not addressed the one issue I will describe below, please take the time out of your day to start a plan to remediate the problem ASAP. Along the same lines, if you are not sure where you stand with regard to the issue, or if you have never checked but you feel confident because everything works today and always has so it can't possibly be an issue... Again, please just take the time to inspect your infrastructure and put a plan in place.

I should also say that if I had a dime for every time I've said exactly what you just read in the paragraph above, I'd be a rich man. I lost count long, long ago of the number of hours spent watching people try to avoid - in any way possible - checking the obvious and addressing it. Usually that's due to those egg-on-face concerns that go along with being they guy who missed something so simple and critical (albeit not too obvious) when it came time to learn the detailed intricacies of running a high-availability network.

Okay, enough with the harshness. Time for the issue at hand.

The number one network mistake I have seen people make on IP networks, over and over again, is using the default settings on their switches and servers that cause the network interfaces to auto-negotiate the speed and duplex settings.

Seriously, if your requirement is to provide high availability and your SLAs require your services be up, do not neglect the critical (but often skipped) process of manually configuring your NICs and switches to the proper setting. Just because the interface says it's running 100mbps and full-duplex doesn't mean it's working, and when your network takes a dive and you start losing packets you'll be sorry.

Along the same lines, never assume that one half of one percent of packet loss is no big deal. Seriously, if you are seeing retransmits on your network interfaces, something is likely wrong. Also, chances are that .5% loss is not being scattered evenly across your traffic. It may all be happening at once in bursts, and that hurts - a lot.

Again, if I had a dime for every time I (or someone working with me) recommended inspecting the interface settings, recommended changing them, and flagged interfaces where traffic analysis showed data transmission loss that was obviously causing network apps to fail... Well, let's just say it's amazing how hard it is to convince some people that their network is the cause of the issue.

Why am I being so blatantly blunt about this? Because I hope that the message will carry, that administrator egos will be set aside, and that people will understand that the real-world evidence based on years of actual experience, proven over and over again, bears out the fact that this will eventually happen to you if you have not already taken the steps to ensure it doesn't. Don't let that happen. Protect that ego now, rather than waiting for it to be damaged.

Finally, don't fall prey to the idea that just because you have high-grade HP, IBM and Dell Servers and Cisco switches that the money you (smartly) spent negates the need to set things up the right way, or that these vendors have everything figured out for you and set as defaults. Point of fact, this issue occurs just as often (if not even more so) with your expensive, data-center class hardware. In fact, Cisco switches have been somewhat famous for requiring intervention of the manual-configuration type. They even have a troubleshooting support article here that you can refer to for your configuration needs.

You have been advised. Now go do something about it. And forward this to every network administrator you know. The network (and ego) you save may be theirs. :)

I recently set up a Windows Live Workspace beta site, and while doing that I saw a program that I had not realized was available before, called SharedView. It's a program that is currently in beta (the release number as of this writing is beta 2), and it's a simple and effective app that lets you share your desktop or applications with someone else and lets the participants grant control of their computer desktop to others in the session. It's integrated into the Office Live Workspaces for collaboration purposes, but it's usable for a variety of purposes.

I didn't download the program immediately, but was intrigued by what Microsoft had put together. Then, as fate would have it, the next day my mom sent me a IM via my mobile device (she really is pretty tech-hip for a retiree, heh), telling me she had a little computer problem and needed some help. In the past we've tried to use remote desktop services and the help-request functions in the MSN/Live IM client, but firewalls always seem to get in the way and performance has tended to be lackluster. Anyhow, in the process of trying to solve the computer issue, it  often becomes too complicated to try to solve it via text messages, so in this case I hooked up my laptop, downloaded the SharedView client and set up a SharedView session with my LiveID account and pointed her to the download so she could join the session using my email address and a passcode.

Within a few short minutes she was online and in the SharedView session and I was able to see her desktop. I liked that I was able to point to things on her desktop and she could see what I was pointing at, without having to take control away (this feature is called Personal Mouse Pointers). Nice feature. When it became necessary, she easily (and intuitively, without specific instructions from me) granted me control and watched as I walked her through the fix, explaining it along the way. Several times I handed control back to her so she could do part of the tasks.

In the recent past I've paid for similar services from other companies that also work well. Some of them don't rely on an installed program like this one does, but the SharedView app download is small and simple and works well on either Windows XP SP2 or Vista. I'd like to see it offered as a click-once app to easy use (at least as an option, if this type of app can even be deployed that way).

One of the great tests of success in today's software utility market is usability. One way I gauge the usability of an app is via watching my mom use it. If she can pick it up without much prompting, it generally passes. If she can't figure it out, chances are others can't either, and so it fails. SharedView met the expectations of that litmus test. Another great example of meeting the usability requirements and needs of the average user is Windows Home Server, which I started using in my own home not too long ago and about which I have written a couple times. There's some true-quality stuff coming out of Redmond right now for the average user, and that's good to see.

Over the past year I have become more and more aware of the value of doing some of those things that I've always wanted to do, yet have never quite gotten myself to execute on. I certainly have my limits, but I've worked to push myself a bit and to welcome this likely-midlife-crisis with open arms -- just jump right in and live a little. What the heck, eh?

So, this weekend I'm flying with a friend to Boston and we're going to the playoff game between the Chargers and the Patriots for the AFC championship. A couple lucky tickets combined with frequent flier and hotel credits make for a cheap relatively affordable weekend of fun. We were darned lucky to be able to line it all up last minute with flights and rooms available purchased with mileage credit, etc. The idea didn't even cross my mind until right after the Chargers beat the Colts last weekend.

For those not intimately acquainted with American Football, the winner of the game we're going to will play the winner of the NFC championship game in the Superbowl in a couple weeks. the Patriots are undefeated this year, and I certainly hope San Diego shows up and makes it a fun game to be at.

The temperatures in the Boston area Sunday are supposed to be in the teens or lower 20's (Fahrenheit), but hey it could be a lot worse. The NFC championship is being played in Green Bay, Wisconsin (Packers vs. the Giants) and the temperatures there are supposed to be considerably lower, with a wind-chill in the hell-frozen-over range. ESPN has a great article on cold-weather football with lots of good trivia for anyone interested.

And before you ask... No, I'm not going to spend the incredible amount of money it takes to go to the Superbowl these days. That's why they make HDTV. :)

Wow, I sure have been making use of my HP MediaSmart Windows Home Server since I acquired it late last year, and to be honest I have not really even scratched the surface. With 64-bit client support coming soon, I am excited about the future, too.

After working with a bunch of music, video and image files over the past few weeks, not to mention computer backups, the single 500GB drive that it came with is both a little small and represents a single point of failure that I realized I don't want to take a chance on. So, I logged onto newegg.com last weekend and ordered a 1TB Western Digital SATA2 hard drive at a great price. It arrived today,and I slapped it into one of the three open trays and slid it into the slot. Within half a minute the drive showed up in the Home Server console and I was able to add it to the storage with a couple clicks and a two minute waiting time:

What a slick and fool-proof process they've come up for adding drives in Windows Home Server. Anyone can do it. It's great stuff, and the add-on community is thriving - There's a whole slew of community-created programs that you can install on your home server to add functionality. It's quite useful and a lot of geeky fun.

With the addition of community programs and the overhead of the additional HP software, the memory's a bit short. So I have a 2GB sick of RAM sitting on my desk, wait for me to decide if warranty risks of taking it apart to beef up the RAM are worth it. Do I dare?

Well, it's finally happened. Apple has released iTunes v7.6.0.29 along with the iPhone v1.3 software, adding support for syncing with 64-bit Windows Vista in this new version. So, I have updated the iPhone (and lost my custom apps at least for now as a result) and am a happy camper. Relying on the aging Mac Mini desktop to sync was not working well for me. Now I can sync to my notebook.

Apple plans to introduce formal support for third-party apps through their own developer program next month, so I will happily wait a little while and hope for my couple of apps that I liked (especially the iFlix NetFlix manager app, one of my recent favorites).

There are some great enhancements, especially in the Google Maps application. Check out some of the new capabilities here in a Apple video tour of the January '08 update.

I left my iPhone at home one day last week when I drove to Portland for a day of jury duty followed by time trying to meet up with other people I know. I didn't notice until I was halfway to the city that I had forgotten it, so it was too late to go back and get it. All afternoon I realized how much I rely on my phone for regular daily stuff and how much others rely on my having it with me, as well.

Now I just have to sync up my purchased stuff from the iTunes Store and get the Audible account moved over. After that, I'm golden!

I wrote before about my new HP MediaSmart Home Server, as well as the fact that there is no 64-bit client support available yet. In the end, it seems the Microsoft Vista team had to make a change to the OS to fix an unrelated issue, and the cascading effect of that change was that certain native backup capabilities on 64-bit windows clients (upon which Home Server relied) got broken. All that happened while Home Server was in development.

Well anyhow, looks like the CES show will be the place where HP will announce a soon-available client for 64-bit Vista. I'm happy, because Windows Home Server and the HP MediaSmart hardware and software are pretty darned great stuff, if you ask me.

So - Thank you in advance, HP. The AV software from McAfee (note that Avast! also recently released a AV package for WHS), enhanced media streaming and other features will be nice to take a look at, as well. Good deal!

News and some detail can be found here:

• Anti-Virus Protection, Enhanced Media Streaming and Vista x64 Compatibility Coming to the HP MediaSmart Server Jan 3, 2008 (link to wegotserved.co.uk)
• The Windows Home Server Team Answer Your Questions! October 4, 2007 (link to wegotserved.co.uk, contains background about the development process including the 64-bit client problems they encountered)

Merry-Freakin'-Christmas from Blockbuster. NOT.

Not too long ago I wrote about Blockbuster's sudden and substantial rate increase. People were upset, me included. I begrudgingly gave in, however, and started paying the $7.00 increase - from $17.99 to $24.99 - per month for unlimited in-store exchanges and three mail rentals at a time.

A few minutes ago I got a very "friendly" email from Blockbuster, letting me know some of the great rentals they have available in the first paragraph, encouraging me to exchange movies in the store in the second paragraph, and then pretty much putting it to me without so much as kissing me first in the third paragraph. Here is exactly what it said (click the image on the right to see a screen shot of the actual email with the section highlighted):

"To continue to bring you the unmatched convenience of both online and in-store DVD rentals, your monthly subscription fee will change from $24.99 to $34.99. This adjustment† will go into effect on your next billing cycle on or after December 27, 2007. The benefits of your subscription plan will remain the same."

So, in the time span of about four to five short months, my monthly cost has gone from $17.99 to $34.99 per month (in other words, roughly doubled) and the services I get for the money are less (since I no longer get the two coupons a month for movie or game rentals that I got for a couple years before their August price and service change).

"Ok, but that's the last straw."

As soon as the month I have already paid for runs out mid-January, I'm dumping this mess. Goodbye Blockbuster. Hello Netflix. I feel like I have to encourage everyone to do the same. This is - in my opinion - not a consumer-friendly company. I know they need to make a profit, and I was willing to support that. But dragging your customers through this kind of mess is not the way to do it. Believe me when I say I'd likely have been willing to spend more for better service (or at least consistently good service in both the store and online, which I don't get today), had a reasonable rate increase been effectively sold to me.

If some kind of miracle happens between now and January 18th when my account runs out and Blockbuster changes their plans, I'll consider sticking around. But it won't happen. This appears to be just more of the same decisions. It's too bad.

If you received an email, feel free to make use of the comments here. What does yours say? What do you think? What - if anything - will you be doing about it? If you agree with me and want to share the sentiment, you can link to http://www.boycottblockbuster.com/, which points to this page.

Time to stand up and say something.

Added -- Some other comments made on other blogs:

• Ars Technica analysis
• Hacking Netflix
• Gizmodo
• SlashGear
• Five Cent Nickel
• Ipod Express

And, via Gizmodo, a humorous visual that effectively captures the essence of the situation...

 

I also noted that new subscribers to Blockbuster (people who go there today to sign up for the first time) will be recruited under the "old" pricing plans, as they have not changed the information on the web site. That seems a little disingenuous, if not completely dishonest, doesn't it? Click the image below to see a fill-size screenshot of their pricing page on the site as of the morning of December 20th. I'd hope they'd at least get this problem fixed soon (unless they don't intend to increase the prices for new customers, of course).

Here we are again, right up against the holidays and I am not ready yet... as usual. On Friday afternoon I'll be jumping in the truck and starting the drive from Portland to Colorado, where my mom and step dad live - as well as my brother and niece, two stepbrothers, and related extended family. My mom had knee replacement surgery just yesterday (which she says went well according to the doc), and so there are a couple important and good reasons to be down there this Christmas.

My good friend Cory, who lives in Portland but whose family is in Minnesota, is going to make the road trip with me and we're going to spend a couple/few days on the slopes in the Keystone area after Christmas before we head back. We're pretty excited and looking forward to the trip. We were going to travel by air, but decided to drive instead for a number of reasons. Renting a four wheel drive in Colorado that week is obscenely expensive as it turns out, and we plan to be in places where it's likely necessary. By the time all is said and done, it's a little less costly and we get to spend more time in Colorado if we drive. Plus we have not done a road trip this year, and we have this tradition thing to keep up.

I recently obtained a HD video camera that I have not used yet beyond taking it out of the box, charging the battery and making sure it works, so I will be taking that with me. Maybe I will do some filming on the slopes and see how HD video does when making YouTube videos or something fun like that. I better do some quick research to see how to best deal with the video for web publication.

Nothing brightens and warms the heart during the holiday season quite like a summons demanding appearance at the United States Federal Courthouse for jury duty. I received my official letter of "congratulations" (yes, they actually use that terminology) in the mail today. I have to appear on the morning of January 8th.

I hope it's not one of those trials that never ends. Fingers crossed. :)

Actually, I believe in the importance of the jury system and take seriously the duty. It's just such a schedule crusher, is all. Luckily I have nothing specific planned that week (or the next), or at least nothing that can't be kept flexible.

A couple weeks ago I rounded up three of my younger, somewhat crazier friends and (without telling them where we were going or what we were doing) jumped on a train to go from Portland to Seattle. This was our Secret Plan day, which sounds kind of stupid but really is a lot of fun. Especially for me, since I am the only one who knows the secrets, and the plan.

It works like this: I picked up my the guys - Broc, Cory and Dave - early in the morning on Thursday. All they knew was that they had to keep Thursday and Friday completely free. That's it - the rest is pretty much all trust and blind faith. But hey - what are friends for, after all? Broc and Dave I have known since I moved to Oregon (they were good friends of my son's years ago), and Cory I have known for a few years (he was in the Navy with Dave).

The whole time, each step of the way, they had no idea what was happening next, where we were going or what we were doing. After picking them up we went downtown and parked. We started walking and ended up at the Portland Union Station. I already had the train tickets in my cool Top Secret folder (heh), so we got on a train (which luckily was not announced out loud while we were in the building, so the guys didn't even know for sure which direction it was going), and pulled out of the station. It turned out we were heading for Seattle.

A few hours later we got off the train and wandered around a bit. We grabbed some burgers and then went to the Pirate Store at Pier 57 on the waterfront, and finally ended up at the Seattle Underground tour for an hour or so, which is pretty fun and interesting. There's a fascinating and surprising history to the City of Seattle, and if you have not done the tour and find yourself in the area I recommend it. From there we checked out a kilt store next door (random, I know - and not part of the plan, heh) and then found our hotel over near Seattle Center.

By this time it was getting to be evening, and we headed out to find some food before the next secret plan stop. Of course, I was guiding us to the general area we needed to be in, but not telling why. We found a good pizza place near the Space Needle and went in. Then, once everyone was seated I told them I had to leave take care of some things and that I would be back. Oh, and that they should not get too drunk or anything since they'd have to walk from the pizza place.

I went out in the cold, found the will-call ticket window at Key Arena (which opened more than half an hour late - why is it that Key Arena staff never seem to be able to get information right, anyhow? Right-arm/left-arm issues are rampant, but I digress...). After freezing my butt off for a while, I had what I had come for (less a half-hour of much-needed time). So, I started running back to the pizza place with almost no time to spare.

I gathered they guys and told them we had to split (like right now), and we started walking toward Seattle Center. The frustrating thing about Secret Plan Day is that at times it's nearly impossible to actually keep the secret - Eventually you want to say something because you're excited and don't want to keep it to yourself anymore, but you can't do that or you'd ruin the whole concept, ya know. Anyhow, I was pretty excited about the next part, so I waited (it was difficult) until we were standing just outside key arena before I took out the next part of the plan and showed it to them: Second row tickets for Dane Cook, who is one funny guy that these three friends of mine really like. The looks on each of their faces when they realized where we were going and what we were doing made it all worthwhile.

Then I pulled out the four back-stage passes and the looks got even better. Heh.

Since the title of this post makes it seem like it should be about Dane Cook, let me say that the back-stage meet and greet things they do with these special tickets (I won them in an auction) is really cool. We got to say hi real quick, shake hands and have our picture taken with him, which was cool. He autographed our tickets and stuff, too. And then we headed out onto the arena floor for some of the best seats in the house and really enjoyed the show. He did a lot of new material, which made it even more fun. It was a great performance. I was able to take a couple of pictures before my camera battery died... I really need to buy an extra battery.

It was a late night, and the next day we boarded another train and headed back home. It was a pretty cool couple of days. Hanging out with just your friends can be a really fun thing to do. Surprising them is even better.

Note: This article contains a cheesy workaround that worked for me. It is most certainly unofficial and not supported by HP or anyone else (including me). So, if you use it - just know your mileage may vary.

I have a HP Pavillion dv9620 laptop with Vista 64-bit Ultimate preinstalled. It's a big-ol' laptop and has a webcam built into the top of the display. But the camera has hardly ever worked. For months I am grumbled at it each time it has failed to work in MSN Messenger and in HP's own QuickPlay software. It worked for a while, then it worked only when I first started the computer, and eventually it would not even do that, so I pretty much gave up. HP drivers did not help, one bit. Heck, just finding them on the HP web site is a painful task.

Tonight Carl Franklin asked me to help his test his webcam. We fired up Live Messenger and I was able to see and hear him just fine, but of course mine was not working. Pretty lame.

Call that inspiration. Nothing worse for a technical person than to have a broken system, especially in front of other techies, heh. I decided to start searching the web again this evening for some sort of solution, and after finding a bunch of the same-old forum and newsgroup posts, I ran across what appears to be a real gem. And it seems to have solved my problem: No more failure to see and use the HP webcam, at least so far in Messenger and in QuickPlay.

The camera is made by a company called Chicony, and it turns out Acer also uses their cameras (as do some other manufacturers). Note that not all HP notebooks have Chicony webcams - some have Ricoh models and possibly other brands. Check your Device Manager to see who the hardware manufacturer is listed as to help determine whether or not this is the right method for you (or just try it and deal with any glitches if it's not). But, according to this post in the forums at notebookreview.com, people are having great success using the Acer drivers on their Vista Pavillion machines with the built-in webcam.

I downloaded the drivers, checked them for safety, and updated my system by following the simple instructions. Voila! It works! It shows up in device manager as an Acer webcam, but I can live with that, for sure.

With a little luck it will keep working. Before posting this I rebooted and rechecked the camera, opened a few programs to try to screw it up, etc. So far, so good.

Here are the brief instructions (as slightly adapted from the post by Dylan Bennett at notebookreview.com):

• First, download the drivers. I got mine from here, and yes -- these are the drivers I used on my 64-bit Vista install: Acer Extensa 5210 Chicony Webcam Driver 5.7
• Next, unzip the installer executable file, then run the setup program and do the reboot thing.
• After you log back in Windows should tell you it's setting up your devices and finding the drivers. Let it finish.
• Open the Control Panel and then open the Device Manager.
• Find the webcam under "Imaging Devices." On mine it was listed as a generic USB 2.0 device. Yours may be different.
• Right-click on the webcam entry in Device manager and select "Update Driver Software..." from the menu.
• Choose "Browse my computer for driver software."
• Choose "Let me pick from a list of device drivers on my computer."
• Uncheck the "Show compatible hardware" checkbox.
• Scroll in the list to find Chicony in the dialog's manufacturer list.
• Choose the "Acer Crystal Eye webcam."
• You're most likely going to be warned that the driver cannot be confirmed to be compatible. You can tell it to install anyway.
• Wait for the driver to be installed.
• Check Device Manager under the Imaging devices section again and see what you have. Note that the webcam will likely now be listed as an Acer Crystal Eye webcam.

Now, go and use Messenger or whatever program has given you fits before and see what your results are. Be sure to reboot and try all your webcam-enabled programs. Give it a real brutal test before declaring success. For me it's been great, but your mileage most certainly may vary, and I am certain HP will not consider this a supportable configuration, heh.

Proof it works for those that need it, here you go. Gotta love the reflection-in-the-glasses thing, heh:

Good luck!

UPDATE re CompUSA: I'm still not sure where the $150 price cut came from, but Reuters and everyone else is now reporting that CompUSA is being sold and, from the sounds of things, pretty much shut down. Stores will remain open over the holidays with some likely fire-sales, so might be the time to see what can be had over the next few weeks... This might explain why the company didn't try to sell me their obligatory extended service plan when I purchased the home server...

I bit the bullet this past weekend and went online over at CompUSA.com and found that a HP MediaSmart Server (the new Windows Home Server OEM device) was in stock at one of the Portland stores (Jantzen Beach, specifically). So, I reserved it online for in-store pickup and headed into the city to get it.

Much to my (very pleasant) surprise, when I got to the store and they rung it up, the $599 price was automagically reduced by $150 as an instant savings at the register (nice!), so I ended up with the 500GB model (the EX-470) for $450 -- which was just fine by me! All that saved money can go toward another hard drive to add to the system's storage capacity.

When I picked up the new server, I was on my way to the Van Halen concert in Portland with a friend (more on that later and in another post), and then we spent the entire next day skiing at Mt. Hood Meadows on Sunday, so the Home Server didn't even get unpacked until late on Sunday night.

HP's packaging is top-notch, and the documentation was excellent. Seriously, the quick setup steps for the hardware are literally three simple steps - Connect the power cord, connect to your LAN router with the Ethernet cable that comes in the box, and push a button. After that, go to a computer on your LAN, pop in a CD, and follow the instructions on the screen.

Windows Home Server is a very cool system. It allows local LAN and remote access, including web-based access for visitors (friends, family, etc). It will back up your computers each night in case something goes wrong with them (Unless you're running an x64 version of Windows - more on that in a minute) and creates a centralized place on your network for media files (audio, video and pictures) as well as installable software. You can copy any type of file to the system (in backup mode or otherwise). The multimedia capabilities allow you to use your Xbox 360 to play the multimedia content stored on the server. The HP flavor also includes iTunes integration (one central library for all your computers) and some other nifty stuff. I pretty much hate iTunes these days (more 64-bit compatibility gripes plus its just so frustratingly bloated), so I am not sure I will actually use that capability, but it's nice to have.

I have one compliment and one gripe at this point in my story about setting up the Home Server out of the box. On the positive side, the setup software is run on a client PC attached to your LAN, and the setup wizard is very user friendly, simple and quick to execute. You don't have to be anything close to a computer expert to install and run this system, which is a huge victory for Microsoft - Great job! However, when I tried to do the setup the first time I did so from my main laptop, which I bought a few months back at a consumer store (also from CompUSA). It would not work. The problem is that my laptop has Vista Ultimate 64-bit installed on it by HP, and the Home Server Client software simply does not support 64-bit Windows. This strikes me as pretty ridiculous in this day and age, and I was more than just a little disappointed. I suppose I could (should) have done my Google homework before I purchased, but seriously... Bill Gates was stating Microsoft's commitment to 64-bit computing back in 2004 and 2005 (and since), and with 64-bit operating systems being installed on consumer computers and sold in retail stores, it seems to me it's time to be shipping 64-bit support in all software right up front. It's really not just about early adopters anymore. And Microsoft's not the only culprit here - there are a number of manufacturers of software that decide for whatever reason not to build in 64-bit support. But I think that's a mistake. That said, word is that 64-bit Home Server Connector bits will be available in early 2008. Okay, so I wish the situation was different but it's not. And yes, building software is expensive and complicated, etc. etc. etc... I know. End of rant.

Once I set up the server using a different client computer (one running 32-bit Vista this time), things went very well. It took very little time and was flawless. My DLink router has UPnP enabled, but for some reason Home Server was not able to automatically configure the Home Server's remote access settings on it, so I had to set that up manually (just three port-forwarding settings after establishing a fixed IP address for the home server on the router). Once the router was configured (the setup program provided all the information I needed in clear and plain language), everything checked out just fine.

From the 32-bit machine I can access the Home Server via a slick console application that lets me configure and access data. It's really a terrific interface, especially for a v1 product. It shows the value in building a clean, network-enabled Windows application over a browser-based web app, for sure. I especially like the remote application capability, which is basically a limited RDP connection for administrative purposes. In order to access the server from my 64-bit machine I can map a drive and/or access the file system via a UNC share name(\\servername\sharename), so I was able to upload a slew of pictures to a shared library that way. I can also RDP into the server from the 64-bit laptop with the standard Windows remote desktop client and launch the Home Server Console that way from the server's remote desktop (a stern warning page is displayed when you login via plain-old RDP, saying be careful and that the preferred method is to use the management console installed on a remote client machine). I'll be glad when the 64-bit client software is available so I don't have to do that anymore.

The hardware is nice, looks good, is fairly quiet and has plenty of expansion room. I've started looking at 750GB and 1TB drives online to determine what I want to buy to build the system out. It has three internal drive bays free and three USB ports as well as an eSATA port on the back, so expansion is pretty flexible. In a podcast that my friend Scott did a while back where he interviewed Windows Home Server product unit manager Charlie Kindel (it's a great show, so you should go listen), Charlie said they had one test system where they added something like 26 drives - wow... The way the system works is cool. You add new drives to the system and it recognizes them and basically through the magic of the underlying software your storage pool grows larger. So, you don't have to worry about multiple drive letters or anything. Also, once you add drives beyond the first one you can set up duplication of folders between different drives for data redundancy. That way the content you mirror will survive the failure of any given drive. Not quite the RAID level of fault tolerance but a good and easy-to-use compromise that provides novice-level flexibility and usability you don't tend to find with RAID controllers. In all, the whole Windows Home Server disk/file subsystem is pretty darn cool.

Perhaps one of the most exciting aspects of Windows Home Server, which I plan to check out over the next few days, is the fact that they opened the system up to allow developers to create add-on applications that expand and enhance the Home Server capabilities. There are already a number of really cool apps, which you can check out here.

So, that's my first impressions. Initial software frustrations aside (and with a future resolution on the horizon), the HP hardware and software and the Windows Home Server operating system check out with very high scores. I can recommend this system without hesitating, and even if you don't know much about computers or networking you'll be able to set this system up and start backing up and sharing information both on your home network and over the Internet with family and friends.