Desktop platforms Toolkit
Story: Microsoft upgrade knocks out 80,000 government PCs
Posted by: Anonymous (Tuesday 30 November 2004, 3:26 PM)
Basic tenet of change management, apart from testing on a subset, is that the change should be capable of being backed out if it fails. Even ITIL change/release management doesn't mention this fact. At least, the version I've been looking at doesn't.
Full Talkback thread
Story: Microsoft upgrade knocks out 80,000 government PCs
-
Sorry but this is unacceptable and as a cockup eve... NJ -
Microsoft causing PCs to crash unknowingly. How i... Anonymous
-
Blame the driver (EDS) and not the car (MS)
MS NOT... Anonymous
-
the point is that MS software shouldn't just... alie -
Well, there aren't really enough details... Anonymous -
"the point is that MS software shouldn't just fall... Alaric
-
I find it interesting EDS is involved.
I'm no fan... Anonymous
-
Didn't they test the upgrade first!!! Anonymous
-
Why didn't they do a programmed upgrade to ba... Anonymous
-
Basic tenet of change management, apart from testi... Anonymous -
If it's EDS why was there a surprise that the impl... Stephen P. Goodman
-
To Quote . . ."If it's EDS why was there a su... Anonymous
-
This was an EDS error, MS are not at fau... Anonymous
-
I have a feeling that the problem here lies with E... Steve Atherton
-
The real problem is that just about everyone consi... Arthur B.
-
Get the Fact's ???
As long we don't know the... Egmond MAringka
