sharepoint upgrade process

SharePoint 2010 Upgrade Approaches

SharePoint Evolution

Reasons for Upgrading SharePoint 2010

Enterprise Content TypesMetadata and Navigation

Document SetsMulti-stage Disposition

Audio & Video Content TypesRemote Blob Storage

List Enhancements

Tagging, Tag Cloud, RatingsSocial Bookmarking

Blogs and WikisMy Sites

Activity FeedsProfiles and Expertise

Org Browser

Performance Point ServicesExcel Services

Chart Web PartVisio ServicesWeb Analytics

SQL Server IntegrationPower Pivot

Ribbon UISharePoint Workspace

SharePoint MobileOffice Client & Office Web App

Integration

Business Connectivity ServicesInfoPath Form Services

External ListsWorkflow

SharePoint DesignerVisual Studio

API EnhancementsREST/ATOM/RSS

Social RelevancePhonetic Search

NavigationFAST Integration

Enhanced Pipeline

Upgrade Challenges

64 bit Hardware

Approaches

Upgrade utilities

Governance Customization

s

Downtime

BrandingUser Training

Service Applications

Fab 40 templates 3rd Party

tools

Project Team

Running 2003

Upgrade Challenges

PREPARING

Customizations

64 bit hardware

Fab 40 Template

Service Application

PLANNING

Downtime

Approach

Project Team

Governance

EXECUTING

User Training

3rd Party Tools

Branding

Upgrade Utilities

Changes to SharePoint 2010

Hardware Changes Software Changes Architecture Changes

Upgrade PathsMOSS SP2, Standard Edition

SP2010 Server, Standard Edition

MOSS SP2, Enterprise Edition

SP2010 Server, Enterprise Edition

MOSS SP2, Trial Edition SP2010 Server, Trial Edition

SP2010 Server , Standard Edition

SP2010 Server, Enterprise Edition

SP2010 Server, Trial Edition

SP2010 Server, Full Product

WSS 3.0 SP2 SP2010 Foundation

WSS 3.0 SP2 SP2010 Server

• Pre-upgrade checker

• Test-spcontentdatabase cmdlet

• PSC Diagnostics

• Merged to consolidate site collections into one database

• Upgrade-SP Enterprise Search Service Application

• Upgrade Logs

• Visual Upgrade

Upgrade Utilities & Improvements

Improvements

• SharePoint 2007 running on 64 bit and with lot of customizations

• Minimal customized SharePoint environment and have no budget for new

hardware

• Lot of content databases but want to do a speedy upgrade

• Want granular level restructuring when upgrading

Scenarios

Upgrade ApproachesIn-Place

Database Attach

Hybrid approach 1: Read

only databases

Hybrid approach 2: Detach databases

Upgrade Approaches

Size of Data

Amount of customization

Site permission

Number of Sites

Factors affecting upgrade to

SharePoint2010

In-Place Upgrade Approach

Applies if

• Currently running 64-bit hardware and software and don’t have budget for new hardware

• Can afford downtime

• Have lot of custom configurations across the form and want to preserve them

Risks

• Existing SharePoint 2007 environment cannot be accessed during upgrade

• With large database the upgrade process might take time

• There is no direct way to rollback the update

Database Attach Approach

Applies if

• Want minimal downtime

• Minimum farm configurations and have resources to redo them

• Want to combine multiple farms

• Want users to access 2007 during upgrade

Risks

• All server and farm settings have to be manually reapplied

• Possibility of new content being added to 2007 sites during upgrade

• Copying databases will take time and bandwidth

Hybrid Upgrade Approach 1 – Read Only Databases

Applies if• Want users to

access 2007 sites during upgrade

• Want minimal downtime

• Very little farm configurations

Risks• All server and farm

settings have to be manually reapplied

• Possibility of new content being added to 2007 sites during upgrade

• Copying databases

will take time and bandwidth

Hybrid Upgrade Approach 2 – In place with Database Detach

Applies if• Want minimal

downtime• Want to preserve farm

settings• Have no budget for new

hardware

Risks• Existing SharePoint

2007 environment cannot be accessed during upgrade

Upgrade Process

Plan

Pre-Upgrade

Test

Post-Upgrade

Upgrade

Important considerations Common issues• Content Size

• Downtime

• Back Out options

• Level of customization

• Desktop client updates

• Language packs

• Missing Dependencies

• Missing web.config changes

• Disc Space

• Ui Changes

• FBA

3rd Party Tools will not help with

When to go for 3rd Party Tools• 2003 to 2010

• Consolidation or Restructuring

• Scheduling

• Move to Cloud

• Migrate from Notes or similar system

• Customizations

• BDC

• SSO

• Configurations

Pre-upgrade Checklist Form a project team

Evaluate Upgrade Approaches

Plan for capacity

Develop a communication plan

Update current setup to SP2

Remove unwanted features

Run Pre-Upgrade check and fix issues

Set up new Hardware and Software

Identify customizations

User Desktop upgrade

Upgrade project team

Business Analyst

Project Manager Developers Architects Branding

SpecialistsAdminist

ratorEnd

usersDecision Makers

Best Practices

• Clean up current SharePoint environment

• Optimize large lists and content databases

• Consider restructuring content and sites

• Consider Virtualized environment

• Definitely perform test upgrades

• Backup Current Environment

• Review Upgrade Logs

• Don’t upgrade broken environment

• Split content database if possible

About IOTAP

Specializing in SharePoint upgrade and migrations

Email : info@iotap.com Web : www.iotap.com

CONNECT COMMUNICATE COLLABORATE

Engagement ModelOnsite and Offsite Model

Our Valuable ClientsOur SharePoint Works

© 2012 IOTAP provides IT Consulting and Software Services to our customers that enable them connect, communicate and collaborate effectively. We are a Microsoft Gold Certified Partner and Microsoft Cloud Accelerate Partner and use products and technologies like Office 365, Dynamics CRM, SharePoint, Silverlight, and the .Net platform to deliver robust solutions.

To upgrade to the latest and best visit : SharePoint Upgrade Planning