Microsoft has failed to explain to corporate customers the repercussions of its twice-a-year schedule to deliver Windows 10 upgrades in March and September.<\/b>
\nMicrosoft has failed to explain to corporate customers the repercussions of the twice-a-year schedule that will deliver Windows 10 upgrades each March and September, an analyst argued today.
There are too many uncertainties about the upgrade schedule, a critical part of Microsoft’s \u00ab\u00a0Windows as a service\u00a0\u00bb model, said Michael Cherry, analyst with Directions on Microsoft.
\u00ab\u00a0Customers shouldn’t have to figure this out, \u00a0\u00bb Cherry said, referring to unanswered questions he had after participating in an online \u00ab\u00a0Ask Me Anything\u00a0\u00bb-style discussion that Microsoft hosted two weeks ago. \u00ab\u00a0We shouldn’t even be having this conversation about, ‘Maybe they mean this, or maybe they mean that.’ They should have told us, ‘Here’s how it works, here’s the documentation, here’s the TechNet article, here’s everything.'\u00a0\u00bb
Cherry aimed his criticism at Microsoft’s announcement last month that Windows 10 feature upgrades would release each March and September, and that each upgrade would be supported for 18 months.
His first complaint was that Microsoft presented the new setup as a done deal that customers — including enterprises that want consistency — could bank on. But the company has not yet demonstrated it can hit an every-six-month schedule; the three upgrades released thus far came at intervals of 4 months, 7 months and 11 months.
Cherry questioned the company’s ability to fulfill its promise. \u00ab\u00a0We need to see consistency that they’re able to accomplish this, \u00a0\u00bb he cautioned. \u00ab\u00a0For now I say that this is aspirational, not policy. They hope to do this [every March and September] . But if they don’t, they don’t. If it’s June, it’s June. Or April.\u00a0\u00bb
The problem is that if Microsoft doesn’t make a deadline, the delay would have a domino effect. \u00ab\u00a0What happens if they slip too far?\u00a0\u00bb Cherry asked. \u00ab\u00a0If Microsoft misses [a release] by six months, then they’ve knocked six months off the time before you have to upgrade to the next.\u00a0\u00bb
Microsoft has said nothing about what it would do in such a case. And that’s a problem, said Cherry. If Microsoft pushes back the following releases, for example, the March-and-September cadence collapses. But if Microsoft simply resumes the tempo with the next slated release, the delay either eats into a version’s support lifetime or throws off the schedule.
One likely consequence? Microsoft’s promise that customers will be able to skip a Windows 10 features upgrade may be in deep trouble.
Under ideal conditions, enterprises have only a two-month migration window if they pass an intervening upgrade. Any delay in the schedule would make upgrade skipping impossible, forcing businesses to deal with each refresh, something Cherry predicted would happen.
In fact, businesses don’t really get a full 18 months out of any one Windows 10 version. The first four of the 18 is, and will continue to be, designated as relatively unpolished, fit for consumers — who act as Microsoft’s unpaid testers — but not for corporate use. Only after Microsoft promotes the version as suitable for widespread company deployment by marking it as \u00ab\u00a0Current Branch for Business, \u00a0\u00bb or starting this fall, as \u00ab\u00a0Semi-Annual Channel (Broad) , \u00a0\u00bb are enterprises to roll it out to workers. So the maximum amount of support to businesses for a given version: 14 months.
Even companies that jump on the uneven code — what Microsoft now calls \u00ab\u00a0Current Branch\u00a0\u00bb but will rename \u00ab\u00a0Semi-Annual Channel (Pilot) in September — may not get 18 months on a release.
\u00ab\u00a0Microsoft told us, ‘Don’t install it yet, ‘\u00a0\u00bb Cherry said of version 1703, the feature upgrade that launched April 11. He was referring to Microsoft’s message, actually aimed at consumers, that they wait for Microsoft to offer the refresh rather than grabbing it immediately. Microsoft delivers feature upgrades in stages, first to a small set of users whose systems will have the greatest chance of successfully completing the upgrade. The company expands the upgrade pool as it fixes problems reported by others until it opens the throttle.
Last year it took three months to ship 2016’s one upgrade to more than 80% of those running Windows 10, meaning that many had 15 or fewer months of support.
\u00ab\u00a0The 18-month count-down starts on the first day, \u00a0\u00bb Cherry said about an upgrade’s release. \u00ab\u00a0But if you’re not at the front of the testing line, you don’t get 18 months. So should I speed up my timeline to get [the full] 18?\u00a0\u00bb
If Microsoft promises that support lifecycle, Cherry argued, enterprise users should get it. \u00ab\u00a0The clock really shouldn’t start until [a version] is fully deployable without concerns, \u00a0\u00bb he said. That would be when Microsoft reported a build as business ready, and promoted it to the Current Branch for Business, or when that label wears out, Semi-Annual Channel (Broad) .
Under that alternate scheme, Windows 10 upgrades would be supported for a total of 22 months, not 18, as each refresh would still require some testing, presumably the same four months as today, with consumers before it’s rated ready for enterprise deployment. Such a change may seem minor, but it would mean — assuming Microsoft continues to issue feature upgrades at six-month intervals — that the firm would be required to support not two, but three CBB\/Semi-Annual Channel (Broad) releases simultaneously, and for a four-month span when the latest was in consumers’ hands, four releases.
To know when support lapses for each given Windows 10 release, enterprises must construct visual aids, Cherry argued. \u00ab\u00a0You have to actually figure out your support, \u00a0\u00bb he complained. \u00ab\u00a0You almost have to build a matrix.\u00a0\u00bb
Microsoft has provided nothing like that. Previously, that was understandable because Windows 10 releases were on a more flexible schedule. But under the twice-yearly plan, releases and support are supposed to be consistent so that enterprises can plan; some kind of chart should have been forthcoming from Microsoft.
\u00ab\u00a0It’s frustrating, \u00a0\u00bb concluded Cherry, speaking of Microsoft’s silence on scheduling topics. \u00ab\u00a0Our clients come to us for answers, and we don’t have them.\u00a0\u00bb
If Microsoft extended Windows 10 support to 18 months for corporate customers, as one analyst recommended, it would have to maintain three releases simultaneously, one more than it has pledged to do.<\/p>\n

\n

Similarity rank: 4.3<\/div>\n

Sentiment rank: 0.3<\/div>\n

<\/div>\n<\/div>\n