preview of Microsoft Exchange 2016 reveals more of a service pack for Exchange 2013 than a full server release. The real innovation can happen in the cloud version and the propaganda is quite loud and clear. Eventually the product will become cloud only with Microsoft’s “cloud first” strategy.
This same thing is also applicable for SharePoint 2016. It has released the detail and shows that SharePoint2016 is on the same path as Exchange 2016. The path selected is called hybrid path which is extended by the cloud-only features, with the mix shifting from on-premises to cloud over time.
The on-premises version of the SharePoint is already evolving in the cloud as a part of Office 365 and as Online SharePoint. Some of the cloud features of SharePoint will not be brought to the on-premises such as Office Graph and Delve. These features will take advantage of cloud to what Microsoft calls “cloud – accelerated” experiences. Ultimately it leads to hybrid configurations involving on-premises SharePoint and letting the users to run the most of the SharePoint on your own server and take the advantage of the features that exist only in the cloud version.
Check out the three example of “cloud- accelerated” experience:
SharePoint will not enable for a stand-alone SQL Express. However, you can still install SharePoint 2016 on a single sever with SQL server installed. Unlike Exchange, which has steadily reduced the number of several roles, you can deploy from five roles in Exchange 2007 and 2010 to the three roles in Exchange 2013 to two roles in Exchange 2016, SharePoint is going in the other way. You need to choose the below mentioned roles by deploying the single server farm or a multiple-server farm:-
Additionally, there are changes in the authentication opinions, with Azure Active Directory trusted by default. Microsoft is apparently moving away from Windows-based identities in favor of claims-based options.
This same thing is also applicable for SharePoint 2016. It has released the detail and shows that SharePoint2016 is on the same path as Exchange 2016. The path selected is called hybrid path which is extended by the cloud-only features, with the mix shifting from on-premises to cloud over time.
The on-premises version of the SharePoint is already evolving in the cloud as a part of Office 365 and as Online SharePoint. Some of the cloud features of SharePoint will not be brought to the on-premises such as Office Graph and Delve. These features will take advantage of cloud to what Microsoft calls “cloud – accelerated” experiences. Ultimately it leads to hybrid configurations involving on-premises SharePoint and letting the users to run the most of the SharePoint on your own server and take the advantage of the features that exist only in the cloud version.
Check out the three example of “cloud- accelerated” experience:
- Search through Office Delve: To provide the predictive personalized content for users, Delve uses Office Graph. A hybrid SharePoint deployment would enable on-premises SharePoint server to still take an advantage of Delve.
- Next-gen protocols: For this, the best example is Office 365 Video, which enables the video content for users in Office 365. Again, a hybrid development would make this capability available to an on-premises SharePoint sever environment.
- Files: Due to the great strategy of Microsoft, it pushes the user to use OneDrive to manage the files across all devices. The system can integrate OneDrive cloud storage into your on-premises SharePoint and that makes sense.
SharePoint will not enable for a stand-alone SQL Express. However, you can still install SharePoint 2016 on a single sever with SQL server installed. Unlike Exchange, which has steadily reduced the number of several roles, you can deploy from five roles in Exchange 2007 and 2010 to the three roles in Exchange 2013 to two roles in Exchange 2016, SharePoint is going in the other way. You need to choose the below mentioned roles by deploying the single server farm or a multiple-server farm:-
- Special Load: For a third-party services isolation from other services
- Web Front end: For user requests
- Search: For Search services
- Application: For back-end jobs
- Distributed Cache: For load balancing of user requests from the Web Front End role.
Additionally, there are changes in the authentication opinions, with Azure Active Directory trusted by default. Microsoft is apparently moving away from Windows-based identities in favor of claims-based options.