Pitfalls of Migrating to SharePoint 2010
-
Upload
dan-usher -
Category
Technology
-
view
3.674 -
download
3
description
Transcript of Pitfalls of Migrating to SharePoint 2010
![Page 1: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/1.jpg)
#spsbmore
WELCOMEWELCOME
SharePoint Saturday BaltimoreBaltimore, Maryland
5/12/2012Pitfalls of Migrating to SharePoint 2010Dan Usher
![Page 2: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/2.jpg)
#spsbmore
• Lead Associate, Booz Allen Hamilton• SharePoint Architect, Implementation
Engineer, and Service Monkey• 7 years of experience with SharePoint
going back to adventures with STS 2001 and SPS 2003 to the present…
• Enjoys discussions about Claims AuthZ, SmartCard AuthN, Atomic Molecular Optics & the Walking Dead
• Follows the SharePoint Credo - ADIDASAll Day I Dream About SharePoint
who am I?
DanUsher
usher
![Page 3: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/3.jpg)
#spsbmore
…and what about this guy?
![Page 4: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/4.jpg)
#spsbmore
who are you all?
How much does your service monkey know about SharePoint migrations?
Right now, not much… Ask me again in an hour…
![Page 5: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/5.jpg)
#spsbmore
Warning!!! Warning!!! Warning!!!
![Page 6: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/6.jpg)
#spsbmore
Smithers, fetch my agenda…
• Wait, why are we doing this?• Migration vs. Upgrade• 3rd Party Tools vs. OOTB Methods• AuthN / AuthZ Changes• Consolidation Considerations• Content Assessments• User Adoption, Experience and Training
![Page 7: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/7.jpg)
#spsbmore
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 8: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/8.jpg)
#spsbmore
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 9: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/9.jpg)
#spsbmore
we need a plan?
You’re pretty funny… you must be new here… we don’t do plans…
![Page 10: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/10.jpg)
#spsbmore
it’s all technical… right?
• 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 ObjectivesMake sure that you’ve successfully incorporated the technology components that help drive adoption
![Page 11: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/11.jpg)
#spsbmore
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 12: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/12.jpg)
#spsbmore
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 13: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/13.jpg)
#spsbmore
3rd Party Tools vs. OOTB
• Out of the Box– In-place– Database Attach– Hybrid
• 3rd Party– Axceler Davinci Migrator– AvePoint DocAve– Metalogix Migration Manager– Idera SharePoint Migration Suite (OEM’d by Quest)– Tzunami Migration– Kapow Solutions– Xavor Solutions
![Page 14: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/14.jpg)
#spsbmore
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 15: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/15.jpg)
#spsbmore
In-place or database attach
vs.
![Page 16: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/16.jpg)
#spsbmore
what about upgrading 2010 to service pack 1?
• Consolidating content from one 2010 farm to another?
– Upgrade from Pre-SP1 to SP1 Required
• Farm, Web Application or Content Database– PSConfig -cmd upgrade -inplace b2b -wait -force
• Site Collection Backup and Restore– Upgrade your farm to SP1
![Page 17: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/17.jpg)
#spsbmore
authentication changes
• SharePoint 2003– Classic Authentication (IIS)
• Anonymous• Basic Authentication• Integrated Windows AuthN
– NTLM & Kerberos
• Client Certificate AuthN
• SharePoint 2007– Classic Authentication (IIS)– ASP.NET Forms
• LDAP, SQL, other ASP.NET FBA solns
– Web Single Sign-On (SSO)• AD FS• Other Identity Management Systems
![Page 18: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/18.jpg)
#spsbmore
mr. fusion meet SharePoint 2010…
• SharePoint 2010• Classic• Claims• Integrated Windows AuthN with NTLM & Kerberos• No Client Certificate Authentication
• Integrated Windows AuthN with NTLM & Kerberos
• Forms Based Authentication• Trusted Identity Provider (SAML & WS-Fed)• Client Certificate Authentication through
AD FS v2
![Page 19: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/19.jpg)
#spsbmore
why would I 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 20: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/20.jpg)
#spsbmore
considerations when choosing…
• Business Functionality Issues with Claims…– PerformancePoint Services, InfoPath Forms Services, Excel
Services, etc.– Search Alerts, Search Crawling– SharePoint Explorer View
• Additional Configuration– IWA Claims - Claims to Token for Kerberos Delegation– FBA & SAML - Secure Secure Store– FBA AuthN - Membership Provider & Role Manager
registrations– SAML - Identity Provider Configuration– SAML - PowerShell for Certificate Exchange
![Page 21: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/21.jpg)
#spsbmore
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…– c:0j.c|claimprovider|useraccount != c:0#.f|claimprovider|useraccount– Similar to Domain A and Domain B user objects in Classic
• What about Multitenancy…– Single zone…– Partitioned search…– Partitioned user profiles…– Partitioned Managed MetaData…
![Page 22: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/22.jpg)
#spsbmore
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…– http://technet.microsoft.com/en-us/library/gg251985.aspx
• Client Certificate AuthN – Requires Proxy (IWA/KCD) or AD FS v2 (SAML)– Office 2007 w/o Persistent Cookies = Integration Issues
![Page 23: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/23.jpg)
#spsbmore
what about search?
• Have you updated your Information Architecture?
• Should be able to find information in any of 3 scenarios:– I know it exists and I know where it is– I know it exists, but I don’t know where it is– I don’t know if it exists
• Talk to your users! Relevancy optimization is an ongoing process.
![Page 24: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/24.jpg)
#spsbmore
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 25: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/25.jpg)
#spsbmore
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 26: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/26.jpg)
#spsbmore
content assessment
• How much data do 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 27: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/27.jpg)
#spsbmore
consolidation considerations
• Does your existing taxonomy fit in the new system?
• 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?– Do we have too many site collections in our databases?
• Customizations / Farm Solutions
![Page 28: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/28.jpg)
#spsbmore
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 29: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/29.jpg)
#spsbmore
other solution sets
• What about the Fab 40?
• What about the Productivity Hub?
• Where’d my Site Directory go?
• Where’d my SharePoint Designer Site Export go?
![Page 30: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/30.jpg)
#spsbmore
prepping for migration… disaster recovery
• Do you have plans?• Have you tested your plans?• Mirroring? Clustering?• Regression Plans• Log Shipping (wait, what?)
![Page 31: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/31.jpg)
#spsbmore
user inputs?
![Page 32: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/32.jpg)
#spsbmore
what about the users?
• 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 33: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/33.jpg)
#spsbmore
training? do we have to?
• YES!
• Training Tools– Videos– Computer based training– Formal classroom training– “Office hours” (on-going)– Productivity Hub from Microsoft
If you have to provide extensive training to your typical user, you’ve most likely made some fundamental design mistakes!
![Page 34: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/34.jpg)
#spsbmore
something to remember
SharePoint 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 35: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/35.jpg)
#spsbmore
Questions and Evals…
![Page 36: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/36.jpg)
#spsbmore
Thank you Sponsors!
![Page 37: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/37.jpg)
#spsbmore
Thanks to our Hosts!
Special Thanks to Eric and Kacey Harlan, Shadeed Eleazer and Enrique
Chumbes for putting together this event!
![Page 38: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/38.jpg)
#spsbmore
Where: Tir Na Nog201 East Pratt StreetBaltimore, MD 21202(410) 483-8968http://www.tirnanogbaltimore.com
![Page 39: Pitfalls of Migrating to SharePoint 2010](https://reader035.fdocuments.us/reader035/viewer/2022062706/55758535d8b42ae7708b458e/html5/thumbnails/39.jpg)
#spsbmore
Reference
• What's new in upgrade• Determine upgrade approach• SharePoint Server 2010 capacity management:
Software boundaries and limits
• Video demos and training for SharePoint Server 2010
• SharePoint 2010 Adoption Best Practices