SharePoint 2016

Posted on 8/10/2015 @ 6:57 PM in #SharePoint by | Feedback | 3668 views

Getting ready to move to SharePoint 2016? Well, still read this up, you might find this useful one day. All of the below is pre-beta, subject to change before release,

  • SharePoint 2016 is a point in time capture of what Office 365/SharePoint online is, and turned it into an on-premises offering. So you will see a number of new hybrid/cloud accelerated experiences.
  • A really notable hybrid scenario being a search service application for cloud storage, which creates a unified index between cloud and on-prem, enabling you to bring delve and office graph to onprem.
  • Extranet scenario which allows you to publish internal sites to the internet using O365 identity federation services
  • Its going to need 16-24G of RAM (for single server), 12-16G of RAM (farm server), 80G HDD, quad core x64 processor
  • Requires Windows Server 2012 R2 with .NET 4.5.2 or Windows Server 10 with .NET 4.5.6. Uses PowerShell 3.0. You will also need to disable RC4 in TLS using KB2898850. 64 bit only
  • It will also need SQL Server 2014 SP1 or newer. 64 bit only.
  • Still uses distributed cache (AppFabric) -  but AppFabric is supported only in SharePoint. You cannot use it for custom code. Also distributed cache offers better performance because it skips NTLM auth when hopping between features because of a new transport layer underneath per feature.
  • Big cost related change: Standalone installations that used SQL express will no longer be supported.
  • Big cost related change: There is no freebie SharePoint foundation
  • You can do database attach upgrade from SP2013 to SP2016. Site collections cannot be in 2010 compatibility mode (14.5 compat mode).
  • SAML authentication will be the default and first class authentication choice. There is only one authentication provider. Windows Identity will be supported over SAML claims. For apps, you will have OAuth backed by AD or Azure AD.
  • For alert emails, SMTP Connection encryption, supporting non default ports and encrypted communication with the SMTP server.
  • Farm solutions still work, but are highly discouraged especially when you can deliver functionality using apps/add-ins.
  • MinRole: During installation (either powershell or psconfigui), MinRole enables an administrator to select the appropriate server role for a specific server when provisioning SharePoint Server 2016 based on five (5) predefined configurations: WFE, Single Server Farm, Search, Application, Distributed Cache, or Special Load – while this could still be done in SP2013, they’ve just made it a lot easier to setup in 2016. Here is a nice walkthrough of the minrole installation http://1drv.ms/1EBogcv
  • There are health rules that will check if your server deviates from minrole, except special load. Special load = custom like you have in SP2013 today. The central administration\servers in farm page will also show you if any server is out of synch with it’s defined role. And you can click a “FIX” Button to bring it back into compliance with the predefined role.
  • Patches with SP2016 will be smaller, and B2B upgrades will not require downtime.
  • Content DB will size up to terabytes
  • You can have up to 100K site collections per content DB
  • List Threshold will be increased to > 5K
  • Max filesize is going up to 10GB, and no character restrictions
  • Large files will be uploaded using BITS instead of SOAP over HTTP, which means better file upload performance
  • Fast Site Creation – greatly improves new site collection creation, it does so by copying a site collection at the content db level, saving loads of time on feature activation.
  • Traffic management: This is a “maybe it’ll never make it to the final product”, but its an endpoint that the load balancer can listen to, and redirect traffic accordingly
  • User profile synch: is like unidirectional import by default (SP2007 style), for bi directional – built-in FIM has been removed, and you can select an external FIM service.
  • Project server databases are now content dbs, and you have durable links to shared files.

Sound off but keep it civil:

Older comments..