SharePoint Server 2016 Bringing Perks for IT Pros
Microsoft MVP Vlad Catrinescu outlined some of the benefits and hardware requirements of the upcoming SharePoint Server release.
SharePoint Server 2016 is planned for product release this quarter, but its improvements mostly will be of interest to IT pros.
An overview of those improvements was described on Thursday by Microsoft MVP Vlad Catrinescu, president of vNext Solutions. His presentation, "What's New in SharePoint 2016 for IT Professionals," was hosted by SharePoint application developer Crow Canyon Systems. In it, Catrinescu described SharePoint Server 2016's requirements, topology changes and new features. Update: Microsoft now hosts the talk on demand at this Channel 9 page.
During the Q&A portion, he recommended upgrades for those organizations with existing SharePoint Server farms.
"If you are on [SharePoint Server] 2007 or 2010, you're not supported anymore, so go to [SharePoint Server] 2016 as soon as possible -- that's a no brainer," Catrinescu said. "If you're on [SharePoint Server] 2013, a lot of people have said that there are not that many reasons to upgrade, but I don't agree with that. First of all, SharePoint 2016 is a lot more stable. It's a lot faster to use for your users.
He also stressed the benefits of some new SharePoint Server 2016 features.
"There are features such as DLP [data loss prevention]," Catrinescu said. One of my clients that wants to go to SharePoint 2016 are going to save $50,000 annually only on that DLP feature because right now they use third-party products to do it. Another one is durable links. You want to get people to move from file shares to SharePoint, and durable links can be a great argument. You say, 'Look, on the file share, when you move something, your link is broken. You put it into SharePoint now, you can move it anywhere on any site and your link won't be broken.' Also, there's hybrid. Hybrid is getting better. You get so many new features. I know that maybe you don't see the reason right away. However, Microsoft is going to add more stuff in 2016 during the year. I'm sure we are going to see some new features in 2016 that are going to make the upgrade even more valuable."
Hardware requirements for SharePoint Server 2016 won't be different from the preceding product, SharePoint Server 2013. On the software requirements side, organizations will need Windows Server 2012 R2 or Windows Server 2016 in place. They'll also need SQL Server 2014 Service Pack 1 or SQL Server 2016. Catrinescu recommended going with SQL Server 2016, if that's an option.
Upgrading from SharePoint Server 2013 to SharePoint Server 2016 is really fast, Catrinescu said. However, if an organization is using SharePoint Server 2010, then there's no direct upgrade path to SharePoint Server 2016. It will be necessary to upgrade to SharePoint Server 2013 first before making that hop.
Some Limits Removed
SharePoint Server 2016 is removing some limits seen with Microsoft's earlier releases. For instance, there was a list item limit of no more than 5,000 items for SharePoint Server 2010 and SharePoint Server 2013. SharePoint Server 2016 now permits more than 5,000 items in a list, with some caveats. Catrinescu said that the maximum he has seen is 120,000 items in the same list view and he said it works, but it's not fast. The problem isn't with SharePoint, he explained, but with SQL Server, which can lock if you query a list with over 5,000 rows in a table.
Microsoft also increased file sizes used with SharePoint Server 2016. The maximum file size previously was 2GB, but now it's 10GB or greater (which is the recommended limit). Catrinescu said he's tried a file that's 15GB in size and it works. While the file size expansion is a good thing, Catrinescu cautioned IT pros that they should still keep an eye on the growth of their content database sizes.
Site collections per database got a boost with SharePoint Server 2016. The old limit was 5,000 site collections. The new server expands that limit to 100,000 site collections. This slide summarized the increased limits in SharePoint Server 2016:
SharePoint Server 2016 will bring a new MinRole topology option, which reflects Microsoft's best-practice approach for server farms. Catrinescu said that earlier SharePoint Server products, such as SharePoint Server 2010, had "traditional topologies" with two server roles, a front-end server and an application server. With this design, there was useless network communication happening to access various services in response to user requests, which generally slowed things down, he explained.
Microsoft came out with "streamlined topologies" with SharePoint Server 2013, consisting of four server roles: a front-end server, a distributed cache server, a batch processing server and a server for specialized workloads. The benefit of this approach is that user requests for services were accessed from the front-end server, so results came back to users faster. This approach stopped wasting inter-server communications time and was a lot better, but it wasn't 100 percent optimized, he said. The streamlined topologies approach wasn't hard coded in the product, but was just based on Microsoft's guidance.
The new MinRole topology requires the use of at least four server roles to make a farm: front-end, distributed cache, application and search. IT pros specify the server role when adding a server to a server farm. User requests come from the front-end server. Distributed caching happens on the distributed cache server. Scheduled tasks come from the application server. The custom server role runs anything you want. SharePoint Server 2016's MinRole approach is shown in this slide:
It's possible to have a single server topology with SharePoint Server 2016, but it doesn't include SQL Express anymore, so organizations have to install SQL Server separately if going this route. However, it's not possible to have a custom server and a single server in the same SharePoint farm, Catrinescu said. If an organization doesn't have four servers to spare, they can go with the custom server option.
Microsoft essentially hardcoded the streamlined topology approach with MinRole. "MinRole is actually [SharePoint Server] 2013 guidance from the streamlined topology, but in code," Catrinescu said. In general, MinRole, derived from Microsoft's cloud approach, requires less testing and promises more simplified deployments than the older approach. Catrinescu showed the following slide, which contrasts the MinRole approach in SharePoint Server 2016 with the streamlined topologies approach in SharePoint Server 2013:
Highly available topologies with SharePoint Server 2016 using the MinRole approach, and including a custom server plus Office Online Server (formerly known as "Office Web Apps Server"), will require having 14 servers in place, Catrinescu said. It's still possible to have high availability with just two servers, but you'd have to go the custom role route, he explained.
Later during the talk, Catrinescu said that Office Online Server is something that IT pros maintaining SharePoint farms likely will have to install since so many SharePoint features will depend on it. Office Online Server is currently at the preview stage, and Microsoft hasn't indicated a product availability milestone for it yet.
Catrinescu blitzed through some of SharePoint Server 2016's new features. Hybrid support is a big theme with SharePoint Server 2016. Catrinescu said that using the SharePoint hybrid configuration wizard is really easy now.
There's support for hybrid Team Sites. Microsoft added a profile redirection capability that shows information in Delve, which is Microsoft's Office 365 solution that surfaces organizational and contact information. Documents tracked by Delve will show up in a SharePoint intranet sites. Hybrid search will show the best results in a single page.
The zero downtime patching claim for SharePoint Server 2016 is "not a myth," Catrinescu said. It works, but organizations will need to use the MinRole topology with high availability to have that capability. He explained that to patch SharePoint Server, there are two required steps. The update needs to be installed first and then the PSConfig program needs to be run. With SharePoint Server 2016, the schema update process doesn't cause server downtime, but MinRole with high availability will be needed to get that benefit.
Another new feature is the ability to create durable links, where URL links don't break when files get moved. That's an issue today with SharePoint Server 2010. However, Catrinescu noted that to use the durable links feature with SharePoint Server 2016, organizations likely will need to install Office Online Server. The Office Online Server also brings benefits for business intelligence and search capabilities, he added.
Microsoft has enabled a Fast Site Collection Creation feature for SharePoint Server 2016. It copies a template at the database level to speed up the site collection process.
Microsoft has integrated Project Server, which now functions as a service application in SharePoint Server 2016. This feature eliminates having to oversee two separate patching activities.
SharePoint Server 2016 also is bringing the ability to use SMTP ports other than the default one (Port 25). Other ports now can be used to send e-mails.
Data loss prevention (DLP) also arrives with SharePoint Server 2016. It's used to find sensitive info before it gets leaked in e-mails. It'll flag things like credit card numbers, Social Security numbers and bank account numbers, protecting against disclosure, and also advising the end user about the issue. It works with Microsoft's E-Discovery Center, which has a query capability to find sensitive documents.
Microsoft plans to deprecate some of its software used with SharePoint Server 2016. The deprecated software won't get further development by Microsoft. Catrinescu has actively tracked those deprecation changes in his blog.
He said that SharePoint Foundation goes away with SharePoint Server 2016. Excel Services is gone, too, but if an organization has Office Online Server in place, they'll still have some of those Excel Services capabilities.
Forefront Identity Manager 2010 R2 is replaced by Microsoft Identity Manager 2016. Catrinescu commented that Microsoft Identity Manager 2016 wasn't built in SharePoint Server. It's a fully separate product now. He explained that the old Forefront Identity Manager 2010 code just didn't mesh with Microsoft's best practices for the new SharePoint Server. Moreover, Forefront Identity Manager 2010 didn't work with Windows Server 2016. Microsoft Identity Manager 2016 is a more "modernized platform" that has the capability for hybrid Active Directory deployments. On SharePoint Server 2016 farms, using Microsoft Identity Manager 2016 can require using an extra server and is "a lot harder to set up." However, it also can be installed on SharePoint's application server, which is a Microsoft supported approach and it's what most organizations will do, Catrinescu said.
SharePoint Designer 2013 and InfoPath 2013 are subject to deprecation by Microsoft but they will still work with SharePoint Server 2016. Microsoft announced extended product support for those solutions this week when it rolled out the release candidate of SharePoint Server 2016.
Catrinescu claimed that Microsoft introduced no new features with the release candidate of SharePoint Server 2016 compared with the earlier beta 2 release. Microsoft is just fixing about 250 bug fixes, he said.