pitfalls of migration to sharepoint 2010

47
Pitfalls of Migrating to SharePoint 2010 SPTechCon Boston 2012 Scott Hoag and Dan Usher

Upload: dan-usher

Post on 12-May-2015

236 views

Category:

Technology


3 download

DESCRIPTION

If you've suddenly b

TRANSCRIPT

Page 1: Pitfalls of Migration to SharePoint 2010

Pitfalls of Migrating to SharePoint 2010SPTechCon Boston 2012Scott Hoag and Dan Usher

Page 2: Pitfalls of Migration to SharePoint 2010

who are we?

Infrastructure Consultant at Applied Information Sciences

8 years of experience with the SharePoint platform from MCMS 2002 to SharePoint 2010 today

Enjoys discussions about user adoption, search, and world peace

Recently returned from a trip around the world…

ScottHoag

ciphertxt

Page 3: Pitfalls of Migration to SharePoint 2010

who’s that other guy?

Lead Associate at Booz Allen Hamilton

7 years of experience with SharePoint going back to adventures with STS 2001 and SPS 2003 with fun in the SharePoint 2007 and 2010

Follows the SharePoint Credo - ADIDASAll Day I Dream About SharePoint

Enjoys discussions about Claims AuthZ, SmartCard AuthN, Atomic Molecular Optics & the Big Bang Theory

Enjoys whey protein biscuits

DanUsher

usher

Page 4: Pitfalls of Migration to SharePoint 2010

introductions

Page 5: Pitfalls of Migration to SharePoint 2010

a few ground rules…

Page 6: Pitfalls of Migration to SharePoint 2010

redundant statement is redundant!

http://xkcdsw.com/2502

Page 7: Pitfalls of Migration to SharePoint 2010

Smithers, fetch my agenda… Wait, why are we doing this? Migration vs. Upgrade 3rd Party Tools vs. OOTB Methods Consolidation Considerations Content Assessments User Adoption, Experience and Training AuthN Changes Entropy vs. Order

Page 8: Pitfalls of Migration to SharePoint 2010

wait, why are we doing this? End User Capabilities

PerformancePoint, Access Services, BCS, Office Web Apps, PowerPivot, Sandboxed Solutions

Architectural Reasons Services Architecture, Scalability, PowerShell,

Disaster Recovery, Multitenancy, Claims AuthN/AuthZ

Licensing, Maintenance and Supportability Because we can…

Page 9: Pitfalls of Migration to SharePoint 2010

migration vs. upgrade Data migration is the process of transferring data

between storage types, formats, or computer systems. 1

System migration involves moving a set of instructions or programs from one platform to another, minimizing re-engineering. 2

Migration of systems can also involve downtime, while the old system is replaced with a new one.

The term upgrade refers to the replacement of a product with a newer version of the same product. 3

1 http://en.wikipedia.org/wiki/Data_migration2 http://en.wikipedia.org/wiki/System_migration 3 http://en.wikipedia.org/wiki/Upgrade

Page 10: Pitfalls of Migration to SharePoint 2010

devising your way ahead

Page 11: Pitfalls of Migration to SharePoint 2010

we need a plan…

You’re pretty funny… you must be new here… we don’t do plans…

Page 12: Pitfalls of Migration to SharePoint 2010

what’s that? a plan? Make sure that you’ve successfully

incorporated the technology components that help drive adoption

Implement a Training Plan Implement a Communications Plan Decide on a Content Migration Strategy Have a User Support Plan Provide Incentives and Rewards Enable End-user Feedback Align Business Objectives

Page 13: Pitfalls of Migration to SharePoint 2010

lets get technical… Hardware and Software RequirementsWeb Front End(s)

Component

Minimum Requirement

Hardware 64-bit, four cores

Memory 8 GB

Operation System

Windows Server 2008 R2 with SP1Windows Server 2008 with SP2

SQL Server(s)

Component

Minimum Requirement

Hardware 64-bit, four cores (small deployments)64-bit, eight cores (medium deployments)

Memory 8 GB (small deployments)16 GB (medium deployments)

Operation System

Windows Server 2008 R2 with SP1Windows Server 2008 with SP2

SQL Server SQL Server 2008 R2SQL Server 2008 with SP1 (SP1) and CU2 (or CU5 or later)SQL Server 2005 with SP3 and CU3

Page 14: Pitfalls of Migration to SharePoint 2010

other preparation

Other Resources TechNet Documentation (Capacity Planning /

Hardware and Software Requirements) Blogs (Joel Oleson, Todd Klindt and Shane

Young) Axceler Migration Toolkit (no cost)

Version Migration Preparation

SharePoint Portal Server 2001

Hire a consultantConsider a 3rd party migration tool

Windows SharePoint Services 3.0

Hire a consultantPrescan.exe / ReGhost.net / GhostHunter Web Parts

Office SharePoint Server 2007

STSADM –o preupgradecheck

SharePoint Server 2010 test-spcontentdatabase cmdlet

Page 15: Pitfalls of Migration to SharePoint 2010

3rd party tools vs. ootb

Out of the Box In-place Database Attach

3rd Party Axceler Davinci Migrator AvePoint DocAve Metalogix Migration Manager Idera SharePoint Migration Suite / Quest

Migration Manger Tzunami Migration Kapow Solutions Xavor Solutions

Page 16: Pitfalls of Migration to SharePoint 2010

in-place or database attach In-place

Same operating system (x64 required) Same hardware (x64 required) Content and settings come along Farm is offline while upgrading

Database Attach New hardware Only content comes along Content is not available while upgrading, but you get

to pick the order! Parallel upgrades of content Combine multiple farms

Hybrid Database attach read-only databases In-place upgrade with detached databases

Page 17: Pitfalls of Migration to SharePoint 2010

in-place or database attach

vs.

Page 18: Pitfalls of Migration to SharePoint 2010

side bar

Page 19: Pitfalls of Migration to SharePoint 2010

what about service pack 1 upgrade? You want to consolidate content from one

SharePoint 2010 farm to another? Upgrade from Pre-SP1 to SP1 Required

Farm, Web Application or Content Database

Site Collection Backup and Restore Upgrade your farm to SP1

> PSConfig -cmd upgrade -inplace b2b -wait -force

Page 20: Pitfalls of Migration to SharePoint 2010

timeout…

Page 21: Pitfalls of Migration to SharePoint 2010

considerations

Page 22: Pitfalls of Migration to SharePoint 2010

authentication changes

Classic AuthN Claims AuthN and AuthZ

Integrated Windows AuthN with NTLM / Kerberos

Forms Based AuthN

Trusted Identity Provider (aka SAML & WS Fed)

Page 23: Pitfalls of Migration to SharePoint 2010

why would you choose claims auth? It’s the new shiny… Microsoft recommends it

for new implementations… Multiple Authentication

Providers – One URL… Handy for extranets and

partner access… Role Based and Attribute

Based Access Control… Vive la Fédération!

Page 24: Pitfalls of Migration to SharePoint 2010

considerations when choosing… Business Functionality Issues with Claims…

PerformancePoint Services, InfoPath Forms Services, Excel Services, etc.

Search Alerts, Search Crawling SharePoint Explorer View

Additional setup required for IWA Claims – Claims to Token for Kerberos Delegation

Secure Store comes in handy with FBA & SAML… Forms Based AuthN – Still have a Membership

Provider and Role Manager to register within multiple web.config files

When setting up a Trusted Identity Provider there’s a bit of work that must be done… Get ready to use some PowerShell for certificate

exchange…

Page 25: Pitfalls of Migration to SharePoint 2010

more considerations… Be prepared to figure out your AuthZ side of

things IWA leverages NT Security Token Forms Role Manager information mapped Group Claims information

Identities with one Claim Provider aren’t the same as with another…

Similar to Domain A and Domain B user objects in Classic

Multitenancy Single zone… Partitioned search… Partitioned user profiles… Partitioned Managed Metadata…

$> i:0#.w|claimprovider|useraccount != i:0#.f|claimprovider|useraccount

Page 26: Pitfalls of Migration to SharePoint 2010

what’s that mean to me? Classic to Classic

Mapping “should” stay intact Classic to Claims

Mapping update required Classic Provider Identity to Claim Provider

Identity Migrate a web application… Client Certificate AuthN

Requires Proxy (IWA/KCD) or AD FS v2 (SAML) Office 2007 w/o Persistent Cookies = Integration

Issues

Page 27: Pitfalls of Migration to SharePoint 2010

authN/authZ decisions

Page 28: Pitfalls of Migration to SharePoint 2010

what about search?

INFORMATION ARCHITECTURE

Find Information

Navigate Search

I know how to find it

I don’t know how to find it

but I know it’s out there

I don’t know if it’s out there

COMMUNICATE

Page 29: Pitfalls of Migration to SharePoint 2010

what about custom solutions? Web Templates and Site Definitions BDC -> Application Registry Database Custom Solutions

.Net version – recompile for appropriate framework

Farm Solutions to Sandboxed Solutions Third Party Tools

Page 30: Pitfalls of Migration to SharePoint 2010

what about workflows? Remember to breathe… In-place upgrades are your best bet Third Party Tools with Full Fidelity

Axceler AvePoint Metalogix … and others?

Gotchas Not using the latest and greatest Workflow History Cleanup

Page 31: Pitfalls of Migration to SharePoint 2010

content assessment How much data we have and where does it

reside? If we’re migrating, how will the transfer occur? How long will it take?

Considerations for Search Corpus size Multilingual?

Does your content need to change in the new system? Choice fields vs. Managed Metadata Content Type authoring in a Content Hub?

Page 32: Pitfalls of Migration to SharePoint 2010

consolidation considerations Do you have existing systems / applications

that will also be migrated into SharePoint? Do we need to (un)consolidate?

Single site collections that need to be broken apart into multiple collections

Sites that need to be promoted into site collections

Too many site collections in our databases Does your existing taxonomy fit in the new

system? Customizations / Farm Solutions

Page 33: Pitfalls of Migration to SharePoint 2010

still more content to assess… Identify 3rd party tools/web parts/etc. that

are installed in your current farm Is there a 2010 version available? Is the functionality now available OOTB in

SharePoint (Ratings, Faceted Search, …) Don’t forget your non-SharePoint data..• Lotus• WebSphere• Drupal• DotNetNuke

• Alfresco• Legacy HTML• Non-OCR’d Text Documents• Orchard

Page 34: Pitfalls of Migration to SharePoint 2010

other solution sets

Site direcotry

Page 35: Pitfalls of Migration to SharePoint 2010

other solution sets

Site direcotry

fabulous 40

Page 36: Pitfalls of Migration to SharePoint 2010

other solution sets

Site direcotry

fabulous 40

productivity hub

Page 37: Pitfalls of Migration to SharePoint 2010

other solution sets

Site direcotry

fabulous 40

productivity hub

spd site export

Page 38: Pitfalls of Migration to SharePoint 2010

disaster recovery impacts Do you have plans? Have you tested your plans? Mirroring? Clustering? Regression Plans? Log Shipping (wait, what?)

Page 39: Pitfalls of Migration to SharePoint 2010

user experience Visual Upgrade (aka v3) is familiar. The ribbon

is not. Are you deploying the Office Web Applications?

(Co-authoring can be fun!) Multiple item selections. Refinement panels.

Metadata navigation. Oh my! What about your licensing? Enterprise?

Standard? Office Workspace? Groove? Mobile? Oh, you are upgrading your Office Clients too

right?

Page 40: Pitfalls of Migration to SharePoint 2010

YES!

Training Tools Videos Computer based training Formal classroom training “Office hours” (on-going) Productivity Hub from Microsoft

If you have have to provide extensive training to your typical user, you’ve most likely made some fundamental design mistakes!

training? do you have to?

Page 41: Pitfalls of Migration to SharePoint 2010

entropy vs. orderEntropy - /ˈentrəpē/ A thermodynamic quantity representing the

unavailability of a system's thermal energy for conversion into mechanical work, often...

Lack of order or predictability; gradual decline into disorder.

Order - /ˈôrdər/ The arrangement or disposition of people or

things in relation to each other according to a particular sequence, pattern, or method.

Page 42: Pitfalls of Migration to SharePoint 2010

closing thought

Page 43: Pitfalls of Migration to SharePoint 2010

something to rememberSharePoint Implementations today consist of a race between Architects, Developers and IT Pros striving to build well planned out, bigger and better idiot-proof solutions, and the Universe trying to produce requirements of entropy with bigger and better idiots.

…so far, the Universe is winning.

Page 44: Pitfalls of Migration to SharePoint 2010

questions

?

Page 45: Pitfalls of Migration to SharePoint 2010

evaluations