Upgrade to SharePoint 2016 - Todd Klindt June... · Upgrading to SharePoint 2016 with as Little...

transcript

This image was selected is show placement and can be replaced with another full slide image.

Upgrading to SharePoint 2016 with as Little Pain as Possible

Todd Klindt, SharePoint MVP

Distinguished Architect

@toddklindt

http://www.toddklindt.com/blog

www.toddklindt.com/blog

http://sharepoint.rackspace.com

todd.klindt@rackspace.com

• @toddklindt

• http://www.toddklindt.com/netcast

Who is this Todd Kl indt guy?

My name is Shane Young

Running for President of the USA

SharePoint MVP for 11 years

Microsoft Cloud Consultant for my company Bold Zebras

http://www.boldzebras.com

Shane.Young@boldzebras.com

@ShanesCows

Agenda

Upgrade Survivor

Gradual

Upgrade

Upgrade Survivor

Gradual

Upgrade

In-Place

Upgrade

• Buy a 3rd party tool

Secret method?

SharePoint 2016 For You and Me

• No shortcuts

• Upgrade 2007 (SP2 or later) to 2010

• Upgrade 2010 to 2013

• Upgrade 2013 to 2016

• Or buy a 3rd party tool

• Upgrade from 2007 to 2013 2016

• Mostly the same as SharePoint 2010 to 2013

• Database attach

• Don’t forget MinRole

• Don’t copy your SharePoint 2013 farm topology

• Don’t use CustomRole (without investigating MinRole first)

• Identify Site Collections in 2010 (14) mode

• Site Collections are Upgraded on Attach

• Project Server is built in

• Excel Services is replaced by Excel in Office Online Servers

• SharePoint 2016

• Are you using Cloud Search?

• Affects hardware topology

• Licensing

• Cannot be converted, must be created new

• http://www.toddklindt.com/happycssa

• SharePoint 2016 Search

Now on to the SharePoint 2013 (2016) Content

• All content databases

• More on Mysites in the next slide

• Service Apps

• BCS

• Managed Metadata

• PerformancePoint

• Secure store (need to know passphrase)

• User Profile databases

• Search administration (no index or property dbs)

• Supported Databases

• Should you upgrade them at all?

• Dip your toe into the cloud

• Need Service Pack 1 for 2013

• Office 365 licenses

• Figure out the authentication

• Not migrated automatically

• User can do it

• Use a third party tool

• MySites and OneDrive for Business

• They cannot exist on the same server

• SharePoint 2010 (2013) databases must be RTM or later (no service pack

required)

• You definitely need more hardware

• SharePoint 2010, 2013, and 2016

• Add managed paths manually before attaching databases

• Always upgrade database with root site collection first

• Try to use same URLs

• 14 = SharePoint 2010

• Quick notes

• They are awesome and you need to use them in 2013 and 2016

• Hardware is key – They must be on their own server with nothing else

• Office Web Apps require you to be using Claims authentication to work

• Requires a specific Office License (volume license)

• Office Online Server is required for Excel Services in 2016

• Go deep on Office Web Apps/Office Online Server

• Claims is dominant

• Classic is left for the golden oldies station

• Recommended to upgrade to 2016 (or 2013) and then convert to claims

• 2 major changes to the web app

• Start thinking about Azure AD

• Authentication

http://upgrade.contoso.com

Create and conver t a Classic Web App

• Boo!

• Instead from management shell you can use:

• test-spcontentdatabase –name <YourDBName> -webapplication

http://YourWebApp

• Look for fancy switches

• Works the same in 2010, 2013, and 2016

• No more preupgradecheck

• Good time to look at the App Model

• 2010 and 2013 stuff mostly just works

• Hopefully you were a good boy or girl and did everything as WSPs

• Shane’s old 2010 blog post will help you get all of the WSPs out of 2010.

Commands are the same or similar in 2013 to get the stuff in.

– http://msmvps.com/blogs/shane/archive/2011/05/05/using-powershell-to-export-

all-solutions-from-your-sharepoint-2010-farm-and-other-fun.aspx

• Features and Solutions

• Test-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication

• Mount-SPContentDatabase –Name WSS_Content_Upgrade –WebApplication

• Upgrade a database

• The commands we just ran

• One upgrade log file per upgrade

• One upgrade error log file per upgrade

• ..\15\logs (\16\logs)

• Still mount multiple databases at same time

• Look and feel are upgraded automatically in SharePoint 2016

• Things that are the same

O N E F A N A T I C A L P L A C E | S A N A N T O N I O , T X 7 8 2 1 8

U S S A L E S : 1 - 8 0 0 - 9 6 1 - 2 8 8 8 | U S S U P P O R T : 1 - 8 0 0 - 9 6 1 - 4 4 5 4 | W W W . R A C K S P A C E . C O M

© RAC K S PAC E LT D . | RAC K S PAC E ® A ND FA NAT I C A L S UPPO RT ® A RE S E RV I C E M A RK S O F RAC K S PAC E US , I NC . RE GI S T E RE D I N T H E UNI T E D S TAT E S A ND OT H E R C O UNT RI E S . | WWW.R AC K S PAC E .C OM

Thank you

Upgrade to SharePoint 2016 - Todd Klindt June... · Upgrading to SharePoint 2016 with as Little...

Documents