I got an email from the Microsoft tech that I’d been working with on the Office problem. I’d told him how I solved the problem, and he asked where I found the registry entries that I’d changed to fix things. He also sent be a set of Knowledge Base links to various mnor problems that the Outlook checking tool had found.
Although the tech didn’t find the solution to my problem, I’d have to say that this is one of the better interactions I’ve had with Microsoft support in the past few years. Their web tool for keeping track of interactions is very good. The tech tried mostly reasonable things. He got back to me fairly quickly, and spent two hours trying to find out what was wrong. His supervisor called to make sure I was satisfied before they closed the ticket.
On the other hand, I’m not so happy with the developers at Microsft who are responsible for throwing a wide variety of errors into this one generic error message. It speaks of slapdash coding, and sure makes the users’ and support folks’ job a lot harder than it would be if Outlook gave a more specific indication of what the trouble is.
Leave a Reply