Productivity solutions
- 10/9/2017
- Skill: Evaluate content and customizations
- Skill: Plan an upgrade process
- Skill: Create and configure app management
- Skill: Create and configure productivity services
- Skill: Create and configure a Business Connectivity Services (BCS) and Secure Store application
- Skill: Manage SharePoint solutions and applications
- Summary
- Thought experiment
- Thought experiment answer
Summary
The upgrade path to SharePoint Server 2016 uses the database attach method.
The Test-SPContentDatabase indicates (but does not correct) issues with content databases.
All content databases to be migrated must be first upgraded to a minimum level of 15.0.4481.1005, or Service Pack 1 and the March 2013 PU to be upgraded to SharePoint 2016. If the SharePoint 2013 farm was initially created with the combination SharePoint 2013 and Service Pack 1 media, then the farm is already at this version level.
A correctly upgraded configuration database does not necessarily indicate that all the surrounding content databases are successfully upgraded.
All SharePoint 2010 site collections in the SharePoint 2013 farm must be upgraded to 2013 site collections prior to the SharePoint 2016 upgrade process.
Web Applications need to be upgraded from classic- to claims-aware authentication, as classic mode is no longer supported in SharePoint 2016.
Consider making some content read-only and migrating content to expand migration scheduling opportunities.
The installation sequence for a new SharePoint 2016 farm should begin at the data tier and work out, in accordance with MinRole guidance.
Content can be migrated from SharePoint on-premises to SharePoint Online by using a Microsoft FastTrack partner, the SharePoint Online Migration API, or Windows PowerShell cmdlets. If you have a significant body of content (more than 10 TB), consider shipping the disk media to Microsoft for upload to your tenancy.
Although you can create the App Management service application from Central Administration, you’ll still have to create the Subscription Settings service application from PowerShell. You might as well build both at the same time from PowerShell.
Building new service applications in a MinRole-compliant SharePoint 2016 farm does not require you to start the individual services (as you would have in 2013); the farm will start these for you.
The App Catalog should live in its own DNS space, not in a subdomain or subsites or managed path because that introduces security issues. The FQDN is used with the app hash to create a unique URL.
Office Online Server is an on-premises server, despite the name; it replaces the Office Web Apps Server in a SharePoint 2016 farm.
SharePoint Insights and SharePoint Telemetry provide the ability to view on-premises server events and performance and user metrics from Office 365.
BCS models are XML-based, and can represent four distinct data sources: Windows Communication Foundation, SQL Server, SQL Azure, and OData sources (including SQL OData sources).
BCS supports three different authentication methods: Credentials-based authentication, Claims-based authentication, and Custom authentication.
Hybrid BCS has four prerequisites: that all user accounts are federated, that there is a service account for the OData service endpoint, that there is a global security group in the on-premises domain, and that the federated accounts be added to the global security group.
Apps (Add-ins) are available for deployment from three locations: a list of previously available Add-ins, from the Add-in Catalog, or from the Office Store.
As is the case with solutions, Add-ins can be added from PowerShell.
Add-ins can be either updated or migrated, depending on their complexity.