Point taken, however, note that one of the (many?) problems with SP3 was with one of M$ own programs. You would think they would at
least check that. This is not a hardware issue. M$ should have have control over all their own programs.
I have an idea for M$ "quality checking" for the next update. (I am trying to be serious here). Send the update to all the
different divisions that have software that is supposed to work with the update and have them see if it does work. If not, then
don't send the update out to customers.
It makes you wonder if they checked anything.
----- Original Message -----
From: "Rick Schummer" <profox .AT. whitelightcomputing .DOT com>
To: <profox@leafe.com>
Sent: Wednesday, April 30, 2008 10:50 AM
Subject: RE: [NF] XP Service Pack 3 is out.
>> Also, I'd kind of like to test the thing on one station before it gets updated on all of 'em.
Is that not Microsoft's job. I thought that is why they have alpha and beta
testers to test the update so it does (not) mess up your machines, or is it M$
machine?<<
Hi Mike,
I know you are sort of a rookie in this business, so come talk to me about deployment when you have
installs going out to 10's of millions of machines with different hardware and software configured
(all of it out of your control). You certainly can write your own ticket anywhere when it goes
perfect on all of them. <g>
This is why the professionals take on the testing responsibilities in-house before they allow it to
roll out to their entire infrastructure.
Rick
White Light Computing, Inc.
www.whitelightcomputing.com
www.swfox.net
www.rickschummer.com
[excessive quoting removed by server]
©2008 kam |
