The document outlines various SharePoint upgrade scenarios, including in-place upgrades, database attachments, and hybrid approaches, emphasizing the importance of planning and preparation for successful upgrades. It details hardware and software requirements, potential pros and cons of each upgrade method, and troubleshooting tips for common issues. A structured cutover strategy and post-upgrade support are recommended for minimizing downtime and ensuring a smooth transition.

1. SharePoint Upgrade Scenarios

2. Quick Facts
About Us Approach Partnerships
• 22nd Year • Vendor • Microsoft Gold
• Grand Rapids & Independent • VMware Enterprise
Royal Oak • Non-reseller • Citrix Silver
• 30 Staff • Professional • Cisco Registered
Services Only • Novell Gold

3. Expertise

4. Get Social with C/D/H
C/D/H Talks Tech C/D/H Tweets Tech

5. About me
Julie Boudro
Consultant
MCITP, MCTS, MCT
julieb@cdh.com
248.554.3176

6. Overview
• Determining your upgrade approach
• Preparing your upgrade approach
• Troubleshooting upgrade failures
• Cut-over strategies

7. Determine your upgrade approach
• In-place upgrade
– Development environment only
• Database attachment
– Production environments
– Ideal for minimal farm-level configurations
• Hybrid approach(es)
– Read-only with a secondary farm
– Detach database with in-place upgrade

8. In-place upgrade
Pros Cons
Great for development Difficult to revert back to previous
environment environment
Upgrades entire environment Farm is unavailable while the
including Central Admin, SSP and upgrade is running
sites
Limited control over the naming
conventions for 2010 databases
Servers must be running
Windows Server 2008 (R2)

9. Database attachment upgrade
Pros Cons
Great for environments with little Farm configurations are not
farm-level configuration upgraded from old environment
Ability to perform a test upgrade Shared Service Provider
database is not automatically
upgraded
Clean install of SharePoint 2010 Requires a “content freeze” for
the final production upgrade
Minimal downtime for end users If moving to a new SQL
environment, databases must be
copied over the network
Easy recovery in case of a failure

10. Hybrid option #1: Database
attach with read-only databases
Pros Cons
Existing farm can be accessed Existing farm is read-only
while the upgrade is occurring on
another farm
Ability to upgrade multiple site Farm configurations are not
collections / databases at the upgraded from old environment
same time
Minimal downtime to users Shared Service Provider
database is not automatically
upgraded
Easy recovery in case of failure Must copy databases over the
network if moving to a new SQL
environment

11. Hybrid option #2: In-place
upgrade with database attach
Pros Cons
Farm-wide configuration settings Hardware must be able to support
are upgraded SharePoint 2010
Database attachment supports Farm is unavailable during the
the flexibility of upgrading multiple upgrade process
sites which increases overall
upgrade time

12. Preparing your upgrade approach
Hardware / Software Requirements
Component Minimum requirement
Processor 64-bit, four cores
4 GB for developer or evaluation use
RAM 8 GB for production use in a single server or
multiple server farm
Hard disk 80 GB for system drive
Windows Server 2008 R2
SQL Server 2005 with SP2 or
Software
SQL Server 2008 R2 or
SQL Server 2012
http://technet.microsoft.com/en-us/library/cc262485.aspx#section4

13. Preparing your environment
• SharePoint 2003 > SharePoint 2007 SP2
• SharePoint 2007 SP2
• Pre-upgrade checker
– Alternate access mapping settings
– Installed elements
– Unsupported customizations
– Orphaned objects
– Valid configuration settings
– Database requirements

14. Preparing your environment
• Locate custom code
• Clean house
– Site collections
– Third-party tools
– Large databases
– Document versions

15. Troubleshooting upgrade failures
Known Upgrade Issues
– Microsoft FAB 40 templates
– Customizations
– Custom site definitions
Other Issues
– Missing customizations
– Security and permissions
– Lack of space

16. Cutover strategies
• Communication plan
• Trial upgrade
• Test upgraded environment
• Test visual upgrade
• Content freeze
• Production upgrade
• Support

17. Conclusion
• Determine the impact of an upgrade in
your environment
• Have a solid plan
• Test, test, test
• Post upgrade support plan

18. Thank You
Royal Oak Grand Rapids
306 S. Washington Ave. 15 Ionia SW
Suite 212 Suite 270
Royal Oak, MI 48067 Grand Rapids, MI 49503
p: (248) 546-1800 p: (616) 776-1600
www.cdh.com
(c) C/D/H 2007. All rights reserved