Slashdot Mirror


Failed Win XP Upgrade Wipes Out UK Government Agency

Lurker McLurker writes "The BBC and the Register report that the UK Government's Department for Work and Pensions attempted to upgrade seven PCs from Windows 2000 to Windows XP, and ended up with BSODs on over 60,000 machines. I wonder if the National Health Service is regretting awarding Microsoft a £500 million contract now." The Guardian also has a good story.

28 of 731 comments (clear)

  1. The reason for the upgrade by Anonymous Coward · · Score: 5, Funny

    They wanted that new version of Internet Explorer with the fancy built-in pop-up blocker.

    1. Re:The reason for the upgrade by phaln · · Score: 5, Funny

      In other news, productivity is UP 64% since the day before the crash!

      --
      SNACKS ARE AWESOME
    2. Re:The reason for the upgrade by Lev13than · · Score: 5, Insightful

      They wanted that new version of Internet Explorer with the fancy built-in pop-up blocker.
      Looks like they got a deal; they got the version that also blocks viruses, worms, and abuse of Solitaire! ;)

      Writing article about Free iPod. Please help out.


      They probably wanted to block assholes who disguise 'Free iPod' links in the sigs. 'TinyUrl' my ass. If you want an iPod, ask your parents to raise your allowance. Otherwise, I heartily encourage you to fuck off.

      --
      When you have nothing left to burn you must set yourself on fire
    3. Re:The reason for the upgrade by skids · · Score: 5, Insightful

      OK, fair enough. A lot of the people I worked with when I was in a government position do deserve that.

      But a lot of them don't. I would say most state employees work their asses off doing pointless things, rather than screwing off. The problem is more with upper management than with the rank and file... though the problem does bleed over into the lower level employees because, after all, how long can you pour your energy into a task that you know only is neccesary because incompetent managers fail to streamline the operation and give you more real, productive work, before you start to take the job much less seriously?

      So those petty state officials who shirk work do so as much due to being beat down, disillusioned, and tapped out as far as trying to do something about it in the face of a "front row" that doesn't like to listen to comments from their inferiors.

      When I was working for the state, I considered myself very lucky to be involved in a project that was doing something meaningful, being productive and, while mistakes were made here and there, was relatively efficient overall. I could see how this was not the case in the departments working beside ours.

      Eventually, though, the egos of the upper echelon managed to intrude even into our well defended (by caring managers) little island of fortitude and competance, and I had to say screw it. Now, unlike most of the rest of my friends that got laid off and sucked the government unemployement insurance tit, I am fending for myself with the money I saved by not buying useless crap.

      So when people try to say I was overpayed at 60% of my fair private-industry salary, I don't shirk from the criticism. Yeah, the benefits were better than the private sector and the environment more permissive, but at least I didn't go looking for a handout like others so they could keep up the credit card payments for their DVD collections and car loan for their gas guzzling S.U.V.

      At least I, one of those loathsome, lazy, state workers, had the good conscience not to apply my talents to better the carreer of a gaggle of idiots who aren't overseen adequately by the legislature that created their positions. If you want the state sector fixed, aim at the top. The clock punchers at the bottom are just a symptom of a management that preserves itself by not giving their underlings enough of a reason to revolt.

  2. Uh-oh... by Dynamoo · · Score: 5, Interesting
    You know that sinking feeling when you've just pressed the wrong button...

    ..of course, it seems to be our friends EDS behind it, who are just great at making a mess of government contracts.. and then, the government just gives them another one.

    --
    Never email donotemail@WeAreSpammers.com
  3. This is typical of our government. by bairy · · Score: 5, Insightful
    If something is actually working right (and it's rare), change it!
    I can imagine it now
    Intern: "Sir, Microsoft have bought out Windows XP Service Pack 2. It's had numerous bug reports of dying pcs and software not working anymore. THIS is the time to upgrade to Windows XP, then upgrade to SP2 because windowsupdate won't stop bugging the hell out of us until we do!"
    Boss: "You mean we could cock something up, and it might not even be our fault for a change?! Lets pay someone vast amounts of money to do it!"

    The Gaurdian reports it was a week long outage. Now, I may be completely wrong here, but surely all they had to do was restore those pcs back to their previous Windows 2000 state using the daily backups they do... I mean, it's only common sense to do backups on such a critical syst...oh, wait, nevermind.

    </cynical>

    --


    Get paid to search..It's geniune and
    1. Re:This is typical of our government. by blowdart · · Score: 5, Interesting

      Only theregister appears to talk about Win2k and XP, so lets see what they're saying.

      According to one, a limited network upgrade from Windows 2000 to Windows XP was taking place, but instead of this taking place on only a small number of the target machines, all the clients connected to the network received a partial, but fatal, 'upgrade.'

      So if this is true then EDS pushed out a partial upgrade. Now come on, if you installed 75% of a new distro over an old one then rebooted would you blame Redhat because it didn't work?

      Or there's the other version

      DWP was trialing Windows XP on a small number ("about seven") of machines. "EDS were going to apply a patch to these, unfortunately the request was made to apply it live and it was rolled out across the estate, which hit around 80 per cent of the Win2k desktops.

      So again EDS pushed out XP patches, overwriting Win2k files and the machines crashed

      Not really surprising if you overwrite parts of an OS with files from a different OS that there is a mass crash, but folks, this is an EDS fuckup not really a problem with Windows.

      Of course theregister could be wrong. It might happen. Heh.

  4. EDS again by Hieronymus+Howard · · Score: 5, Informative

    Every time I hear about a big government IT fuck-up it seems to be caused by EDS. Yet the government keep awarding them contracts. Why?

    1. Re:EDS again by I+confirm+I'm+not+a · · Score: 5, Interesting

      Yet the government keep awarding them [EDS] contracts. Why?

      I don't know, but I do recall an article about IBM refusing to tender for UK.gov contracts: apparently it was too costly, and too risky - you could spend millions only to not get the tender, and IBM felt that the chance of getting the tender awarded to IBM was too small. So... I'd suggest either it's too costly to play so players are dropping out (the reasonably answer), or someone in government really loves EDS, and IBM know it (the tinfoil hat answer).

      Living in the UK, I'm minded to go for option 2.

      --
      This is where the serious fun begins.
  5. Come on now by Mick+Ohrberg · · Score: 5, Insightful

    Incompentent admins can turn any minor upgrade to a catastrophic failure. Don't blame M$ for this one unless there are irrefutable proof that the admins did everything by the numbers.

    --

    Quidquid latine dictum sit, altum sonatur.

  6. EDS now stands for... by BlackHawk-666 · · Score: 5, Funny

    Every Desktop Shutdown.

    --
    All those moments will be lost in time, like tears in rain.
  7. Nooo! by Turn-X+Alphonse · · Score: 5, Funny

    It's like a thousand solitaire players suddenly cried out in frustration and then silence...

    --
    I like muppets.
  8. Not a nail for Microsoft. by alistair · · Score: 5, Interesting

    "On another note, How did upgrading seven machines to XP BSOD 60000"

    If you read the register article, it says that they were attempting to only push the update out to 7 PCs, but it actually went to all 60,000.

    I would imagine they were using something like Microsofts SMS services or Bigfix to push out packages, and simply selected push out to all instead of a test community.

    I don't think this is a nail in Microsofts coffin, I have seen similar things happen in the mainframe world where patches intended for dev hit live production systems with similar bad consequences. It has to count as a bad day at the office for the person pushing the button though.

    It also highlights the difficulty in pushing out big updates to major networks of PCs, be they running Windows or Linux. The complexity of moving from Win NT to XP has proved so complex in my organisation that for the future Longhorn upgarde and beyond we are now looking to Citrix to allow the migrations of applications across servers and essentially use the PC as a thin client for all but core office and email apps.

    1. Re:Not a nail for Microsoft. by ilyaa1 · · Score: 5, Insightful

      OK, so let's see. Someone installs WinXP dll's on Win2K machines. Hmm, I wonder, how come those don't boot now?..

      It's true that Microsoft's robustness is rather mirage-like, but there's a thing called human error, and that can bring down any system. All the software did was follow human instructions, after all: that's why we need IT people with brains to decide who is doing what.

      However, PXE boot and a server with HDD images ready would've been helpful...

  9. Avoidable blunder by Waffle+Iron · · Score: 5, Funny

    Obviously these sysadmins were incompetent. Everybody knows that a BSOD is impossible under Windows XP. If they had simply upgraded the other 60,000 machines to XP first, and then updated these 7 problem systems, this whole problem would easily have been avoided.

  10. Re:Too slow. by Apathetic1 · · Score: 5, Insightful

    It was EDS that screwed it up. I can't say I'm surprised. For once I find it hard to blame Microsoft - rolling an XP patch out onto a Windows 2000 machine (or 60000) will have the predictable effect of hosing the system. Given what I know about EDS (I worked there for two summers) I don't think running Linux would have helped.

    --

    My username does not make me Apathetic. It's irony, get it?

  11. Wrong! by Mr_Silver · · Score: 5, Informative
    Bad Slashdot reporting again? Quote Slashdot:

    the UK Government's Department for Work and Pensions attempted to upgrade seven PCs from Windows 2000 to Windows XP, and ended up with BSODs on over 60,000 machines.

    In actual fact, the Register quotes:

    According to one, a limited network upgrade from Windows 2000 to Windows XP was taking place, but instead of this taking place on only a small number of the target machines, all the clients connected to the network received a partial, but fatal, 'upgrade.'

    and then below it:

    Another source says that the DWP was trialing Windows XP on a small number ("about seven") of machines. "EDS were going to apply a patch to these, unfortunately the request was made to apply it live and it was rolled out across the estate, which hit around 80 per cent of the Win2k desktops.

    So, by merging them you get the following story:

    There was a trial of seven PC's, instead of patching only those seven, the request to roll it out was accidently performed and every computer attempted to install a botched version of XP.

    Somewhat slightly different to the Slashdot version wouldn't you say?

    In addition, I'm pretty sure that if you accidently deployed a botched version of the linux kernel then it too would probably have a similar effect.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  12. The funniest thing.. by WindSword · · Score: 5, Funny

    was the government spokesperson. After the intro to this piece on Radio 4 this morning, her opening sentence was "Let me correct you, 20% of our workstations are functioning". Talk about a positive spin.

  13. Re:Too slow. by Zocalo · · Score: 5, Insightful
    Actually, I tend to see this as potentially an opportunity for Microsoft to gain some excellent, and totally undeserved, *good* PR. The root cause of the problem seems to be that EDS erroneously pushed a Windows XP update out to Windows 2K desktops - hardly Microsoft's fault. Having got completely out of their depth (which isn't especially far out of the shallows given EDS' track record to date) EDS decided that it couldn't fix the problem and called in Microsoft.

    Now, assume Microsoft bails EDS out, and there is no reason why not, because you can bet they'll send a bunch of temps to every DWP office at EDS' expense if they have too. In a nutshell, Microsoft gets a PR coup: "We've just bailed out out a leading *cough* solution provider! Now imagine that had been, say, a Linux deployment... Who could EDS have called then?" Given the excellent grasp of PR, spin and FUD Microsoft has, I don't think this is going to help break the Microsoft stranglehold at all.

    --
    UNIX? They're not even circumcised! Savages!
  14. We need to educate the decision makers by mishmash · · Score: 5, Informative
    We've got to stop this happening again, we've got to educate the people spending our money on huge computer systems which are prone to failure.

    I have found that many MPs when questioned on anything related to technology simply say that "it is a complex issue", which to me isn't good enough when such huge amounts of money and significant impact on people's lives is involved.

    There is a huge contract that'll be up for grabbs soon - EDS are preparing themselves to manage the UK national identity database and identity card scheme. This is one we could lobby our representatives on to ensure they do it right..

    Where to have the debate where it might be read by those who mater:
    Free service to fax your MP

    Boris
    Richard Allan
    Tom Watson
    Shaun Woodward
    Citing the recent and ongoing failures such as that cited in the article, and the UK Child support agency's computer failure. as well as the NHS computer system UK

    1. Re:We need to educate the decision makers by mikerich · · Score: 5, Funny
      There is a huge contract that'll be up for grabbs soon - EDS are preparing themselves to manage the UK national identity database and identity card scheme. This is one we could lobby our representatives on to ensure they do it right..

      No, no, no, this is the one we lobby them to employ EDS and Microsoft on!

      If MPs are stupid enough to implement Blunkettcards we should at least get some entertainment out of it.

      Best wishes,
      Mike.

    2. Re:We need to educate the decision makers by mikerich · · Score: 5, Informative
      Where to have the debate where it might be read by those who mater:
      Free service to fax your MP

      Can I take the opportunity to point out that faxyourmp is for UK citizens ONLY and should only be used to fax your own MP. It is not for international write-ins or mass lobbying.

      Best wishes,
      Mike.

  15. Re:Hope they all loose their jobs tomorrow by 0123456 · · Score: 5, Insightful

    "What happened to all the competent people??"

    They emigrated, most likely. One of the problems with incompetence is that it's self-reinforcing, the competent get more and more fed up with having to deal with incompetence all day and find something better to do with their time.

  16. Re:TCO costs rise scarily with Windows XP failures by speed-sf · · Score: 5, Interesting

    Something that makes me curious, you hear Ballmer lament about the lower TCO of windows. You hear the linux community shriek about it's lower TCO. The bottom line is really this, if your sysAdmins are less than competent and bugger up something like this which system would have a lower cost to recover? This is a really good thing to know when you are considering any enterprise system. Call it, TCCR (total cost of catastrophic recovery). Ballmer, Linux communities answer me this!

    --
    All your database are belong to us
  17. Member of Parliament by dominux · · Score: 5, Funny

    you can call them senators if it makes you feel better.

  18. Perhaps I'm just missing something here.... by emrysk · · Score: 5, Insightful

    ...but is there any actual evidence is was a Microsoft error? I like bashing Windows as much as the next guy, but it seems this is at least as likely to be a huge fumble by the admins.

  19. Re:TCO costs rise scarily with Windows XP failures by malkavian · · Score: 5, Insightful

    They're probably using something like Novadigms's Radia. And instead of linking the correct 7 PCs, they linked to all of them (misconfigured group). In that case, it's not a case if installing a patch that is installed using the new mechanisms, the "Patch Manager" simply dumps the files to all the machines that connect up using it's client, and force an overwrite.

    Given, they should actually have an install script that checks the OS before it actually dumps the install package on there, but hey.

    Not normally an MS apologist, but this isn't really Microsoft's problem. It's the contracted company that made the update package failing to ascribe it to the right download group.

    So, the analogy. It's like some perfectly good system being installed, and someone presses the button marked 'open all doors' instead of simply open door 7.
    I don't see anyone really blaming the door manufacturer here (Microsoft or the contractors), although I'd hazard a guess that the person who skipped over the part of the process that said 'double check the groups you assign this patch to' will be sorely chastised...

  20. Re:TCO costs rise scarily with Windows XP failures by mikechant · · Score: 5, Insightful

    The public sector in the UK is nothing more than unemployment benefit for the middle classes.

    In my experience (having worked for both) in terms of inefficieny and stupidity, there's only one thing worse than the British Public sector and that's the British Private sector.
    My company used to be part of a large public sector concern and was sold off. Since then we seem to spend nearly of our time/money:

    Changing company logo and name every 6-12 months
    Adding a new problem management system which we have to learn every 6 months (we currently have about 5 each of which was supposed to replace all the others).
    Paying huge bonuses to upper managent.
    Paying huge car allowances to middle management including those who refuse to drive.
    Not giving any rises under the so-called performance related pay scheme for 4 years despite meeting profit targets because all the money has gone on the above 2 items.
    Making skilled people redundant then recruiting at vast expense people with the same skills 2 months later.
    Making skilled people redundant then reemploying them at twice the pay as contractors for the next 2 years because they're still needed.
    Repeatedly shuffling kit from datacenter to datacenter around the country at vast expense and disruption to our customers.
    Ordering expensive buffets for management meetings , 95%+ of which get thrown away.
    Managers having a schedule involving meetings all over the country which means that they spend about 25 hours out of 40 driving.
    Managers refusing to use video-conferencing for meetings even in the light of the above.

    How many of these things happened when I was in the public sector? Virtually none. We didn't have the money to throw around on such things. We were forced to be efficient.

    Also if this private sector company I'm referring to was atypically inefficient, presumably it would do so badly it would collapse or be taken over. So this implies that many private sector companies are like this.

    It's very easy to slag off the public sector if you use stereotypes, generalizations and distortions.