ROFL... You must be kidding.

I'll give Bing some credit, it does try to "decide" what I'm actually searching for. However, I hate to break it to M$, my brain is a much better decision engine. Part of the beauty of what Google gives you is that you know very quickly if you need to refine your search terms, which helps you actually use your brain and learn to think about what you are trying to find. So using Google I can quickly see that I need to refine my search question to give me better results, which almost always results in very relevant results. Bing tries to think for you, but in doing so doesn't actually help you find the best results. So instead of helping me figure out how to express my search better, Bing actually gave me fewer helpful results by limiting what it returned and returning things it thought I was trying to search for.

So no thank you Bing, I'd rather use the most powerful decision engine in existence, my brain.

Actually, that's accurate, at least fore Vista before SP1. I had a test Vista computer corrupt network files regularly before SP1. Of course after SP1 then networking worked better (still a pain in the 4$$ with their stupid wizards).

Agreed, steep learning curve, but the benefits are worth it.

My company analyzed Office 2007 briefly when it first came out, management decided to boycott it as long as possible. They were appalled at the total lack of anything familiar to them, which basically made doing basic daily tasks 3 times harder. So we're sticking with office 2003, the last good version of the Office suite. Perhaps Office 2009 will be better...? Unlikely.

Once OpenOffice 3.1 is rolled out I plan on making a case that we move to it, since Office 2003 licenses aren't going to be available forever.

According to my installation of Google Updater, it consumes a whopping 804KB of Physical memory, and 2.5MB of virtual memory.

So far it's working flawlessly, although I did change it to only notify me of updates instead of automatically updating. I do understand that they should make the updater more configurable (ie: removable), but c'mon it's a good first start.

For this exact reason I'm switching my Active Directory Group Policies to use wpkg in combination with OCS Inventory NG (or maybe GLPI, I'm just starting my research on migrating).

With WPKG you aren't constrained to MSI packages, you can distribute and manage ANY package. With the latest IE security flaw fiasco it got me looking at how to deploy Firefox. This seems to be the best way and should actually make my maintenance jobs much easier.