Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Microsoft slashes IE support, sets 'huge' edict for Jan. 2016

Gregg Keizer | Aug. 11, 2014
Company makes another move that will complicate the lives of its best customers: enterprises

Commercial customers, however, were always able to dodge the auto-upgrades, either through blocking toolkits or by using their patch management systems, like WSUS (Windows Server Update Services).

End-arounds like that will be moot once Microsoft pulls the patch plug. And that's going to be a problem for enterprises, analysts said.

"Most organizations need to test their applications [against a new browser], and historically many of those applications broke. And many ISVs [independent software vendors] require and only support specific IE versions for their products," said Silver.

Microsoft's slashing of IE support will, at the least, disrupt enterprises and create a backlash, at worst drive some to consider alternatives, like Google's Chrome or Mozilla's Firefox.

"This will irritate enterprise customers," said Miller. "They want to hang on to their legacy [Web] apps."

Hilwa of IDC echoed that, but with a caveat. "Probably there will be pushback, but these steps have to be taken," he said. "I am afraid this is inevitable and it is the right thing to do for Microsoft. [And] I think the way software is being released and updated is changing. Over time, enterprises have to adjust."

Hilwa made two interesting points, both which were echoed by other analysts Computerworld spoke to. "It is the right thing to do for Microsoft," and "enterprises have to adjust," he said.

Those same comments were common prior to the retirement of Windows XP, which was forewarned years in advance but still caught many companies short of having stripped the OS from their networks, for reasons that ranged from the same app compatibility issues that Silver mentioned to lack of time and money.

The fact is that outsiders, including some customers, saw XP's retirement as primarily beneficial to Microsoft — after all, the company makes relatively little revenue from existing PCs but books the bulk of Windows sales from OEMs that build new machines — and not themselves. Many were angry and frustrated that they were the ones forced to adapt, which cost them money, not Microsoft.

"I thought Microsoft had learned about 8-10 years ago that pushing people would backfire, but looks like new management, old style," said Edward Tinker, an IT security professional, in an email today. Tinker was reacting to a Computerworld story earlier Friday that reported Microsoft's accelerated release schedule for Windows, and the impact on enterprises.

Tinker could just as well have been talking about the IE support revamp; the two will play out much the same.

"My main concern is that, even with a long lead time [to January 2016], we're talking about businesses who generally need to take long lengths of time for change, often for compliance reasons," said Miller of Directions. "Even with almost a year and a half, enterprises need to get in motion soon. But I think a lot aren't going to, so they'll go through a fire drill, like when they chose to hang on to XP."

 

Previous Page  1  2  3  4  5  Next Page 

Sign up for Computerworld eNewsletters.