SharePoint 2016 on-premises update Ignite recap
I was fortunate enough to attend the Ignite conference last week in Chicago it was a good time, lots of good news we're coming out with. I highly recommend watching the Bill Baer sessions on SharePoint 2016 on Channel9 that I have listed at the end of this post. I also attended a YamJam about 2016, I have provided a bulleted list of most news related to SharePoint 2016 on-premises:
- Patching more details to follow soon but 0 downtime because we removed dependencies between Front end and Back End components
- InfoPath Designer will not be shipped with 2016 but we will bring forward InfoPath forms Services to SharePoint 2016 and support InfoPath 2013 client.
- SharePoint Designer will not be shipped with 2016, SharePoint Designer 2013 can still be used with SharePoint 2016
- When installing Office 2016 it will remove:
- InfoPath Designer 2013
- SharePOint Designer 2013
- Project 2013
Note: You will have to reinstall via your original media if you need it
- Actively working to address the 5000 List View Threshold, more details soon on new increased threshold
- MaxFile size increased to 10GB, removed character restrictions. This will be achieved natively within SharePoint 2016 no need for a native and/or 3rd party RBS provider
- 2x increase in Search scale to 500 million items
- 100,000 site collections per content database
- Content Database sizing into the TBs
- We will continue investing in broader availability of endpoints to support search scenarios, particularly connectors. We are also going to ship new APIs to support surfacing external sources in Delve
- There will be updates to existing PowerShell cmdlets and new cmdlets specific to SharePoint 2016
- Removed integrated FIM implementation and will now support uni-directional sync via AD sync in addition to external MIM for bi-directional sync scenarios
- No plans to deprecate any of the capabilities as they exist in SharePoint 2013 for SharePoint 2016
- Workflow Manager and Workflow foundation will be brought forward from SharePoint 2013 and we are actively investigating new modern workflow scenarios
- Working on a new analytics solution that provides a more rich experience when compared to previous Web Analytics experiences
- SAML claims-based authentication is the preferred authentication method but Windows classic authentication (i.e. NTLM/Kerberos) will remain supported and available through the UX
12/28/15 UPDATE: Windows Claims Authentication is the default authentication method out of the box. As of this writing all of the steps that were used to configure SharePoint 2013 to use SAML authentication will need to be followed to have your SharePoint 2016 environment work with SAML authentication. SharePoint 2016 is in Beta 2 so there is no final picture of what the specific improvements/changes for SharePoint 2016 with SAML authentication will eventually be when an RTM candidate is available
- AppFabric remains supported with SharePoint 2016 thru its lifecycle, this is specific to the standalone AppFabric scenarios.
- SharePoint on-premises will continue to ship on a 2-3 year cadence whereas we update SharePoint Online monthly, the objective being that we will define on-premises through the cloud.
Whats new for IT Professionals in SharePoint 2016?
The Evolution of SharePoint: Overview and RoadMap: