Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
The Military Communications Government Microsoft Security The Almighty Buck United States IT

The US Navy's Warfare Systems Command Just Paid Millions To Stay On Windows XP 192

itwbennett writes: The Navy relies on a number of legacy applications and programs that are reliant on legacy Windows products,' said Steven Davis, a spokesman for the Space and Naval Warfare Systems Command in San Diego. And that reliance on obsolete technology is costing taxpayers a pretty penny. The Space and Naval Warfare Systems Command, which runs the Navy's communications and information networks, signed a $9.1 million contract earlier this month for continued access to security patches for Windows XP, Office 2003, Exchange 2003 and Windows Server 2003.
This discussion has been archived. No new comments can be posted.

The US Navy's Warfare Systems Command Just Paid Millions To Stay On Windows XP

Comments Filter:
  • Not a bad price (Score:5, Insightful)

    by Anonymous Coward on Monday June 22, 2015 @11:32PM (#49967341)

    Is it just me, or does that not seem like that bad of a price?

    • Re:Not a bad price (Score:5, Interesting)

      by spongman ( 182339 ) on Tuesday June 23, 2015 @12:57AM (#49967675)

      it'll buy you nearly 1 hour of launches from an aircraft carrier.

    • Nope, if the contract runs it's full length it works out to $270/machine over the next two years.

    • by mveloso ( 325617 )

      $9m is cheap, and it might have been paid by EDS or whomever their IT contractor is now. The navy spends that much on ketchup every day.

  • Yeah (Score:5, Interesting)

    by Greyfox ( 87712 ) on Monday June 22, 2015 @11:34PM (#49967347) Homepage Journal
    They did that with OS/2 back in the day, too. They stayed on OS/2 1.2 a couple years past when the OS expired for everyone else. I guarantee you what they paid for this one was less expensive than changing all the documentation to reflect a later version of windows.
    • Uses DOS just to be safe.

    • by mjm1231 ( 751545 )

      I guarantee you what they paid for this one was less expensive than changing all the documentation to reflect a later version of windows.

      Except, they will still have to do this eventually, and now they are paying for both.

  • by Duckman5 ( 665208 ) on Monday June 22, 2015 @11:36PM (#49967355)
    Someone help me out here. I can understand why they would be running XP. It was a stable OS and it was used in a lot of embedded systems. They probably don't want to just replace the underlying operating system on a computer running a nuclear submarine or something.

    Office, though? What are they doing? Using a mail merge macro to address the nuclear missiles on said submarine? Why the heck can't they just replace that with minimal issues?

    At the end of the day, though, I'm not that worried. $9.1 million is a drop in the bucket compared to the nearly $700 billion [wikipedia.org] DoD budget. There's a whole lot more pork in that barrel to be worried about.

    • by Goetterdaemmerung ( 140496 ) on Monday June 22, 2015 @11:50PM (#49967431)

      Office 2003 is arguably still the best version of Office. I have co-workers who still use it and I've used pretty much every version since 4. I don't disagree with them, although I have personally transitioned to 2010 for compatibility. Newer versions don't provide much additional usability and make certain things more difficult such as removing the ability to select chart curves directly from the legend. Why??

      • Newer versions don't provide much additional usability and make certain things more difficult such as removing the ability to select chart curves directly from the legend. Why??

        Because for those people that need those new features, they are invaluable (note I don't use any of those features myself, but having been a part of a few migrations, with proper training courses for users, the end result was always positive). The people who complain tend to be the ones forced to figure it out themselves and so are frustrated with that, rather than the actual product.

      • by rtb61 ( 674572 )

        Now if the government is paying for the full cost of patching and bug fixes, why the fuck haven't they negotiated to release what citizens taxes have already paid for to the citizens that paid for it. Why does M$ get a role out a big ole fuck you to the citizens that paid for that work to be done.

      • Newer versions don't provide much additional usability and make certain things more difficult such as removing the ability to select chart curves directly from the legend.

        If that's your only complaint about newer versions of Office, you're a lucky, lucky man.

      • I use the most current version of Office (not by choice).

        If you know what you're doing, you can make it look and operate exactly the same as Office 2003.

    • by Mashiki ( 184564 )

      Office, though? What are they doing? Using a mail merge macro to address the nuclear missiles on said submarine? Why the heck can't they just replace that with minimal issues?

      I know of several government offices that still use Wordperfect 5.1 because it suits their needs perfectly for what they have to do, it would also be more expensive to change over, update all the documentation, and retrain everyone on a new system. Sometimes using something that's existing like that is far cheaper, not always but often enough. There's a realty office that I do work for and they're still using a 2.0 Novell NetWare machine, it does everything that it needs to do.

    • Ribbon hate?

    • by rikkards ( 98006 )

      We spent the last year doing the same thing and are down to about 400 XP machines out of 110,000. Why 2003? Here is why we didn't
      1. Too much inhouse custom crap on user machines to go through the testing cycle to make sure it worked with 2010. Which equals more money spent
      2. We are moving users to Windows 7 in a short time why go through Step 1 for practically no gain
      3. We have enough protection on the desktop and procedures to not worry about an infection spreading if a machine was hit. Essentially things

    • Bear in mind the recently decomissioned Space Shuttle still used DOS 3.1 for many systems
    • by tehcyder ( 746570 ) on Tuesday June 23, 2015 @09:09AM (#49969685) Journal

      What are they doing? Using a mail merge macro to address the nuclear missiles on said submarine?

      Jesus, Duckman, what part of "Top Secret" don't you understand?

  • by Anonymous Coward on Monday June 22, 2015 @11:36PM (#49967359)

    "That reliance on obsolete technology is costing the tax payers". Do you have any idea how much it would cost the tax payers to try to *replace* all that embedded technology? Far, far more than $9.1M. I really wish that people wouldn't post articles with such blatant biases and so little background research.

    The best thing that Microsoft could do for the world is put Windows 7 into perpetual maintenance and charge $50/year for the product. No more churn to replace hardware and software when they obsolete an old O/S. No more retraining costs to get IT personal who can manage the new O/S which does things just differently enough to trip people up.

    At least MS isn't as bad as Apple where the literally force you to buy new hardware along with the new O/S (Ipad 1 anyone?)

    • by OrangeTide ( 124937 ) on Monday June 22, 2015 @11:49PM (#49967427) Homepage Journal

      Maybe we shouldn't have bought the technology in the first place if we had no plan on how to effectively upgrade it.

      (I'm an embedded SW engineer)

    • by mlts ( 1038732 )

      MS would make money hand over fist by doing that. Look at OS/2. There is a company, EComStation still cranking out support and updates for Warp.

      The problem is that XPe and other embedded versions can't be upgraded. Try that, and millions of dollars worth of equipment will be rendered into scrap. One can treat XPe like a broken SCADA system and firewall/airgap the living hell out of it, but the best of all worlds is to have MS continue supporting it (for a decent fee) which is a win/win for all parties i

      • by vux984 ( 928602 ) on Tuesday June 23, 2015 @01:54AM (#49967851)

        The thing that irks me is that once various governments and organizations have "sucked-it-up" and ponied up the "ransom" to keep XP going -- why cant the public at large benefit from this. Especially given that we are the ones literally paying for it.

        Once the patches are written, tested, and released why aren't they available on Windows update?

        Don't get me wrong, I want XP to die in a fire. Cutting over to Vista onward, embracing 64 bit*, leaving the days of "administrator by default" behind, etc were all good things. But still if my government dropped 9 million bucks to get MS to develop some more security patches for XP; it'd be nice if the lathes at work could have them too.

        * (yes, yes, i know xp 64 bit existed. shut up. :)

        • by jaseuk ( 217780 )

          I'm sure Microsoft would be happy to negotiate that deal too. It'd probably cost more like $9 billion though.

          Jason.

    • by drkim ( 1559875 )

      The best thing that Microsoft could do for the world is put Windows 7 into perpetual maintenance

      That's sort of what they are doing with the free upgrade to Win10

    • Do you have any idea how much it would cost the tax payers to try to *replace* all that embedded technology?

      A lot less then trying to work around systems that cannot be maintained, let alone be repaired and are therefore utterly broken. Have you any idea how many security leaks their software must have? Even if they upgrade Windows for a few MegaBucks, all the libraries used inside the software remain unpatched. Heck, if somebody from China wants to be anonymous on-line, it is probably easier to do through the US Navy than through any Chinese server.

    • At least MS isn't as bad as Apple where the literally force you to buy new hardware along with the new O/S (Ipad 1 anyone?)

      You seem to be under the impression that backward and forward hardware compatibility are easy things:

      1) That an arbitrary OS could be expected to run well on hardware made many years in the past and many years in the future, and
      2) That arbitrary hardware can easily support ancient software.

      Suppose you'd said this about DOS. Microsoft should support it in perpetuity! OK, then, but where are you going to buy a mouse today that supports the hardware ports that DOS knows how to handle (or would you think mou

    • At least MS isn't as bad as Apple where the literally force you to buy new hardware along with the new O/S (Ipad 1 anyone?)

      A little harsh, there, don't you think? Apple's not literally forcing anyone to buy new hardware. My iPhone 3G (released in 2010, just like the first iPad) is working just fine, even though it's stuck at iOS 6. Pretty good for a 5-year-old consumer product. Do five-year old Android devices run Kit Kat? Any five-year-old Windows phones?

      The upcoming release of OS X, just like the current one, supports machines all the way back to 2007 (that's a core 2 duo machine with 1GB RAM).
      OTOH, my copy of Windows XP

    • At least MS isn't as bad as Apple where the literally force you to buy new hardware along with the new O/S (Ipad 1 anyone?)

      Huh? Your "all that embedded technology" comment likely refers to *old hardware* too. It's (likely) not that they're trying to continue to run XP on completely new hardware... They're trying to run it on whatever ancient hardware (including weird custom peripherals)...

      Which is JUST like keeping an original iPad running to run some old iOS app that doesn't run on the current OS on curr

  • Windows XP? (Score:4, Insightful)

    by dunkindave ( 1801608 ) on Monday June 22, 2015 @11:39PM (#49967379)
    Honestly, with the speed they develop and certify critical software in the military, I'm surprised some of these systems are up to Windows XP.
    • by Greyfox ( 87712 )
      Yeah, IBM would probably have continued to accept the large briefcases full of cash to support OS/2 1.2, and God knows no one would have the experience to hack that shit. But you know, EDS went all windows/citrix and they're (basically) the only guys willing to put up with the bullshit required to do Government contracts, so the Navy had to follow along.. Sure the path was rather bumpy, kind of like when the engine on the plane you're building in midair falls off and lands in a urban neighborhood, but they
      • 2008 IBM was banned from bidding on government contracts with the EPA, and it took until last year before we started seeing significant contracts come back in.

        One of which was to do Application Rationalization for SPAWAR, funny enough.

        http://www.federalnewsradio.co... [federalnewsradio.com]

  • by jpellino ( 202698 ) on Monday June 22, 2015 @11:39PM (#49967381)
    the XP version of Minesweeper. Apparently they get a lot of use out of that one.
  • by lytlebill ( 659903 ) on Monday June 22, 2015 @11:41PM (#49967397)

    'The US Navy paid $9.1M to insure that critical systems running an older OS are still supported while they continue to transition away from said older OS, a process that anyone with IT experience knows cannot happen overnight, and sometimes can take years, particularly when it comes to systems with potentially disastrous consequences at risk should you just slap updates on them willy-nilly.'

    I do realize that we're talking about post-Dice Slashdot here, but this is one of the lamer website shillings I've seen in a while. Honestly, the article itself isn't nearly as sensational as this clickbait summary would have you believe.

    • I'm out of mod points, but...

      <3
    • by Jack Griffin ( 3459907 ) on Tuesday June 23, 2015 @12:03AM (#49967475)
      You'll never believe what this Government did next!
      10 secrets the Military don't want you to know!
      This one simple trick made $9 Million!

      It's not funny, it's sad.
    • by funwithBSD ( 245349 ) on Tuesday June 23, 2015 @12:16AM (#49967521)

      I could say a lot about what happened at SPAWAR and why it is going the way it is going but I can't.

      I might say that there was no technical reason and it was all just internal politics, but I could not say that either.

    • The US Navy paid $9.1M to insure that critical systems running an older OS are still supported while they continue to transition away from said older OS, a process that anyone with IT experience knows cannot happen overnight, and sometimes can take years,

      It's not as if anyone knew years ago that XP would go EOL and a migration would be needed .... oh wait!

      More seriously, while this may represent a rational and cost effective solution in this instance, what about the future in which Microsoft will releas

    • Windows EOL dates are known way in advance. 10 years from the date of release. Sometimes they do extend it (they did with XP) but you can plan on a decade. That really is a good amount of time to plan on the lifecycle for your products. It is not too much to say "about once a decade we are going to make sure that our code is up to date and compatible with the current version of windows, and then transition to that". Were you to transition to 8.1, you'd have support until 2023.

      While critical systems certainl

      • by swb ( 14022 )

        Why follow Microsoft's arbitrary release cycle if you don't have to?

        The software they are using is just as functional now as the day it was installed (more so if you count bugfixes installed since) and the system integrations, testing and validation they have done are not inexpensive to repeat with a new operating system because Microsoft stopped supporting something, not because they had to -- but because they need to, to keep revenue flowing.

        It's not hard to imagine complex installation scenarios where th

    • xp was released in 2001. mainline support ended in 2009 and extended support ended over a year ago. sure, they need to insure critical systems stay online but they've known for the better part of a decade that this day was coming. it's maybe "only" nine million dollars, but it's a nine million dollar bandaid on an issue that they'll still need to address in the near future.

    • by Overzeetop ( 214511 ) on Tuesday June 23, 2015 @05:34AM (#49968489) Journal

      it's not a hammer, it's a manual nail insertion device designed to provide application of no less than 5000 ft-lb of energy to a drawn steel fasteneing device of up to 0.162" in diameter and 3.5" long with swaged or pressed impact points. The design must be such that operation is possible by users which fall within the 20th and 98th percentile for size based on standard American male growth charts for all races. The device shall require low skill level for operation. Item must be maintenance free with no adjustment required for initial or long term operation. All materials shall be sourced in accordance with OPM regulations and include a certificate of authenticity for all natural materials and a certification of chemical composition for all non-natural materials. Chemical composition may be provided by certificates of origin and testing by third parties at the source of material, or through destructive testing and analysis of the 0.1% of the fabricated product quantity per lot. Each lot shall be identified using ONLY the military item number (no commercial numbers or identification shall be allowed), be marked "U.S. Military Use Only", and carry the lot number. Identification shall be integrally cast, impressed, and/or indelibly marked on the item, or on each part of the item if the assembly is separable.

      • by bytesex ( 112972 )

        Oh god. Don't *do* that. The nightmares - they keep on coming back!

        • You know full well that's just the executive summary. The actual procurement spec is 143 pages long, excluding the appendices.

  • by nickweller ( 4108905 ) on Tuesday June 23, 2015 @01:53AM (#49967843)
    'Davis wouldn’t provide more details about the systems or their use, citing cybersecurity policy, but an unclassified Navy document says the Microsoft applications affect “critical command and control systems” on ships and land-based legacy systems. Affected systems are connected to NIPRnet, the U.S. government’s IP network for non-classified information, and SIPRnet, the network for classified information.'
  • Well, not secure from outside attack, you can defend against that by not putting it on a network... KISS

    Maybe everything after XP started phoning home to who knows what "area code" (206, NSA, KGB, unit 61398 [wikipedia.org]?)

    Doing things right, and doing things cheap are two different things.The presumption was that "COTS" was both... maybe not so much anymore. (BTW the spirit of COTS means OSS is fair game for scrutiny.)

    Quis custodiet ipsos custodes?
  • My tax dollars are paying for the updates. Why can't the government share them?

  • by Kythe ( 4779 ) on Tuesday June 23, 2015 @07:35AM (#49968965)
    The U.S. Office of Personnel Management continues its contract for Windows 3.1 support.
  • It looks like a sound decision to me. What's the current alternative? The fiasco known as Windows 8 and its attempted fix Windows 8.1? In the military documentation is critical. How much would it have cost to replace all of the Windows XP documentation?

    .
    imo, it was a good decision, ==provided== there will be an effort to start moving off of Windows XP and on to a more sustainable environment than Windows.

  • Finally the update from NT.
  • by kilodelta ( 843627 ) on Tuesday June 23, 2015 @08:02AM (#49969163) Homepage
    It isn't just the U.S. Navy, but the IRS and a bunch of other government offices that are still on XP for legacy reasons. Let's face it, Vista was an abortion from the get go, and Windows 8 wasn't much better. In fact every even numbered OS from Microsoft is horrid. Hence why business uses Windows 7 now.
  • by laughingskeptic ( 1004414 ) on Tuesday June 23, 2015 @10:00AM (#49970103)
    The Navy purchases computers as parts of much larger systems, often ships. These things get assembled and their expected lifetime is much longer that the technology cycles we enjoy outside of their domain. Refit schedules are not driven by the computers on board but rather by much larger, more expensive and longer lived components like diesel motors. The Navy is just in the last couple of years starting to move some of their onboard computer systems to what they refer to as "Carry On" components. There are probably ships in the fleet that have 25 year old electronics on them because these components weren't ever expected to be replaced.
  • The NMCI [navy.mil] was supposed to be a manageable intranet, with the Initiative back in 2000 the first step, identifying apps, updating systems, blah blah blah.

    Sort of got done. Sort of. The history of the NMCI [wikipedia.org] is a study in vendor management, high expectations, and bureaucracy.

  • Ah, yes, SPAWAR...

    Where wrinkly old generals sit around in a hot tub all day discussing their war plans.

    At least that was my first thought when I moved to San Diego years ago and first spotted the sign on the huge complex.

    Trivia: during WWI, the building they are housed in was an aircraft factory. The factory roof and nets covering adjacent Pacific Highway had painted scenery to fool an errant Japanese bombers.

    Millions of mom-and-pop businesses thank SPAWAR for enabling their old inventory system sitting in

Real programmers don't comment their code. It was hard to write, it should be hard to understand.

Working...