spscbr - pitfalls of migrating to sharepoint 2013
DESCRIPTION
Organisations of all sizes are begging their technical departments to set up SharePoint 2013 so that they're able to make use of some of the capabilities introduced within the SharePoint 2013 platform. While designing, implementing, configuring and deploying a system in and of itself has its own set of challenges, migrating into that shiny, new SharePoint environment can be even more difficult. In this session, Scott will share his experiences and lessons learned along with tips, tricks and pointers for ensuring that you've considered the various aspects and challenges that arise during a migration effort. Further, as a bonus we'll work though how to not fall prey to some of these pitfalls but rather be able to show that you're a well-rounded professional that's thought things through before pressing the enter key.TRANSCRIPT
Gold Sponsors Silver Sponsors Bronze Sponsors
Pitfalls of Migrating to SharePoint 2013
Scott HoagApplied Information Sciences
Migration versus Upgrade
Why Upgrade?
3rd Party versus OOTB
Consolidation
Content, Content, Content
Authentication
User Adoption
Agenda
Data migration is the process of transferring data between storage types, formats, or computer systems.
System migration involves moving a set of instructions or programs from one platform to another, minimizing re-engineering.
The term upgrade refers to the replacement of a product with a newer version of the same product.
http://en.wikipedia.org/wiki/Data_migration
http://en.wikipedia.org/wiki/System_migration
http://en.wikipedia.org/wiki/Upgrade
Why Should We Upgrade?
End-user improvements
Architectural considerations
Licensing, Maintenance and Supportability
Do you have a…
Training Plan
Communications Plan
Content Migration Strategy
User Support Plan
Business Case
Technical Requirements for SharePoint
Technical Requirements for SQL
must
Other Resources
Platform Considerations
Version Migration Preparation
SharePoint Portal Server 2001 Hire a consultant
Consider a 3rd party migration tool
Windows SharePoint Services 3.0 Hire a consultant
Prescan.exe / ReGhost.net / GhostHunter Web Parts
Office SharePoint Server 2007 STSADM –o preupgradecheck
SharePoint Server 2010 Test-SPContentDatabase cmdlet
SharePoint Server 2013 Test-SPContentDatabase cmdlet
Other ResourcesTechNet Documentation (Capacity Planning / Hardware and Software Requirements)
Blogs
Metalogix Migration Expert (no cost)
Still more to consider…
SharePoint in the Cloud
Hybrid
Windows Server Support
SQL Server Support
Browser Support
Disaster Recovery Impacts
Do you have plans?
Have you tested your plans?
Mirroring? Clustering? Log Shipping?
Regression Plans?
3rd Party Tools versus Out of the Box
Out of the Box
3rd Party
Database Attach Upgrade
Only Business Data Connectivity
Managed Metadata
Performance Point
Search Service
Secure Store
User Profile Service
Know your content…
How much data we have and where does it reside?
Considerations for Search
Does your content need to change in the new system?
What About Search?
You’re not done yet…
3rd Party Tools
Non-SharePoint Data
Authentication Changes
Classic AuthN Claims AuthN and AuthZ
Integrated Windows AuthN with NTLM / Kerberos
Forms Based AuthN
Trusted Identity Provider (aka SAML &
WS Fed)
It’s the new old 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!
Why Choose Claims?
Business Functionality Issues with Claims
Additional setup required for IWA Claims
Secure Store can be handy for FBA & SAML
Forms Based AuthN
Your developers should give you a TIP!
Considerations When Choosing…
Classic to Classic
Classic to Claims
Client Certificate AuthN
What is the Impact?
AuthN/AuthZ Decisions
Pitfall Mitigation Check
Project Plan
Implementation Strategy
Training Plan
Communications Plan
Content Inventory
Defined IA/Taxonomy
Defined AuthN/AuthZ Strategy
Scriptable/Repeatable Process
Tested x3 (at least)
Upgraded Browsers
Upgraded Office Clients
Acquired New Hardware
Built for Extensibility
Aligning to The Business™
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.
Question and Answer
Gold Sponsors Silver Sponsors Bronze Sponsors
Thanks for listeningRemember to submit your feedback so you go in the draw to win prizes at the end of the day
Reference
Geoff Evelyn - Sample Project Plans
Technical Diagrams for SharePoint 2013
Hardware and software requirements for SharePoint 2013
Upgrade Service Applications to SharePoint 2013
Migrate from classic-mode to claims-based authentication in SharePoint 2013
Checklist for database-attach upgrade (SharePoint 2013)
Claims Based AuthN Resources (TechNet Wiki)
Plan for user authentication methods in SharePoint 2013
Discover SharePoint
Productivity Hub
Office 365 Change Management Guide for the Enterprise
AIIM Industry Watch – SharePoint 2013