Microsoft says that it wants to push rapid updates to users; but there are issues…
I saw an interesting update on the Supersite for Windows the other morning, and I answered a comment asking what the issues were on this in the US. I wanted to expound a bit more, so I thought I’d gather what I wrote and then start shooting my mouth off.
The original article deals with Microsoft taking control of OS related updates from the mobile carriers – in the States, that’s basically, AT&T, Verizon, T-Mobile and Sprint, but may also include a number of larger regional or budget carriers like US Cellular, Cricket and Boost Mobile – and making updates available roughly four to six (4 – 6) weeks after the updates go RTM. Based on a report from Ed Bott, Microsoft is serious about it. According to Terry Myerson,
“Here at Microsoft, we take our responsibility to keep Windows secure seriously. We follow up on all reported security issues, continuously probe our software with leading edge techniques, and proactively update supported devices with necessary updates to address issues. And today, we’re announcing this continuous update process applies to all Windows 10 devices, including phones.”
The only way that Windows as a Service (WaaS) REALLY works, is if Microsoft can release updates to users as they are ready.
The problem is that mobile broadband carriers in the US don’t allow just anything to ride their networks and don’t allow hardware manufacturers or OEM’s to release just any device update without that update going through a testing and certification process. Well, at least everyone but Apple; users of any cellular capable iDevice get iOS updates all the time…as soon as they’re released, in fact. I’ll deal with Apple in just a bit. However, every other device and device manufacturer/ OEM has to jump through a lot of hoops.
There are two parts to this issue: Control of the (enterprise) network and control of support. The second one is easy to understand. The first one is a PITA.