[toyg]

The only drawback of the current onslaught of Microsoft activity is the fact that most "enterprise" businesses and software products are completely unprepared or unwilling to move in step.

As an integrator, I've barely started seeing Win2012 in production last year, so it will be another 5 years before I can start playing with these new toys. Hell, some people are still chugging along with 2003sp2... and I'm talking Big Business, not some godforsaken countryside school.

[CrLf]

And one might argue they are taking the sane approach to the upgrade treadmill. It's easy to forget technology is supposed to solve real problems and that there's no economic incentive to use new toys to solve already solved problems, possibly introducing new issues with less well-known solutions.

The fact businesses are extending the life of systems not because they are unwilling to invest in upgrades but because they work just fine is a sign that the industry has reached a good level of maturity. It's a good thing. We should all be working collectively to solve new problems instead of reiterating over the same problems again and again.

In the old days of NT4 a 4-year old system would accumulate maintenance costs. Today, Windows 2003 is 13 years old and still pretty serviceable.

I'd be more worried about businesses accumulating unsustainable technical debt than accumulating old (but stable) technologies.

[illumin8]

Windows 2003 is end of support life and you aren't receiving security patches unless you're paying Microsoft a huge amount of money for extended support.

One might argue that it's insane to run a 13 year old OS that is not getting security updates any more at your business.

[CrLf]

Windows 2003 is EOL because Microsoft wants to push customers to the latest version. Customers have been pushing back at this for a while now, but Microsoft (and other vendors) makes more money selling the new shiny than extending their products' lifecycle.

In an ideal world, operating systems (server and desktop alike) would already be on a 5-year release cycle with just yearly incremental upgrades in between (as much as the vendor can manage in a service-pack model).

Is it insane to run systems without any security updates? Even within the lifecycle of the product many businesses never even patch after the initial install. I personally know people that live by this: never patch anything unless presented with proof that it's necessary to do so (I don't completely agree with this, but money has been lost catering for low-impact security updates and people tend to learn a few lessons from it).

Security is more about risk management than being free of vulnerabilities. The issue isn't going by without security updates, is doing so without assessing the risk.

[brazzledazzle]

Correct me if I'm wrong, but hasn't Microsoft introduced a lot of security features into the versions since 2003?

[poooogles]

>Today, Windows 2003 is 13 years old and still pretty serviceable.

Unless you're maintaining Server 2003 itself, at which point it comes with 13 years worth of problems.

[tammer]

Absolutely. I'm involved in systems design & IT strategy for a very large institution. By and large we've found literally zero advantages imparted to end users by Windows 10, besides being forced to deply it by MS deciding to early end-of-life Win7. Some cool features in Server 2016, but nothing that will affect a user's workflow in the slightest.

[duncans]

I was a bit of a Windows 7 stalwart until recently. I upgraded my parents' Vista machine to Windows 7 ... very sluggish. Thought I really needed to get them an SSD at some point. Then I upgraded it to Windows 10 on a whim - incredibly snappy. No need for SSD yet.

[tammer]

Sure, snappier on older hardware is a plus. But we've got a 4 year replacement cycle, and a slight increase in snappiness isn't what I'd call a major upgrade.

[CyberDildonics]

You dodged a $40 bullet there.

[toyg]

I absolutely agree! I guess my complaint is that MS is developing all this new stuff with no regards for the installed userbase -- they are all add-ons for Windows 10 and 2016 Server, rather than standalone cross-version apps that could be deployed sooner on existing infrastructure. It's obviously easier for them, but it means "normal people" will not be able to enjoy most of these advances for a very long time.

[userbinator]

Hell, some people are still chugging along with 2003sp2

I'd think this is for the same reason XP lasted so long --- it's a good stable platform free of all the hassles and complexities of the ones that came after it. A lot of home users are already quite disturbed by the privacy implications of Windows 10, and if anything big businesses would be even more cautious of the same for its server counterpart.

[untog]

I'd be interested to see a survey of home users with regards to privacy. I think a lot fewer care than we'd hope.

[Zekio]

and all of those home users are on Facebook already, so it probably doesn't matter.

[Sir_Substance]

Just because you're on facebook doesn't mean everyone is.

I'm one of an extremely large number of people who haven't made your mistakes. We tend not to bring it up because people like you go super-aggressive-defense and accuse us of being paranoid if we do.

Don't mistake our not bring it up for us not existing.

[Zekio]

Not on facebook.

[dijit]

By the same logic; I am a UK citizen, so it "probably" doesn't matter.

https://en.wikipedia.org/wiki/Tempora

[rubber_duck]

I don't see how this is a drawback. Maybe not 5 years but this stuff is still cutting edge, untested and unproven. Do you really want to use this kind of stuff in production when most of the issues haven't even been found yet let alone fixed ? No best practices, no other people mistakes to learn from ? Maybe tomorrow Microsoft decides it wasn't such a good idea and starts moving away from with (TBH they are better than most in this regard but still).

[pjmlp]

Still doing .NET 4.0 and Java 7 for production code here, exactly because of these type of issues.