sharepoint 2010 upgrade planning
DESCRIPTION
In this presentation, we discuss benefits of upgrading to SharePoint 2010, hardware requirements, impacts of upgrade, methodologies for upgrade from MOSS 2007 and SPS 2003TRANSCRIPT
1ironworks.com | 804.967.9200
SharePoint Upgrade Planning
2
Ironworks Introduction
Key Facts:
• Started in 2001• 300 Employees• Offices in Richmond (HQ), Washington DC, Raleigh, Charlotte, Atlanta, Minneapolis• Key Industries: Healthcare, Government, Not for Profit and Financial Services
Project-based technology consulting firm with key strengths in:
• Enterprise Content Management / Portal Integration• Business Intelligence• PMO / Management Consulting• Interactive User-Centric Design
Key Differentiators:
• Competitive Rates, Senior Resources, Loyal Clients, Results and Delivery Driven
3
About The Presenter
Chaitu MadalaSharePoint Architect
Blog: http://www.goodbadtechnology.blogspot.com
• Over 8 years of experience in development and implementation of web and windows-based IT solutions
• Background in SharePoint, WCF, Windows Workflow, InfoPath Forms Services, ASP.NET, ADO.NET, XML, XSLT, AJAX, JavaScript, and SQL
• Numerous SharePoint engagements: Extranets, Intranets, Publicly-Facing Web Sites, Enterprise Search, Document Management, Web Part Development, and Custom Applications
• Bachelor of Science in Computer Science• Microsoft Certified Professional (MCP) for SharePoint 2010• Microsoft Certified Technology Specialist (MCTS) for MOSS 2007• Brainbench Certified in SPS 2003, C# & ASP.NET
4
• SharePoint 2010 Overview
• Benefits to Upgrading
• Upgrade process
• Determine readiness of infrastructure
• Allocate resources to perform upgrade
• Impact of upgrade
• Pre-upgrade checklist
• Performing the upgrade from MOSS 2007
• Performing the upgrade from SharePoint 2003
Agenda
5
SharePoint 2010 Overview
6
Benefits to Upgrading
New Features
Opportunity To Revisit System Architecture
Stay on SharePoint Release Schedule
BI Dashboards
2 way BCS
Ribbon UI Office Integration
Cross Browser Support
Managed MetadataSocial Networking
PowerShell
FAST Search
7
The Upgrade Process
Identify Current State
Plan & Prepare
Identify Impact on Services
Pre-Upgrade Checks
Perform Upgrade
Post-Upgrade Checks, Issue Resolutions
Deploy Customizations & Apply Configurations
8
Step 1 – Identify Current State
Software• SharePoint 2007 SP2
Update
Hardware• 64 Bit OS• Windows Server 2008 /
2008 R2• SQL Server 2005 SP3/
2008 SP1/R2• RAM
Resources• Migration Schedule• Training (User &
Admin)• Allocate Developers• Budget
Environment• Staging Environment
• Baseline Infrastructure and Resources
9
Step 2 – Plan and Prepare
• Training, governance, compliance, business value planning, adoption and other elements should be a critical part of any upgrade strategy
• Organizations need to realize that to successfully upgrade to SharePoint 2010 you have to look at the upgrade from a holistic fashion and not just consider technical issues
• Leverage the planning worksheet to take an inventory of the current environment. The inventory can be used later as a checklist during upgrade
– http://technet.microsoft.com/en-us/library/cc262451.aspx
10
Step 3 – Identify Impacts on Services
• Search
• Business Data Catalog
• Profile/MySites
• InfoPath Forms
• Single Sign-On
• Excel Services
11
When using in place upgrade:
• Each Shared Service gets upgraded into a new service app
• Web application associations are preserved– A proxy is created for each service app
• New databases are created as needed
When using database attach
• Personalization (user profile, My Sites) is upgraded
• Must manually reconfigure– Search, InfoPath, BDC, Excel Services
Upgrading Shared Services
12
Upgrade Impact On Search
• Search settings are not preserved during a database attach upgrade.
• Consider Hybrid approach if search settings are too important
• No more SSP in SharePoint 2010
• No longer possible to configure a dedicated WFE for crawling through the UI
• New Search Service Application for each SSP
• Crawl Server in SP 2010 contains one or more crawl components that can crawl content independently of one another
• Changed search databases in SharePoint 2010:MOSS 2007 SharePoint 2010
SSP Database Search Administration DatabaseSearch Database Crawl Database
Property DatabaseSearch Administration setting stored in SSP Database
One Administration Database / Search Service Application
Single Crawler Multiple Crawlers
13
Upgrade Impact On Other Services
• In-Place Upgrade– All of the services infrastructure and the settings for the services
themselves are upgraded
• Database Attach Upgrade– Most service Settings will need to be reconfigured– Services that are affected:
User Profiles My Sites InfoPath Forms Services Excel Services BDC Single Sign-On (SSO) Search
14
Step 4 – Pre-upgrade checklist
Microsoft provides utilities against the legacy system to evaluate the readiness for upgrade
PreUpgradeCheck
• Run against SharePoint Server 2007 (source)• Available as part of SharePoint Server 2007 SP2• Identifies any issues with the environment.• Checks for database schema changes, server version,
etc…
Test-SPContentDatabase
• Run against Server 2010 (destination)• Test the source database in designation environment
before doing actual upgrade• Verify all customizations referenced within the content
database are also installed in the web application
15
Step 5 –Perform The Upgrade
There are multiple upgrade methods which each require the Visual upgrade to complete the process
Visual Upgrade
In-Place
Database Attach
Hybrid
After Visual Upgrade complete, conduct • Master Page Upgrade• Page Layouts Upgrade
16
Pros• All at once• Easy• Upgrades configuration databases, services• Most settings will be preserved• Resume upgrade if an error occurs
Cons• Most risky – No rollback• Slowest• Prone to failure• Will have down time
Tips• Take proper backups before you start – Farm, VM,
Database• Issue with Profile upgrade not using ForeFront and creating
a BCS connection
In-place Upgrade
17
Pros• Safer• Faster• Requires no downtime. Can be done in a
separate parallel farm.• Can perform multiple database upgrades
simultaneously
Cons• Only upgrades content, environment must
be reconfigured
Tips• Plan properly• Change the DB mode to read-only before
the upgrade• Copy all the file system customizations
from 12 hive into 14 hive• Check status of upgrade by going to
Central Administration > Upgrade and Migration > Check upgrade status
Database Upgrade
18
Pros• Upgrades multiple databases in parallel
Cons• Will have downtime
Tips• Detach databases before upgrade
Hybrid Upgrade
19
• SP 2010’s look and feel
• Runs in a separate process
• Sites can be upgraded one at a time
• Farm / Site Admin Controlled– Web Level Setting
• Offers 3 options– Continue with SP 2007 look and feel– Preview SP 2010 look and feel– Move to SP 2010
Visual Upgrade
20
Before Visual Upgrade
21
Visual Upgrade Options
22
After Visual Upgrade
23
Upgrade Master Pages
• Ensure that the new ContentPlaceHolder controls exist in order to update your master page to be compatible with SharePoint 2010
• Newly added Server ribbon in SharePoint 2010
• Many controls that were previously included with the default master page that have been moved into the new Server ribbon UI
• Page layouts need to be upgraded with the new “UIVersion=4” attributes (as they appear in v4.master)
• All custom master pages need to be upgraded as well
Upgrade Master Page and Page Layouts
24
Migrate Users & Permissions from MOSS 2007 to SharePoint 2010
• Classic Mode vs. Claims Based Authentication
• All upgraded web applications will use Classic Mode Authentication
• Configure claims-based authentication for Web application before attaching any databases
• FBA can only be applied on web applications using Claims Based Authentication
• Steps to migrate:– Remove web.config changes and add them back after the upgrade– Convert the existing Web applications to claims authentication (PowerShell)– Migrate users and permissions (PowerShell)
Migrate Users & Permissions
25
SharePoint elements that won’t be upgraded:• Custom Site Definitions
• Custom Site Templates
• Custom List Definitions
• Custom List Views
• Custom Field Types
• Workflow Actions– CustomWorkflowActionsFiles– ModifiedWorkflowActionsFile
• All files in 12 hive that are not deployed as part of features must be copied manually into 14 hive in SharePoint 2010 for DB Attach Upgrade
Objects that won’t be upgraded
26
• RAN BY SHarePoint Admin
• Test-SPContentDatabase– Verify whether the database is ready for upgrade
• Mount-SPContentDatabase – Start upgrade
• Upgrade-SPContentDatabase – Resume upgrade (usually used in InPlace Upgrade)
• Upgrade-SPEnterpriseSearchServiceApplication – Search
• Upgrade-SPSingleSignOnDatabase – SSO
• Export-SPInfoPathAdministrationFiles– Import InfoPath forms to the new farm
• Move-SPProfileManagedMetadataProperty– Any taxonomy data is upgraded, and you can copy the taxonomy data into a Taxonomy
database for use by the Managed Metadata service after upgrade is complete
Powershell Cmdlets
27
Upgrade from SharePoint 2003
• No direct path, requires 2007 server availability to perform 2 upgrades
28
Upgrade Tools to Consider
SharePoint 2010 Upgrade
Tools
Quest Software Migration Manager
for SharePoint
Metalogix SharePoint Site Migration Manager 2010
Tzunami Deployer for SharePoint 2010
migration
AvePoint DocAve SharePoint Migration
Manager
MetaVis Migrator for SharePoint
Xavor SharePoint 2010 Migration Tool
Axceler Davinci
29
Ironworks Blogs
• Fit & Finish: Insight from the Ironworks User Experience Group– http://fitandfinish.ironworks.com/
• Under the Hood: Insight from the Ironworks Technology Group– http://underthehood.ironworks.com/
Contact
• For further information about Microsoft SharePoint services at Ironworks, please contact – Keith Long: [email protected]
Q&A
30
Richmond10900 Nuckols RoadSuite 400 Glen Allen, VA 23060804.967.9200
Research Triangle11000 Regency ParkwaySuite 404Cary, NC 27518919.462.2092
DC Metro8133 Leesburg PikeSuite 650Vienna, VA 22182703.506.3964
Charlotte10405 Toringdon WaySuite 205Charlotte, NC 28277704.848.8889
Minneapolis6 Pine Tree DriveSuite 280Arden Hills, MN 55112651.493.2601
ironworks.com | 804.967.9200