Linked by Eugenia Loli on Thu 12th Jan 2006 07:36 UTC, submitted by Resolution
Permalink for comment 85274
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-01-02
I bet this is because they rushed this patch out the door and they were understaffed due to the holidays. People were probably camping in the microsoft offices getting the test matrix run and some Program Manager on too little sleep made a bad decision. If you have a true high-uptime Windows System, it has to be clustered (that's basically the way Microsoft expects you to maintain high-availability), so this shouldn't hit those people.
This definitely seems like it has happened and is pretty bad.