By Philip Churchill on February 04th, 2008
Microsoft Senior Product Manager Joel Sider talks Windows Home Server
The Computer Outlook Radio Talk Show host John Iasiuolo interviews Senior Product Manager Joel Sider about Windows Home Server. Joel discusses the basic purpose of Home Server, who it was built for, some of the Add-In applications available, such as tools that help you publish your own websites, to hosting your own blog, to performance apps like Diskeeper.
Joel wraps up the interview with info on where he expects to see the Home Server evolve in the future. If you have an hour to kill this podcast can give you a good overview of what Windows Home Server can offer you.
The podcast can be listened to online or as an MP3 download.
Share this WHS Article with Others:
Every since Jim left Microsoft, it’s been mostly FUD hype. Take for example Vista RTM, full of hardware driver failures. But what’s interesting here is how this happens, and continues to occur. I bet most of you don’t know that Vista RTM kernel was actually ditched to be replaced by Windows Server 2008 kernel in Vista SP1. But at the same time, Microsoft has not updated its Windows Vista Logo program to require drivers to be tested specifically against SP1.
So was Vista RTM kernel so bad, it couldn’t be fixed, or was Vista RTM kernel so bad it had to be replaced? You tell me…
Now we come to WHS, built upon Windows Server 2003, which Windows 2008 replaces 2003, but NOT in WHS. To make matter worse, WHS Drive Extender Technology is rumored to be the cause of all the data corruption. And yet, it too goes unresolved even as WHS Power Pack 1 is said to be even more than a service pack release. One can only wonder if this is meant to actually rebuild the system architecture of WHS RTM?
Spending more money isn’t the answer… Microsoft has gone a path in the wrong direction. Is it any wonder why Microsoft “Live Search” only holds about 9% of the market?
Even with HP’s help, WHS remains to be poorly adapted by the mainstream. It’s buggy, has data corruption issues and is basically “borrowing” third party solutions to appease the geeks, who basically should be using a real server. While the typical home server needs a more robust OEM solution that provides real streaming capabilities instead of focusing upon backup protection, which at this time isn’t able to even protect itself from data corruption.
Jim A. is really missed and not forgotten.