I don't speak numbers. I speak English. A bit of geek. And most nights I can figure things out. But I get really frustrated when error codes and diagnostic messages don't tell me what I'm supposed to do. It's no wonder that 'normal' folks are shutting off Windows update after patches that "break things" they don't understand, after WGA is shot down on their boxes without any communication ahead of time of what it's doing and any number of myraid things that they don't want to deal with. Technology should work... and one of the most annoying things about when it doesn't is that even us geeky folks get frustrated with it. And if we... okay ... if "I" get frustrated, it's no wonder others do too.
Just today in fact -- this was posted to the 2k3 newsgroup:
Is there a list of SBS2003 upgrades/patches - one that shows which ugrades
had problems and required patches?
The last upgrades installed - we let the automatic windows installer do it
and that messed up our computer. Cost us much time and money to undo it.
We are just learning this system and are uneasy about the upgrades. We know
they are critical, but we don't want to paralyze our system again.
I just checked online with Windows upgrade, and they are recommending 15
upgrades to our SBS2003. How do i know which ones won't be an issue?
Any advice is most welcome!
I hated to tell that poster that once he flips over to Microsoft Update he's got lots more patches to deal with.
Nick (who I had the pleasure of meeting with at SMBnation this year) had a great blog post about their patch process. That's a pretty cool way to deal with patch issues is to build your own knowledge base in a firm.
Have you thought about building a patch database for your clientele?