Great article over at Newsweek about the Lost Decade of Microsoft. I’m fully aware that Dan Lyons is Fake Steve, but that doesn’t change that fact that his insights are often right on the ball. I’ll also fully admit that I have no love for Microsoft – I appreciate that they bring competition to the industry, but honestly, over the last 5 years at least, if not longer, that competition has been limited and mouldy. This is a company that has been lacking direction, focus and ability to “wow” for far too long, riding on its coat-tails and existing product marketshare without innovating. To quote Dan Lyons:

Now, instead of being scary, Microsoft has become a bit of a joke. Yes, its Windows operating system still runs on more than 90 percent of PCs, and the Office application suite rules the desktop. But those are old markets. In new areas, Microsoft has stumbled.

The best thing that could happen to Microsoft at this point would be to replace Steve Ballmer with someone who actually understands the technology they’re trying to sell.

 

(We interrupt this regularly scheduled blog article with a reminder that Enterprise Systems Backup and Recovery: A Corporate Insurance Policy is currently on-sale with the publisher, CRC Press, as well as continuing to be available from such other fine online retailers as Amazon and others. Don’t forget – having enterprise class backup and recovery software is only just part of the equation in ensuring that you have a well running and reliable backup and recovery system. For comprehensive details about building that complete and reliable system, the book is an indispensable resource.)

So with October over, we’ve got some clear winners in the blog-article popularity stakes. Driven by search engine referrals we have a return to the top of the “Basics – Fixing NSR Peer information errors“. This is something that a constant turnover of visitors to the blog.

Here’s a thought: it’s time this should be addressed in the NetWorker Management Console. That’s right, instead of having NetWorker just log these warnings/errors, it would be handy if instead there was a section of NMC devoted to “intervention required” events … let’s see, that would probably fit most in the monitoring panel, and could even be reported under logging, with a double-click on the event to lead into a dialog box/session offering to delete the offending peer information if and only if the NetWorker administrator were certain that the host wasn’t being spoofed.

If you’re wondering why you need to fix these errors, it’s simple: they cause all sorts of issues when it comes time to recovery – either directly when trying to recover data for that client back onto that client, or as part of a directed recovery.

© 2012 The NetWorker Blog Suffusion theme by Sayontan Sinha