I work as part of a technical support team. We work in a field where there are lots of early adopters. So when there’s a new Microsoft operating system released, we’re often asked when we’re going to deploy it everywhere. Suffice to say we’re never in a rush, and with good reason. Here’s an anecdote.
While working on a Vista install, a member of our team encountered the following error.
Need I say more? I’m not a Microsoft lover or hater, I’ve found all surviving OSes to serve their niche well. I know they’ll iron these things out later. We’d just rather wait for others to uncover the problems so that we can have a more seamless transition.
Microsoft
(No Ratings Yet)
Loading ...
10 responses so far ↓
1 Ian // Jun 6, 2007 at 10:51 pm
I was going to mention how in the scheme of things delaying doesn’t really matter because there will still be plenty of problems when it gets rolled out. I’ve been hearing rumours that (at least in other faculties) the rollout may happen as soon as this fall, although given the track record with regards to getting things done in time (*cough* BLS/WebCT *cough*), who knows…… but I see you caught it at the end with “more seamless.”
I was working at … uhh … another helpdesk on campus that shall remain nameless, but it receives more significantly more traffic than the FCS helpdesk, so maybe the same rules don’t apply. Officially we didn’t support Vista, or Office 2007 for that matter. Unfortunately everyone who bought a computer this year got stuck with them, so you have to unofficially support them. You can’t really leave them hanging.
In my opinion, the problem isn’t with Vista, and as much as I hate to say it, it’s not even with Microsoft. The problem is with lazy and bad developers. Vista was only in beta for *forever*, and major vendors like Cisco and McAfee *still* couldn’t get functional builds out for it in time… and those are ‘good’ developers, to say nothing of the people who assume their app will run with admin privileges and drop files all over the disk instead of using %TMP%, %HOMEPATH% etc… to say nothing of legacy applications like Banner, which does strange and horrible things under Vista (forces browser out of Aero, crashes randomly…)
It’s frustrating.
2 Markk // Jun 6, 2007 at 11:38 pm
Ahh, the dreaded Red X errors! And while many errors may not be Microsoft’s fault but that of other developers, Microsoft gets all the blame. Poor things
3 MMSS // Jun 7, 2007 at 10:12 am
Maybe the Error was so Severe that the Red X didn’t want to say what it was?
4 Marc // Jun 7, 2007 at 6:04 pm
Well I appreciate the extra information. i had no idea that was a developer issue and not a Microsoft issue.
We are also supporting people as best we can. We’re just dodging the major bullet of mass deployment within our lab environments.
5 Dean // Jun 8, 2007 at 7:58 am
This one just happens to be an Adobe Acrobat error. So not Microsoft’s fault necessarily.
6 Marc // Jun 8, 2007 at 10:38 am
Boo Adobe!!!
7 mike // Jun 8, 2007 at 9:34 pm
Some errors are too severe for a common language like English. Had your speakers been on at the time, you would have heard the sheer anguish of the O/S expressed through song.
Most likely some emo-rock/punk.
8 Marc // Jun 8, 2007 at 9:43 pm
I would have loved to hear that sound. unfortunately the speakers were off at the time. We’ll have to try and reproduce that one so we can record the sound and share with all
9 Tabletop Baseball // Jun 10, 2007 at 12:46 pm
How do you know that is an Adobe error?
10 Marc // Jun 10, 2007 at 4:16 pm
Dean was involved in the install. That’s how he knows