Migration Consideration for SharePoint Online - PowerPoint Presentation

Slide1

Migration Consideration for SharePoint Online

Garth LukeElaine van Bergen

OSP316A Slide2

Garth

Luke

@

Garthluke

Garth.luke@avepoint.com

Text/Icon/PicSlide3

My Home

SHARE 2012

|

3

Silicon Valley – Northern CaliforniaSlide4

Elaine

V

an Bergen

@

laneyvb

Elaine.vanbergen@obs.com.au

Slide5

Your Migration Roadmap for Success!Slide6
Slide7

This is your chance to revisit your approach to Information management in your business:

Business need : Where can SharePoint fit into the IM Strategy?Align technology to IM StrategyUnderstand your data silos and plan to incorporate them into your strategy

Why a Business Case?Slide8

Why SharePoint 2013 ?

Business Intelligence

Excel BI and Services

Visio Searches

PerformancePoint Services

Search

Personalized search results

Rich contextual previews

Enterprise Content ManagementeDiscoveryTeam FoldersSlide9

Why SharePoint 2013 ?

Social

Communities

Discussions

Blogs

BYOD

Classic and contemporary mobile views

Automatic redirectionMobile Web Apps

APP ModelNew APP modelVariety of scopeSlide10

O365 Benefits

Simplified DeploymentAllocate resources towards driving business value rather than maintaining infrastructure

Predictability

Easier to forecast cost of platformFaster UpdatesSharePoint Online updated before on-premises90 day release cyclesIntegrationExchange, Lync, Project, DynamicsSlide11

O365 Concerns

Lack of ControlCannot deploy full-trust solutions

Cannot opt-out of updates

Lack of FlexibilitySharePoint 2013 OnlyNo RBS (Remote BLOB Storage)RegulationsCompliance, data sovereignty Data Loss

No access to data without connectionSlide12

Understanding Hybrid

Workloads are divided across separate SharePoint environments

Gradual transition to cloud

In most cases today, the integration

is

not quite seamless On Premise Farm

Cloud (private or public)Slide13
Slide14

How organisations

thinkSlide15

Risk Assessment

Don’t just focus on what you can see:

Risk

Awareness

Risk

Ignorance

Regularly accessed data

Un-accessed data

Data cleanup

Dark Data

Migrating old data expensive

Metadata tagging moves with data

Know your classification requirementsSlide16

Information dynamics

D

ocument types

Document sizes and average sizes

Smallest and largest sizes

Content size count

Overall document count

Database counts

Site and site collection counts per content databaseSlide17

Information Gathering Commands

Test-

SPContentDatabase

Both 2010 and SP2013 versionsSTSADM -o PreUpgradeCheck (no longer exists in 2013)

Third Party ToolsSlide18

How you should thinkSlide19

Lifecycle

MetadataPermissions

Information ManagementSlide20
Slide21

Upgrade and migration strategies

Upgrade/migrate to the cloud

Upgrade to next version

– sequential (recommended

)

Leapfrog to the latest versionSlide22

Upgrade to the Next Version

Things to look out for:

Storage requirements

customisations & Missing

files

Changes in supportabilily limitsOrphaned sitesPatch level (not up to date)Platform changes (Search, OWA, etc.)Authentication type (Classic, Claims, etc...)The only built-in method supported and provided by the productSlide23

Leapfrog to the latest version

Things to look out for:

Storage requirements

customisations & missing

files

Changes in supportabilily limitsOrphaned sitesFunctionality in useRunning workflowsDepricated featuresLoad on resources (hardware and people)Requires 3

rd party

tools or multiple upgradesSlide24

Benefits

High Availability/Disaster Recovery is the provider’s responsibilityMaintaining current software and patch levels (evergreen, etc.)

Upgrade/Migrate to the Cloud

Things to look out for

Difference in capabilities

Not all workloads available in the cloudCertain workloads are challenging in hybrid modeConnectivity to other systems and their locationsExisting solution-specific customisations/managed codeLicensing costs for 3rd party migration tools, support, etc.Future plans with regards to customisations, integration, etc.Amount of data to be migrated and throughput targets during process

Requires 3

rd party tools or manual migrationSlide25

What workloads are currently in use?

What is the size of environment?

Technical ConsiderationsSlide26

How

customised is the implementation?External Applications interfacing with SharePoint?

Technical ConsiderationsSlide27

Changing authentication model?

Plan to upgrade authentication model to claims

Technical Aspects – Authentication ModelSlide28

Organisational Aspects -

Environment & Skills

Who owns

the

environment?

Who manages the environment?Who has access to the environment’s servers?How skilled is your organization on the new version of SharePoint?Operations teamDevelopment teamSupport organizationSlide29

Project Management/Sponsorship

Project Management Skills & Experience

Support within the Organization

Ensure adequate level of supportExternal or InternalProject Management approach (ITIL, Agile, Ad-Hoc

, etc.) Slide30

Can it be removed

Will it work in target environmentThird Party or In HouseDo you have the code ?

Is it under support

Customisation governanceSlide31
Slide32

Disruption

Defined as any significant change that:

Requires changing client software to match server

Requires retraining to use existing abilitiesRequires refactoring/replacement of customisations

Not the same as downtimeUse

Deferred Site Collection Upgrade to forestall most disruptionSlide33

Downtime

No such thing as zero downtime!!!Possible

to reduce downtime using mitigation

processesUse Test runs to predict outagesSlide34

Performance

Know what performance you have and what you want

Audit

existing hardware and performanceAudit existing contentSlide35

URL Changes

Should avoid URL changes whenever possibleStacking URL changes with upgrade can complicate experience

Plan to not change URLs in the futureSlide36

Notification Plan

Plan to inform users about upcoming upgrade requirements/events

Include info on what will happen

Indicate when upgrade will occurProvide directions if using self-service upgrade abilitiesIndicate when upgrade must be completed byIndicate when upgrade is finishedSlide37

Test Environment Considerations

Be careful of impacting live environments from test onesTry to prevent/minimize URL changes

Use proper hardware and content to determine timingSlide38

Expectations From Testing

Understand upgrade methods and processes

Understand performance and downtime

mitigationGain experience and confidence in troubleshooting and validationSlide39
Slide40

How to Migrate to OnlineSlide41

Understand the capabilities of the target platform

How does the target differ from what you have nowService DescriptionsC

ustomisation

GuidancePlanning: Know where you are goingSlide42

Third party tools – need to know:

CostsCapabilitiesNot everything can be migrated

Some things can be migrated but require planning

Can you upgrade in-flightWhat kind of throughput can you get in your environmentHow can you manage deltas

Need a POC or Pilot

Planning: How do I get there?Slide43

Support

HelpOperationsProcesses

Site Provisioning

Customisation modelsPlanning: Organisational changesSlide44

Sunset

customisationsWhat remediation needs to be done in legacy production prior to migration

Develop a map between the existing and target Information Architectures

Cleanup - archive or deletePrepare: ContentSlide45

Verify capabilities

Understand the tools – test settingsVerify fidelity

Verify throughput

Involve stakeholders in quality assurance and acceptanceIncorporate learningsPrepare: Conduct the pilotSlide46

Script everything possible

Do everything possible to prevent the introduction of errorsCutover strategy

Freeze periods

Gradual or big bangPrepareSlide47

Migrate sites

Freeze source farm – read only if possibleSync deltas

Testing and acceptance

Address defectsCutoverSupportMigrateSlide48

SharePoint 2010 – 2013 HybridSlide49

Why ?

SharePoint 2013 has lots of improved functionality

Business wants these ahead of full upgrade due to

Time/Budget constraintsLots of customisations

Training and change managementSlide50

Published Services OnlySlide51

Supported Services

Managed Metadata

*

Metadata only not Content Type HubUPSSearchBCSSecure StoreSlide52

Design Considerations

Old user interface or New functionality

Latency /Location of farms

Security of environments

LicensingSlide53

Merged FarmsSlide54

Staged MigrationSlide55

Implementing Services Upgrade

Gather applicable services settings on source

farm

Backup services databases on source

farm

Ensure service application pools created firstCreate each service application and proxyStart service instances only after service is created with upgraded databasesSlide56

Share service Applications

Exchange trust certificates

Publish service application

Grant permissions to SA

Connect to remote farm

Add proxy to web app2013 only configure server to server authenticationSlide57

SharePoint 2013 On Premises UpgradeSlide58

2013 Server Prerequisites

2010 or earlier SharePoint products must not be installed

To use existing 2010 SharePoint Farm hardware:

Uninstall and CleanRebuild OSSlide59

Client Minimum

Software Requirements

Office 2010 or Office 2013

SharePoint Designer versionWeb BrowserSlide60

Databases Supporting Database Attach Upgrade

Content databases (->2010 and ->2013)

Profile database (->2010 and ->2013)

Project databases (->2010 and ->2013)Note: Four 2010 merged to one during upgrade to 2013Search admin databaseSocial databaseSync Database – but why ???Managed Metadata database

Secure Store databaseNote: Passphrase required to retain passwords in store

Access databasesNote: Supported for B2B upgrades onlySlide61

Databases Not Supporting Database Attach Upgrade

Configuration database

Unsupported for both V2V and B2B upgrades

Has never been supported in prior versionsSearch index databasesUnsupported for V2V upgrades onlySlide62

Upgrade ImprovementsSlide63

Deferred Site Collection Upgrade

Allows existing 2010 site collections to work unchanged in

SP2013

Replaces Visual UpgradeRequires deep backwards compatibilityDefault state for all site collections in upgraded databasesSlide64

Page Rendering Coexistence

SP2013 App Process Space

SP2013

Config

Database

SP2013 ContentDatabase

SPSite

SPWeb

SPSite

SPWeb

WSE/14/Templates

WSE/15/Templates

/_layouts/

/_layouts/15/

WSE/14/Templates/Layouts

WSE/15/Templates/Layouts

Page

Page

Code

Code

14

Assembly

Redirect

Policy

15

Assembly

In-process request routing

14

Mode

Site Page

15

Mode

Site PageSlide65

Site Collection Health Checks

Rule based health checks

Looks for common known

issuesSite collection level scoped toolRuns automatically before Site Collection version to version upgradeSlide66

Customizations Gathering

Solutions

Should always have a build-out directory for FT solutions

Don’t forget admin deployed InfoPath Forms

Sandbox solutions are fineOther stuff

MSI deployed componentsXCopy or manually deployed features/files/changesUse directory comparisons to be sure you have it allSlide67

Customization Categories and TypesSlide68

Implementing Services Upgrade

Gather applicable services settings on source farm

Backup all applicable services databases from source farm

Ensure service application pools are created firstCreate each service application and proxyStart service instances only after service is created with upgraded databasesSlide69

Example Of Managed Metadata Service Provisioning

$applicationPool

= Get-

SPServiceApplicationPool -Identity "SharePoint Service Application"# Create Managed Metadata service and proxy$sa = New-SPMetadataServiceApplication

-Name "Managed Metadata Service Application" -ApplicationPool

$applicationPool -DatabaseName "ManagedMetadata_Upgrade_DB"if ($sa) {New-SPMetadataServiceApplicationProxy -ServiceApplication $sa -Name "Managed Metadata Service Application Proxy" -DefaultProxyGroup #Start Managed Metadata serviceGet-SPServiceInstance | Where-Object {$_.TypeName -Eq "Managed Metadata Web Service"} | Start-SPServiceInstance}Slide70

Prior to DB Attach

Setup web applicationsManaged Paths

Alternative Access Mappings

CustomisationsSlide71

Upgrade Related PowerShell CommandsSlide72

Upgrade Log Failures

Should always review logs after any upgrade

Start

at top of log and work downwardsOrder of operations in reviewing logsOrder of operations is solving issuesSlide73

My Site Host Upgrades

My Site Host works in both 14 and 15 mode

Once My Site Host is upgraded to 15

modeAll new personal sites will be created in 15 modeAs users visit My Site Host, their sites are added to upgrade queue

If upgrade of personal site fails, it will be reattempted after a delaySlide74

Governance

Determine control and rollout of upgrade abilities

Web

Application and Site Collection variables control thisSlide75

Validate Predetermined Sites

Pick certain sites in advance and ensure they work as expected before upgrade

As a best practice include at least one of every site definition and feature in use

Take care to review high impact/high profile sitesSlide76

Create New Validation Targets

Create new Site Collections/WebsActivate features

Create new pages

Add web partsCreate new libraries/listsRecommend best practice is to create 2x for each template migratedSlide77

Verify Services FunctionalitySlide78

Other areas for testing

SecurityExternal Data

Customisations

FunctionalVisualSlide79

SharePoint 2013 – O365 HybridSlide80

SharePoint 2013 and O365

Configure environments

Setup identity management

Configure specific function

Search

BDCDuetSlide81
Slide82
Slide83
Slide84

Supported options

Search

Inbound – SharePoint 2013 queries Online and returns results

Outbound – Online queries SharePoint 2013 and can return resultsTwo way – Both

BCS /Duet

Inbound Two waySlide85
Slide86

Requirements - SharePoint

SharePoint 2013 farmOffice 365 tenant of E1 (search only) , E2 or E3Slide87

Requirements - Authentication

AD DS domain with 2008+ functional level

Servers for AD FS 2.0

Server for Dir SyncWildcard cert by public authority for inboundSupported reverse proxy (TMG)Slide88

Tips

Step by StepNon-Prod ?

Allow for change control

Don’t get the ‘SPAdmin’ to do this !!Slide89

Steps – Search example

Configure infrastructureConfigure SSO

Create result source using remote service

urlSetup query rule to include result blockSlide90

References

Upgrade

service applications

http://technet.microsoft.com/en-us/library/ee731990.aspx Upgrade services farms http://technet.microsoft.com/en-us/library/cc303435.aspx

Configure shared services cross farms

http://technet.microsoft.com/en-us/library/ff621100.aspxSharePoint 2013 and O365 hybrid http://technet.microsoft.com/en-us/library/jj838715.aspx Slide91

Your Migration Roadmap for Success!Slide92

Developer Network

Resources for Developers

http://

msdn.microsoft.com

/en-au/

Learning

Virtual Academy

http://www.microsoftvirtualacademy.com/

TechNet

Resources

Sessions on Demand

http://channel9.msdn.com/Events/

TechEd/Australia/2013

Resources for IT Professionals

http://technet.microsoft.com/en-au/Slide93

Keep Learning

Keep up to date with all the latest Office 365 information at

http://

ignite.office.com

Get

on top of your pilot using the

FastTrack

deployment process

http://fastTrack.office.com

Trial

Office 365

http://office.microsoft.comSlide94

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.