This article lists out the difference between SharePoint 2013 and SharePoint 2016.
As you all know, SharePoint 2016 has too much to offer to an administrator or a developer. As an administrator, I love the changes that Microsoft has done in SharePoint 2016. I will also talk about the features, which are deprecated by Microsoft in SharePoint 2016.
SharePoint 2013 Vs SharePoint 2016.
I will try to explain all the features in the SharePoint 2016 row, which were not present in SharePoint 2013.
App Launcher
It helps SP 2016 to match the Office 365 experience by providing the users almost an identical interface to navigate both SharePoint 2016 and Office 365.
Min Roles
With SharePoint 2016, we can select the specific role of a Server and according to the role Service will be enabled on the Servers. Thus, we don’t have to worry about individually running SP Services on Specific SP Farms.
Min-Role Farm Topology
Six pre-defined roles are available to create a new Farm or join an existing Farm. SP automatically configures the Services according to the selected role.
Zero Downtime Patching
In order to take the advantage of zero downtime patching, your Farm must have a High Availability, HA and topology.
Integrated Project Server
Project Server 2016 is installed with SharePoint 2016 but it will be licensed separately.
Deprecated Features
Six features are deprecated from SharePoint 2016, if we compare it with SharePoint 2013 or the previous editions.
- SharePoint Foundation – SharePoint Foundation has been removed.
- Stand-Alone Installation - Stand-alone is not possible now in SP2016 for Single Server you have to make sure that SQL installed and configured.
- Forefront Identity Manager Client (FIM) - In SharePoint 2016 Microsoft replace FIM with MIM.
- Excel Services in SharePoint - SharePoint Server 2016 you must also deploy Office Online Server with Excel Online to ensure Excel Services functionality remains available.
- Tags and Notes - You will no longer be able to create new tags or notes or even to access existing ones.
- Stsadm.exe - PowerShell is the way to go but backward compatibility remains with STSADM.
No comments:
Post a Comment