In November I flew to Sydney and in route, the Pilot checked a few things in the plane and then when we landed he explained that there was an indicator light malfunctioning and that as a standard procedure, firetrucks would be on the tarmac. We landed ahead of time, uneventfully. So it was interesting a week ago to get a letter from United saying “we apologize for your Emergency landing by sending you this travel voucher….” and I was like …uh.. exactly what emergency landing are you guys talking about?
So I see on the message boards that there are some folks reporting corruption on Windows Home Server, but per my eyeballs, it’s hard to do a headcount on the real bodies in there. And this post is in no way aimed to discount the issues. But at the same time… I think the Home Server folks blew it. They should have blogged more like Ed Bott’s post that reads… http://blogs.zdnet.com/Bott/?p=348
“This is not an issue that affects every Windows Home Server installation, and the symptoms require several factors that are not mentioned in the KB article. The largest contributing factor is when a home server is under extreme load. If you’re doing a large, highly demanding file copy operation in the background and you’re using one of the listed applications to edit a file that’s stored on a shared folder on the home server, and you save the edited file to the server, then you might see this bug…..
Meanwhile, backups stored on a Windows Home Server are completely safe, as are files copied to the server for safekeeping or streaming. This issue affects only files that are saved directly from one of the listed applications to a shared folder on a Windows Home Server.”
The reality is I see more people impacted by the IE6 patch bug with the December patches. http://blogs.technet.com/msrc/archive/2007/12/20/ms07-069-cumulative-security-update-for-internet-explorer-post-install-issue-automated-work-around.aspx
Step one in any emergency situation is to not overreact to the issue at hand. Stay calm.