greg hughes - dot net - Home Servers http://www.greghughes.net/rant/ Note that the contents of this site represent my own thoughts and opinions, not those of anyone else - like my employer - or even my dog for that matter. Besides, the dog would post things that make sense. I don't. http://www.greghughes.net/images/gregheadshot1.png greg hughes - dot net - Home Servers http://www.greghughes.net/rant/ en-us Greg Hughes Tue, 23 Nov 2010 19:27:43 GMT newtelligence dasBlog 2.1.8015.804 greg@greghughes.net greg@greghughes.net http://www.greghughes.net/rant/Trackback.aspx?guid=3ec657c7-ffd6-4450-bc77-ded94bdad773 http://www.greghughes.net/rant/pingback.aspx http://www.greghughes.net/rant/PermaLink,guid,3ec657c7-ffd6-4450-bc77-ded94bdad773.aspx http://www.greghughes.net/rant/CommentView,guid,3ec657c7-ffd6-4450-bc77-ded94bdad773.aspx http://www.greghughes.net/rant/SyndicationService.asmx/GetEntryCommentsRss?guid=3ec657c7-ffd6-4450-bc77-ded94bdad773 7

Yesterday I wrote about how I enabled my MacBook Air to share a wireless laser printer in my home office so I could print to it using the new Air Print feature in iOS 4.2 on the iPad. That works great, but since my MacBook is only *almost* always on, I started thinking about other options. I have a first –generation (Power-PC-based) Mac Mini in my living room that basically doesn’t get used at all, but I don’t think OS x 10.6.5 is really an option for that. So, I turned my attention to the other always-on computer in my home office, the HP MediaSmart Home Server.

airprint_services I wondered to myself, has anyone come up with a way to share printers accessible from a Windows computer with AirPrint-capable iOS devices? And, sure enough, someone has already done just that. The short tutorial covers Windows workstation versions (XP, Vista and Win7), but the instructions apply to Windows Home Server and other flavors of Windows Server, as well. My Win Home Server is based on the Server 2003 OS.

I’m going to add to a couple of the original steps here, since there are a few things I did that were not included in the instructions on the original post.

First of all, you need printer drivers installed for the printer you want to share on the system. You may not have printers already installed and shared on your Windows Home Server. To do this, you can make a Remote Desktop connection to your WHS  machine, and from there follow the standard steps to set up a local printer. In my case, I downloaded the Brother printer drivers and set up the network printer and printed a test page from the WHS machine to make sure it was working properly. Next, I followed the instructions on the port referenced earlier, and then I enabled sharing on the networked printer.

The first time I connected to the printer, a little padlock icon appeared on the iPad (see beow), indicating a Windows account user name and password were required to access the shared printer. This, of course, can be controlled and changed on the Windows computer in the printer sharing security preferences:

     print_locked

After entering the account information, the printer was accessible and printing of various content (text, graphics and photos) worked flawlessly. One big difference I noticed between sharing the same printer through Windows vs. the Mac is that when connected via the Windows AirPrint share, an option for double-sided printing appeared. That option is missing when connecting to the same printer shared via the Mac. Here’s the Windows-connected printer options as seen on the iPad:

     print_windows

So, I now have my laser printer shared across all devices on my LAN, including iOS 4.2, via the Windows Home Server, no extra charge!

Related Links:

 



greghughes.net weblog - copyright 2009 - licensed under a Creative Commons License. Enable AirPrint printer sharing on Windows Home Server for iOS 4.2 devices http://www.greghughes.net/rant/PermaLink,guid,3ec657c7-ffd6-4450-bc77-ded94bdad773.aspx http://www.greghughes.net/rant/EnableAirPrintPrinterSharingOnWindowsHomeServerForIOS42Devices.aspx Tue, 23 Nov 2010 19:27:43 GMT <p> Yesterday I <a href="http://www.greghughes.net/rant/TherersquosNoAirprintFromIOS42InOSX1065NdashButTherersquosAnAppToFixThathellip.aspx" target="_blank">wrote</a> about how I enabled my MacBook Air to share a wireless laser printer in my home office so I could print to it using the new Air Print feature in iOS 4.2 on the iPad. That works great, but since my MacBook is only *almost* always on, I started thinking about other options. I have a first –generation (Power-PC-based) Mac Mini in my living room that basically doesn’t get used at all, but I don’t think OS x 10.6.5 is really an option for that. So, I turned my attention to the other always-on computer in my home office, the <a href="http://www.greghughes.net/rant/HPWindowsHomeServerMyFirstCoupleOfDaysAQuickReview.aspx" target="_blank">HP MediaSmart Home Server</a>. </p> <p> <img style="border-bottom: 0px; border-left: 0px; margin: 0px 0px 10px 20px; display: inline; border-top: 0px; border-right: 0px" title="airprint_services" border="0" alt="airprint_services" align="right" src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/EnableAirPrintprintersharingonW.2devices_A12F/airprint_services_1.png" width="435" height="209"> I wondered to myself, has anyone come up with a way to share printers accessible from a Windows computer with AirPrint-capable iOS devices? And, sure enough, <a href="http://jaxov.com/2010/11/how-to-enable-airprint-service-on-windows/" target="_blank">someone has already done just that</a>. The short tutorial covers Windows workstation versions (XP, Vista and Win7), but the instructions apply to Windows Home Server and other flavors of Windows Server, as well. My Win Home Server is based on the Server 2003 OS. </p> <p> I’m going to add to a couple of the original steps here, since there are a few things I did that were not included in the instructions on the original post. </p> <p> First of all, you need printer drivers installed for the printer you want to share on the system. You may not have printers already installed and shared on your Windows Home Server. To do this, you can make a Remote Desktop connection to your WHS&nbsp; machine, and from there follow the standard steps to set up a local printer. In my case, I downloaded the Brother printer drivers and set up the network printer and printed a test page from the WHS machine to make sure it was working properly. Next, I followed the instructions on the port referenced earlier, and then I enabled sharing on the networked printer. </p> <p> The first time I connected to the printer, a little padlock icon appeared on the iPad (see beow), indicating a Windows account user name and password were required to access the shared printer. This, of course, can be controlled and changed on the Windows computer in the printer sharing security preferences: </p> <p> </p> &nbsp;&nbsp;&nbsp;&nbsp; <img style="border-bottom: 0px; border-left: 0px; display: inline; margin-left: 0px; border-top: 0px; margin-right: 0px; border-right: 0px" title="print_locked" border="0" alt="print_locked" src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/EnableAirPrintprintersharingonW.2devices_A12F/print_locked_2.png" width="242" height="241"> <p> After entering the account information, the printer was accessible and printing of various content (text, graphics and photos) worked flawlessly. One big difference I noticed between sharing the same printer through Windows vs. the Mac is that when connected via the Windows AirPrint share, an option for double-sided printing appeared. That option is missing when connecting to the same printer shared via the Mac. Here’s the Windows-connected printer options as seen on the iPad: </p> <p> &nbsp;&nbsp;&nbsp;&nbsp; <img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="print_windows" border="0" alt="print_windows" src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/EnableAirPrintprintersharingonW.2devices_A12F/print_windows_1.png" width="242" height="239"> </p> <p> So, I now have my laser printer shared across all devices on my LAN, including iOS 4.2, via the Windows Home Server, no extra charge!<br> </p> <p> Related Links: </p> <ul> <li> <a href="http://www.greghughes.net/rant/TherersquosNoAirprintFromIOS42InOSX1065NdashButTherersquosAnAppToFixThathellip.aspx" target="_blank">Enabling AirPrint support in OS X 10.6.5</a> </li> <li> <a href="http://jaxov.com/2010/11/how-to-enable-airprint-service-on-windows/" target="_blank">How to enable AirPrint service on Windows</a> </li> </ul> <p> &nbsp; </p> <p> <div style="padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px" id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:b6abf619-6c0d-4ca5-9347-677d2ac9eb9a" class="wlWriterEditableSmartContent">Technorati Tags: <a href="http://technorati.com/tags/Air" rel="tag">Air</a>,<a href="http://technorati.com/tags/Print" rel="tag">Print</a>,<a href="http://technorati.com/tags/Airprint" rel="tag">Airprint</a>,<a href="http://technorati.com/tags/iPad" rel="tag">iPad</a>,<a href="http://technorati.com/tags/Windows" rel="tag">Windows</a>,<a href="http://technorati.com/tags/Home" rel="tag">Home</a>,<a href="http://technorati.com/tags/Server" rel="tag">Server</a>,<a href="http://technorati.com/tags/Apple" rel="tag">Apple</a>,<a href="http://technorati.com/tags/iOS" rel="tag">iOS</a>,<a href="http://technorati.com/tags/AirPrint" rel="tag">AirPrint</a>,<a href="http://technorati.com/tags/4.2" rel="tag">4.2</a> </div> > <br /> <hr /> <font size="1">greghughes.net weblog - copyright 2009 - licensed under a <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">Creative Commons License</a>.</font> http://www.greghughes.net/rant/CommentView,guid,3ec657c7-ffd6-4450-bc77-ded94bdad773.aspx Apple Home Servers Tech Windows
http://www.greghughes.net/rant/Trackback.aspx?guid=c9d0f424-1064-48c7-833a-d1208680b63c http://www.greghughes.net/rant/pingback.aspx http://www.greghughes.net/rant/PermaLink,guid,c9d0f424-1064-48c7-833a-d1208680b63c.aspx http://www.greghughes.net/rant/CommentView,guid,c9d0f424-1064-48c7-833a-d1208680b63c.aspx http://www.greghughes.net/rant/SyndicationService.asmx/GetEntryCommentsRss?guid=c9d0f424-1064-48c7-833a-d1208680b63c 5 Since I "needed" a new high-def disc format player (specifically Blu-Ray Disc) to take the place of my suddenly-antiquated HD-DVD hardware, and since Thursday was my 41st birthday, I decided to get what is arguably the best Blu-Ray player out there. The Playstation 3. Ah mid-life and gadgety toys, heh.

As luck would have it, my dad called me and asked what I'd like for my birthday. We go through the same conversation each time, and it's really kind of funny. I say I don't know and we end up in a friendly stalemate. I told him what I was looking at buying for myself, and he got interested. It was too much money, really - but he insisted (thanks, dad!). And so I went to the local big box store and picked one up and brought it home last night.

I'm not going to do a PS3 review. Yes, it's great hardware and the Blu-Ray discs play great. Watched 3:10 to Yuma last night (good flick). I was impressed, just as I was with HD-DVD.

But you know what impresses me more? In the past few weeks I have seen device after device - from different, even competing manufacturers - communicating with each other to share media on the network.

My Windows Home Server and Windows Media Player devices can share out media with the Xbox 360, with my DirecTV HD-DVR receiver, and now I see also with the new Playstation 3. Streaming audio around the house that's stored on the Home Server is a daily occurence around here. The XBox 360 is, of course, also a front-end for Media Center (which runs on my Vista Ultimate machine), and once we see a real-world version of the DirecTV USB component receiver (dubbed the HDPC-20 and currently in limited beta we're told), that's going straight into my den and should truly round out my interconnected, media-driven home.

With about 2TB (yeah, terabytes - who woulda thunk it a few years ago eh?) of Home Server storage and all these devices spread around that stream various media, it really is turning into a whole different kind of user experience - and a good one at that.



greghughes.net weblog - copyright 2009 - licensed under a Creative Commons License. Playstation 3 and all this integrated media stuff http://www.greghughes.net/rant/PermaLink,guid,c9d0f424-1064-48c7-833a-d1208680b63c.aspx http://www.greghughes.net/rant/Playstation3AndAllThisIntegratedMediaStuff.aspx Sat, 12 Apr 2008 07:28:38 GMT Since I "needed" a new high-def disc format player (specifically Blu-Ray Disc) to take the place of my suddenly-antiquated HD-DVD hardware, and since Thursday was my 41st birthday, I decided to get what is arguably the best Blu-Ray player out there. The Playstation 3. Ah mid-life and gadgety toys, heh.<br> <br> As luck would have it, my dad called me and asked what I'd like for my birthday. We go through the same conversation each time, and it's really kind of funny. I say I don't know and we end up in a friendly stalemate. I told him what I was looking at buying for myself, and he got interested. It was too much money, really - but he insisted (thanks, dad!). And so I went to the local big box store and picked one up and brought it home last night.<br> <br> I'm not going to do a PS3 review. Yes, it's great hardware and the Blu-Ray discs play great. Watched 3:10 to Yuma last night (good flick). I was impressed, just as I was with HD-DVD.<br> <br> But you know what impresses me more? In the past few weeks I have seen device after device - from different, even competing manufacturers - communicating with each other to share media on the network.<br> <br> My <a href="http://www.greghughes.net/rant/HPWindowsHomeServerMyFirstCoupleOfDaysAQuickReview.aspx">Windows Home Server</a> and Windows Media Player devices can share out media with the Xbox 360, with my DirecTV HD-DVR receiver, and now I see also with the new Playstation 3. Streaming audio around the house that's stored on the Home Server is a daily occurence around here. The XBox 360 is, of course, also a front-end for Media Center (which runs on my Vista Ultimate machine), and once we see a real-world version of the DirecTV USB component receiver (<a href="http://www.engadgethd.com/2008/01/08/directvs-pc-tuner-is-real/">dubbed the HDPC-20</a> and currently in limited beta we're told), that's going straight into my den and should truly round out my interconnected, media-driven home.<br> <br> With about 2TB (yeah, terabytes - who woulda thunk it a few years ago eh?) of Home Server storage and all these devices spread around that stream various media, it really is turning into a whole different kind of user experience - and a good one at that.<br> <p> </p> <br /> <hr /> <font size="1">greghughes.net weblog - copyright 2009 - licensed under a <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">Creative Commons License</a>.</font> http://www.greghughes.net/rant/CommentView,guid,c9d0f424-1064-48c7-833a-d1208680b63c.aspx Home Servers Tech Windows Media Technology
http://www.greghughes.net/rant/Trackback.aspx?guid=b3b7c0e7-504c-48cb-9c3c-6020e6851db0 http://www.greghughes.net/rant/pingback.aspx http://www.greghughes.net/rant/PermaLink,guid,b3b7c0e7-504c-48cb-9c3c-6020e6851db0.aspx http://www.greghughes.net/rant/CommentView,guid,b3b7c0e7-504c-48cb-9c3c-6020e6851db0.aspx http://www.greghughes.net/rant/SyndicationService.asmx/GetEntryCommentsRss?guid=b3b7c0e7-504c-48cb-9c3c-6020e6851db0 3

When the Windows Home Server data corruption bug surfaced a couple months ago (updated information is available here), the Home Server team at Microsoft focused their efforts on squashing it. As a result, the Home Server Power Pack 1 release was delayed as a lower priority (and understandably so at the time).

image Microsoft has recently announced that they plan to get the data corruption issue fix out to the market in June this year, but Home Server Product Manager Todd Headrick posted a query on the Microsoft Home Server forums asking people if they'd like to get Power Pack 1 sooner, or if we'd prefer to wait for the corruption fix and take it all at once.

I've voted for the "Power Pack now" option, and will be glad to take a data corruption fix later. As long as there's no dependencies on the bug fix (and it sounds like there's not), and as long as additional risk is not being generated, releasing the power pack earlier is certainly the best option, as long as it's ready. Here are a few reasons why:

  • 64-bit client support, so users of Vista 64-bit can use the home server as it is meant to be used (this appears to be a broader-reaching and more-common issue than many thought it would)
  • Ability to back up the home server folders to external drives
  • Usability and UI improvements
  • Other fixes
  • Opportunity some good news into the channel (it's a great product with a lot of goodwill in the community that would benefit from some positive karma right now)

As a general rule, big companies (or "enterprise" customers, as we call them) want multiple changes carefully packaged together, with as many problems solved in one patch or update as possible, with low risk. But Home Server is notably not an enterprise product. Instead it is laser focused on a crowd where more frequent feature and fix releases are preferred, encouraged and asked for. So, in the case of Home Server it's probably best to adopt something closer to an iterative release cycle.

What do you think? Microsoft wants to know!



greghughes.net weblog - copyright 2009 - licensed under a Creative Commons License. Windows Home Server Power Pack 1 - Do you want it now or later? http://www.greghughes.net/rant/PermaLink,guid,b3b7c0e7-504c-48cb-9c3c-6020e6851db0.aspx http://www.greghughes.net/rant/WindowsHomeServerPowerPack1DoYouWantItNowOrLater.aspx Tue, 11 Mar 2008 16:25:04 GMT <p> When the <a href="http://www.microsoft.com/windows/products/winfamily/windowshomeserver/default.mspx" target="_blank">Windows Home Server</a> data corruption bug surfaced a couple months ago (<a href="http://support.microsoft.com/kb/946676/en-us" target="_blank">updated information is available here</a>), the Home Server team at Microsoft focused their efforts on squashing it. As a result, the <a href="http://blogs.technet.com/homeserver/archive/2008/01/06/windows-home-server-power-pack-1.aspx" target="_blank">Home Server Power Pack 1</a> release was delayed as a lower priority (and understandably so at the time). </p> <p> <img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; margin: 5px 0px 10px 15px; border-right-width: 0px" height="132" alt="image" src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/WindowsHomeServerPowerPack1Doyouwantitno_846C/image_3.png" width="188" align="right" border="0"> Microsoft has recently announced that they plan to get the data corruption issue fix out to the market in June this year, but <a href="http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2980524&amp;SiteID=50" target="_blank">Home Server Product Manager Todd Headrick posted a query</a> on the Microsoft Home Server forums asking people if they'd like to get Power Pack 1 sooner, or if we'd prefer to wait for the corruption fix and take it all at once. </p> <p> I've voted for the "Power Pack now" option, and will be glad to take a data corruption fix later. As long as there's no dependencies on the bug fix (and it sounds like there's not), and as long as additional risk is not being generated, releasing the power pack earlier is certainly the best option, as long as it's ready. Here are a few reasons why: </p> <ul> <li> 64-bit client support, so users of Vista 64-bit can use the home server as it is meant to be used (this appears to be a broader-reaching and more-common issue than many thought it would) <li> Ability to back up the home server folders to external drives <li> Usability and UI improvements <li> Other fixes <li> Opportunity some good news into the channel (it's a great product with a lot of goodwill in the community that would benefit from some positive karma right now)</li> </ul> <p> As a general rule, big companies (or "enterprise" customers, as we call them) want multiple changes carefully packaged together, with as many problems solved in one patch or update as possible, with low risk. But Home Server is notably not an enterprise product. Instead it is laser focused on a crowd where more frequent feature and fix releases are preferred, encouraged and asked for. So, in the case of Home Server it's probably best to adopt something closer to an iterative release cycle. </p> <p> What do you think? <a href="http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2980524&amp;SiteID=50" target="_blank">Microsoft wants to know</a>! </p> <br /> <hr /> <font size="1">greghughes.net weblog - copyright 2009 - licensed under a <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">Creative Commons License</a>.</font> http://www.greghughes.net/rant/CommentView,guid,b3b7c0e7-504c-48cb-9c3c-6020e6851db0.aspx Home Servers Tech
http://www.greghughes.net/rant/Trackback.aspx?guid=fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6 http://www.greghughes.net/rant/pingback.aspx http://www.greghughes.net/rant/PermaLink,guid,fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6.aspx http://www.greghughes.net/rant/CommentView,guid,fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6.aspx http://www.greghughes.net/rant/SyndicationService.asmx/GetEntryCommentsRss?guid=fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6

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:



greghughes.net weblog - copyright 2009 - licensed under a Creative Commons License. MediaSmart Home Server 64-bit client coming soon http://www.greghughes.net/rant/PermaLink,guid,fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6.aspx http://www.greghughes.net/rant/MediaSmartHomeServer64bitClientComingSoon.aspx Fri, 04 Jan 2008 18:26:31 GMT <p> I <a href="http://www.greghughes.net/rant/HPWindowsHomeServerMyFirstCoupleOfDaysAQuickReview.aspx" target=_blank>wrote before</a> 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. </p> <p> 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. </p> <p> So - Thank you in advance, HP. The AV software from McAfee (note that Avast! <a href="http://www.avast.com/eng/download-windows-home-server-edition.html" target=_blank>also recently released</a> a AV package for WHS), enhanced media streaming and other features will be nice to take a look at, as well. Good deal! </p> <p> News and some detail can be found here: </p> <ul> <li> <a href="http://www.wegotserved.co.uk/2008/01/03/anti-virus-protection-enhanced-media-streaming-and-vista-x64-compatibility-coming-to-the-hp-mediasmart-server/">Anti-Virus Protection, Enhanced Media Streaming and Vista x64 Compatibility Coming to the HP MediaSmart Server</a> Jan 3, 2008 (link to wegotserved.co.uk) <li> <a href="http://www.wegotserved.co.uk/2007/10/04/the-windows-home-server-team-answer-your-questions-2/" target=_blank>The Windows Home Server Team Answer Your Questions!</a> October 4, 2007 (link to wegotserved.co.uk, contains background about the development process including the 64-bit client problems they encountered)</li> </ul> <br /> <hr /> <font size="1">greghughes.net weblog - copyright 2009 - licensed under a <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">Creative Commons License</a>.</font> http://www.greghughes.net/rant/CommentView,guid,fee4d5c8-3cd5-4b8b-96cb-49f3e75124c6.aspx Home Servers Tech
http://www.greghughes.net/rant/Trackback.aspx?guid=979f7514-14e9-40e4-9b9d-8c4fc2d542c4 http://www.greghughes.net/rant/pingback.aspx http://www.greghughes.net/rant/PermaLink,guid,979f7514-14e9-40e4-9b9d-8c4fc2d542c4.aspx http://www.greghughes.net/rant/CommentView,guid,979f7514-14e9-40e4-9b9d-8c4fc2d542c4.aspx http://www.greghughes.net/rant/SyndicationService.asmx/GetEntryCommentsRss?guid=979f7514-14e9-40e4-9b9d-8c4fc2d542c4 5

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.

HomeServer2 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.

HomeServer1 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.



greghughes.net weblog - copyright 2009 - licensed under a Creative Commons License. HP Windows Home Server - My first couple of days - A quick review http://www.greghughes.net/rant/PermaLink,guid,979f7514-14e9-40e4-9b9d-8c4fc2d542c4.aspx http://www.greghughes.net/rant/HPWindowsHomeServerMyFirstCoupleOfDaysAQuickReview.aspx Tue, 04 Dec 2007 22:56:27 GMT <blockquote> <p> <em><strong>UPDATE re CompUSA:</strong> I'm still not sure where the $150 price cut came from, but <a href="http://www.reuters.com/article/mergersNews/idUSN0734134020071208?sp=true" target=_blank>Reuters and everyone else is now reporting that CompUSA is being sold</a> 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...</em> </p> </blockquote> <p> I bit the bullet this past weekend and <a href="http://www.compusa.com/products/products.asp?in_dim_search=1&amp;N=201357" target=_blank>went online over at CompUSA.com</a> and found that a HP MediaSmart Server (the new <a href="http://www.homeserver.com" target=_blank>Windows Home Server</a> 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. </p> <p> <a href="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/WindowsHomeServerFirstcoupleofdaysArevie_BF31/HomeServer2_2.jpg"><img style="BORDER-TOP-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; MARGIN: 0px 0px 10px 15px; BORDER-RIGHT-WIDTH: 0px" height=184 alt=HomeServer2 src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/WindowsHomeServerFirstcoupleofdaysArevie_BF31/HomeServer2_thumb.jpg" width=244 align=right border=0></a> 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. </p> <p> 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. </p> <p> 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. </p> <p> 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. </p> <p> 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. </p> <p> 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. </p> <p> 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(<a href="/">\\servername\sharename</a>), 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. </p> <p> <a href="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/WindowsHomeServerFirstcoupleofdaysArevie_BF31/HomeServer1_2.jpg"><img style="BORDER-TOP-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; MARGIN: 0px 0px 10px 15px; BORDER-RIGHT-WIDTH: 0px" height=184 alt=HomeServer1 src="http://www.greghughes.net/rant/content/binary/WindowsLiveWriter/WindowsHomeServerFirstcoupleofdaysArevie_BF31/HomeServer1_thumb.jpg" width=244 align=right border=0></a> 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 <a href="http://www.hanselman.com/blog/HanselminutesPodcast71WindowsHomeServerInterviewWithCharlieKindel.aspx" target=_blank>great show, so you should go listen</a>), 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. </p> <p> 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, <a href="http://www.wegotserved.co.uk/windows-home-server-add-ins/" target=_blank>which you can check out here</a>. </p> <p> 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. </p> <br /> <hr /> <font size="1">greghughes.net weblog - copyright 2009 - licensed under a <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">Creative Commons License</a>.</font> http://www.greghughes.net/rant/CommentView,guid,979f7514-14e9-40e4-9b9d-8c4fc2d542c4.aspx Tech Home Servers