5 ms·
Microsoft’s upgrade cycles for Windows 10 are a big problem for many companies. Many places deferred PC upgrade cycles for 6-10 years because they didn’t need t
by Spooky23 7y ago
Microsoft’s upgrade cycles for Windows 10 are a big problem for many companies. Many places deferred PC upgrade cycles for 6-10 years because they didn’t need them.
Now they are stuck with an accelerated upgrade cycle and big capex.
With respect to other subscriptions, I think that you’ll see pushback. Adobe and Microsoft play hardball, which gets old quick.
- jklehm 7y agoI don't follow, Win10 runs on a 9 year old pc for me without issue?
- hermitdev 7y agoI think it's more of a will this update cripple our 20yr old in house developed app that is crucial for the business that either we don't know how to maintain or lost the source no longer working on the latest windows. Previous employer, we were on WinXP and compiling a/ VS2003. Upgrade to Win7 mostly effectively crippled VS2003 for reasons I don't know. This necessitated porting our very large (100s of Millions of LOC in C++ to at least VS2008) set of in-house libraries. It should on paper be trivial, but it was a firm wide effort that spanned 18 months. Why? Because someone sent the CEO an xlsx that he couldn't open. This was circa 2007-2008. We were forced to upgrade OS and compiler for the new Office version, but it trickled into a firm wide rebuild of all C++ code. Wasnt pretty or fun.
- vbezhenar 7y agoLTSB edition is supposed to fix that. Unfortunately their licensing for LTSB is strange and not friendly...
- Spooky23 7y agoIf LTS[B/C] is the answer, you’re usually asking the wrong question.
- wongarsu 7y agoThat would likely turn the 18 month upgrade effort into a 36 month upgrade effort that happens 5 years later. Sometimes long upgrade cycles are great, but I suspect a yearly upgrade to the latest Visual Studio would have been a lot less painful. Fixing a few small issues is much easier than fixing many of them, and having to do it yearly both makes everyone better at doing it and better at avoiding the creation of such issues.
- agumonkey 7y agoManically laughing at the wonderful logic of the universe. Much laryngeal nerve.
- Spooky23 7y agoIt’s not supported and isn’t reliable enough to be cost effective. Microsoft barely supports what they claim to support, its bad advice to do this unless you have no options at all. Being accountable for upgrading about 250k devices, we found that 3-5% of devices with questionable support status failed, as compared to near zero for supported devices. That 3-5% is unpredictable and expensive to address. You also have to remember that Windows 10 isn’t a thing, it’s a lifestyle. Windows 10 1803 went EOL last week, and there are devices that worked with 1803 that won’t work with new builds.
- zamadatix 7y agoUpgrading Windows 10 regularly is an operational burden not a capital burden.
- alexanderdmitri 7y agoIt's definitely a security issue in the sense they've explicitly reserved the right to change and redefine the data they collect from Windows 10 machines with each update while reserving the right to not state what data they're syphoning at any one point.
- no_wizard 7y agoI’ve never understood why modern businesses have these deployment issues. Maybe it’s the nature of where I work but we are always on the latest windows 10 version and we keep it that way quite aggressively without issues
- el_dev_hell 7y agoI worked for a fortune 500 manufacturing company not long ago (2-3 years). Their main ERP was running on an AS400 mainframe and multiple pseudo-linked applications that were recently (4 years ago) updated to run on Windows 7 (which took 7 years to complete). > I’ve never understood why modern businesses have these deployment issues. Not every business is a tech-first company. Plenty of huge companies have legacy systems in place that can't be pushed to Windows 10 with a simple update.