What do you need to run SharePoint 2016?

In this article we are going to cover some important things, you need to know about system requirements, configuration and scenarios for planning and running SharePoint Server 2016.
– MinRole feature. With the help of this new feature SharePoint farm administrators can now define each server’s role in a farm topology. When you select a role, SharePoint automatically configures the services on the chosen server based on the respective server role.
– Standalone Farm Installations. The option for a standalone installation on a single server is no longer available in SharePoint Server 2016. The SharePoint administrators now must separately install and prepare Microsoft SQL Server to be included as a SharePoint Single-Server Farm.

Below are few sets of System Requirements for SharePoint 2016:

Scenario

 

If you are considering the upgrade from SharePoint 2010 or SharePoint 2013, these are the tips you should keep in mind during this process:

  • To upgrade from SharePoint Server 2010, you should first upgrade to SharePoint 2013 and then to SharePoint 2016.
  • To upgrade SharePoint Server 2013 to SharePoint Server 2016, you need to make sure that you first upgrade the SharePoint Server 2013 Site Collections that are still using SharePoint 2010 mode to SharePoint 2013 mode.
  • To upgrade from SharePoint Server 2013 to SharePoint Server 2016 you can either perform an in-place upgrade, or apply the database-attach method as described below:
  1. Create a SharePoint Server 2016 farm.
  2. Copy SharePoint Server 2013 content and service application databases.
  3. Attach the databases to SharePoint Server 2016 farm.

SharePoint Server 2016 new hybrid features

New hybrid features of SharePoint Server 2016Microsoft has announced SharePoint 2016 version vision and strategy in April 2015. It became available for users with SharePoint Server 2016 IT Preview edition in August 2015. To meet the exact up-to-date customers’ needs the SharePoint Server 2016 Beta 2, based on customers’ feedback, has been released in November 2015.
SharePoint Server 2016 introduces familiar and intuitive user experiences, cloud-inspired infrastructure with hybrid at the core and robust security and compliance for SharePoint Server 2016.
MS SharePoint Server 2016 Beta 2 provides new hybrid experiences that enable customers to take advantage of the possibilities of the cloud.

In SharePoint Server 2016 new hybrid features are available to enable hybrid solutions. Here are the most prominent ones:

– Hybrid Cloud Search. A new unified Search approach experience is now available in SharePoint Server 2016. With its help all of your crawled content gets indexed (including on-premises content) to your search index in Office 365. You would need to use the Office 365 Search to take advantages of this feature.

– Hybrid OneDrive for Business. Users can sync files with Office 365 and share them with others. They can also get access to their files through the Office 365 directly from any device.


- Extensible Hybrid App Launcher. SharePoint Server 2016 Beta 2 introduces the App Launcher to gain a common access experience across applications and solutions in Office 365 and SharePoint Server 2016.

– Sites you follow in one place. Users can now have the ability to follow SharePoint Server and SharePoint Online sites, and see them aggregated in a single list. 
- Data Loss Prevention. Intensified support for new Data Loss Prevention capabilities is included in SharePoint Server 2016 Beta 2.

– Increased File Size for uploads. The limit for maximum size of the uploaded file to SharePoint, set to 2Gb in previous versions, is no longer the issue. Though there’s no real limit now, Microsoft has strongly recommended for it not to go beyond 10Gb.

– Mobile experience. SharePoint Server 2016 comes with a touch friendly interface to allow you to make decisions faster and keep in contact with colleagues.

– Durable links. The idea is to make sure that links, you sent to your folks continues to work regardless of what happens to the document, i.e. the file name was changed or the document moved.

– Compliance tools. SharePoint Server 2016 provides a wide range of features and capabilities to ensure sensitive information to remains safe and that the appropriate people have access to the right information at the proper time.

How To – SharePoint Server 2016 Installation and Deployment

Today I would like to share some information regarding the upcoming SharePoint Server 2016. This article describes initial investments made in installation and deployment of SharePoint Server 2016 from Microsoft Ignite in Chicago.

1. Hardware Requirements
Installation with the minimum recommended services.

Pic-1

Test installation running all available services

Pic-2

2. Operating System Requirements
SharePoint Server 2016 is supported on Windows Server 2012 R2 and Windows Server Technical Preview.

3. Database requirements
SharePoint Server 2016 requires SQL Server 2014 for its databases, also it will support SQL Server 2016.
For additional information on SQL Server 2016 see also http://www.microsoft.com/en-us/server-cloud/products/sql-server-2016/.

4. .NET Framework requirements
According to Microsoft starting from January 13, 2016, .NET Framework 4.5.2 will be the minimum supported version of .NET Framework 4.x.
For SharePoint 16 based on Windows Server 2012 R2 you will need .NET Framework 4.5.2 version.
For SharePoint 16 based on Windows Server Technical Preview “Threshold” you will need .NET Framework 4.6 Preview version. This version comes with Windows Server Technical Preview “Threshold”.

5. Prerequisites
SharePoint Server 2016 prerequisites are the same as for SharePoint Server 2013. Prerequisites can be installed manually or with the Prerequisite Installer, similar as for SharePoint Server 2013.
Here is the full list of SharePoint Server 2016 prerequisites:
– Application Server Role, Web Server (IIS) Role
– Microsoft SQL Server 2012 Native Client
– Microsoft ODBC Driver 11 for SQL Server
– Microsoft Sync Framework Runtime v1.0 SP1 (x64)
– Windows Server AppFabric 1.1
– Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763)
– Microsoft Identity Extensions
– Microsoft Information Protection and Control Client
– Microsoft WCF Data Services 5.0
– Microsoft WCF Data Services 5.6
– Microsoft .NET Framework 4.5.2
– Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850)
– Visual C++ Redistributable Package for Visual Studio 2013

6. MinRole (v1) Overview
MinRole is one of the new infrastructure advancements in SharePoint Server 2016. MinRole is designed to transform guidance into code, simplifying deployment and scale with SharePoint ensuring a request is served end-to-end by the receiving server based on the origination of the request (I.e. end user or batch processing) and role of the destination server.
In previous versions of SharePoint, servers’ role was only defined by what services were provisioned and its placement in a SharePoint Farm topology.

MinRole simplifies on-premises server farm deployments, and reduces the unit of scale to simplify capacity planning while providing predictable performance characteristics through enabling selective provisioning of SharePoint server roles based on position and function within a topology.

Pic-3

MinRole enables an administrator to select the appropriate server role for a specific server when provisioning SharePoint Server 2016 based on predefined configurations:
Role №1 – Single Server Farm
Provisions all services on the server for a single server deployment. This role is provided for evaluation and development purposes.
Role №2 – Application
Services the backend jobs or the requests triggered by backend jobs, optimized for high throughput.
Role №3 – Web Front End
Services end user requests, optimized for low latency.
Role №4 – Search
Reserved for Search services.
Role №5 – Distributed Cache
Services distributed cache for the farm. Optionally, the server assigned to this role can load balance end user requests among the web front ends.
Role №6 – Special Load
Reserved for services to be isolated from other services, I.e. 3rd party, PerformancePoint, etc.

Also MinRole adds a new command line parameter, “localserverrole”, that can be used to specify the role that should be assigned to a specific server when configuring SharePoint Products and Technologies. Also MinRole can be instrumented through the PSConfig GUI.

7. Upgrade and Migration
SharePoint Server 2016 will support upgrade from SharePoint Server 2013. To upgrade from SharePoint Server 2013 to SharePoint Server 2016, you can use the database-attach method to upgrade.
As for site collections provisioned in backward compatible SharePoint 2010 (14) mode, they must be upgraded to 2013 prior to upgrading to SharePoint Server 2016.