by Craig Roth | May 10, 2015 | Comments Off on Microsoft Ignite: Of Course We’re Dedicated to SharePoint Server! Did You Ever Doubt That?
My main goal at Microsoft Ignite was to judge the SharePoint Server zeitgeist. To be clear, since Office 365’s announcement at SPC13 Microsoft never said they weren’t dedicated to continuing its on-premises version. But they didn’t do a lot to say they were either.
Vendors often don’t talk two full versions out, but they also don’t often push a competing product either. And when one of those products gets a huge amount of push and messaing that makes users of the old product feel like dinosaurs, I can understand how many of the clients we talked to felt they would be hurt by staying on premises. That didn’t have to be the server product being discontinued – it could be lagging investment, punative pricing, or hobbled functionality.
So it seems Microsoft has realized they needed to turn up the volume on their Server messaging. And they did. For example, Julia White said “We’re deeply committed to Server”.
So there you have it: Server lives. Whether it was simply a misunderstanding, a head fake to see how many customers they could get to duck over to the cloud, or backtracking is a matter of debate. But the result is the same: SharePoint Server 2016 will be a real version; more than just patches to the old one. They outlined a set of improvements, many driven by what they’ve learned from managing it themselves at cloud scale.
So what about SharePoint Server 2019/2020? Mum’s the word.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.