Upgrade your Server farm SharePoint 2007 to a new version, or migrate content to a new SharePoint 2010 environment. This presentation helps you plan and perform the upgrade.

1. Upgrading Microsoft Office SharePoint Server 2007 to SharePoint Server 2010 Ivan Sanders SharePoint MVP, Architect DeveloperDimension Solutions inc. Dimension Solutions inc. ivan@dimension-si.com

3. Upgrade Scenarios and Methods Supported Scenarios In-Place Upgrade Database Attach Upgrade: Content Database Profile Service Database Project Service Database Single Click Install - SQL Migration Windows Internal Database (WID) -> SQL Express 2008 + File Stream RBS Unsupported Scenarios Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2 Direct upgrade from WSS v2/SPS 2003 or earlier Side by side installation Gradual upgrade

4. In-Place Upgrade Next, next, finished Advancements Restartable! Common blocking time outs removed All sites are unavailable during upgrade Site visitors continue to use the same URLs after upgrade Does require v3 to be 64 bit Whitepaper on moving from 32 bit to 64 bit SharePoint http://technet.microsoft.com/en-us/library/dd622865.aspx Previous version must be manually removed when upgrade is complete

5. In-Place Pros/Cons Pros Cons Farm wide settings are preserved and upgraded Customizations are available in the environment after the upgrade if they are v4 compatible Servers and farms areoffline while the upgradeis in progress The upgrade proceeds continuously Existing v3 farm must support (64 bit and performance

6. Inplace Upgrade DEMO

7. Database Attach Steps Stsadm –o preupgradecheck on your 2007 farm Backup 2007 Content DB Restore to SharePoint 2010 SQL Server, using SQL Tools Test-SPContentDatabase –name wss_content_2007 –webapplication http://Team2010WebApp Mount-SPContentDatabase –name wss_content_2007 –webapplication http://Team2010WebApp

8. DB Attach Pros/Cons Pros Cons Upgrade multiple content databases at the same time Combine multiple farmsinto one farm Customizations must be transferred manually The server and farm settings are not upgraded Customizations must be transferred manually Missing customizations

9. Database Attach DEMO

10. Hybrid Approach Detach DBs Upgrade to 2010 in-place DB Attach content DBs

11. Hybrid Pros/Cons Pros Cons Farm wide settings preserved Customizations alreadyin place Multiple content databasesat the same time Non-upgraded sites(in read-only mode) whileyou upgrade the content Labor intensive Direct access to the database servers x86 is a lot of work Existing hardwaremay need replacing

12. Hybrid Approach DEMO

13. Downtime Mitigation Processes Read-only databases (v3 SP2, v4) Parallel content database upgrades Parallel upgrade farms (v4) Single farm, multiple upgrade sessions (v4) Content database attach with AAM redirection (v4) http://technet.microsoft.com/en-us/library/ee720448(office.14).aspx

14. Move DB Database Attach with AAM RedirectUser interaction model SQL SQL ? 302  http://WSS http://WSSold http://WSS WFE WFE v3 Farm v4 Farm WSS v4 Web App WSS v3 Web App SQL Instance v4 Config v3 Content v4 Content v3 Config

15. What is “Visual Upgrade” A feature that separates data upgradefrom UI upgrade Data and code upgrade happens all at once Site UI has two modes: this version andprevious version Pages and components make the decisionat runtime, and it’s safe by default

16. Why “Visual Upgrade”? IT Focus on the data Schedule flexibility Developers Clear expectations More control over legacy code and controls Users Puts the user impact into users’ hands Accommodates big shifts (ribbon)

17. Visual Upgrade DEMO

18. Core Upgrade Overview Improvement Upgrade improvement areas Predictability/reliability Diagnostic ability/logging End-user experience Admin experience Logging Upgrade logs per session(saved in same place) Error log per session ( -error.log) Separate log for just errors Shows callstacks Upgrade logs always have same columns of data making reporting easier to automate.

19. Core Upgrade Improvements Logging Upgrade logs per session(saved in same place) Error log per session ( -error.log) Separate log for just errors Shows callstacks Upgrade logs always have same columns of data making reporting easier to automate. Admin experience Visual feedback Better warning Quota handling and locked site collections Upgrade status page

20. Upgrade points to consider V3 must be Service Pack 2 or later You cannot upgrade a Trial SKU FBA web applications now use Claims in v4 Stsadm command shipped with SP2, updated with Oct 09 CU –o preupgradecheck Do Spring cleaning before you upgrade Stale sites Excessive document Versions Reorganize Site Collections into databases as necessary Plan to revisit branding http://technet.microsoft.com/en-us/sharepoint/ff420396.aspx

21. Q & A

22. Who can you trust?? The blogs I trust through all of the noise. Maurice Prather http://www.bluedoglimited.com/default.aspx Andrew Connell http://www.andrewconnell.com/blog Spence Harbarhttp://www.harbar.net Jim Duncan Heather Solomon http://www.heathersolomon.com/blog Todd Klindthttp://www.toddklindt.com/default.aspx Todd Baginskihttp://www.toddbaginski.com/blog Todd Bleekerhttp://bit.ly/edlSm5Jan Tielenshttp://weblogs.asp.net/jan Patrick Tisseghemhttp://www.u2u.info/Blogs/Patrick/default.aspx WictorWilenhttp://www.wictorwilen.se Ted Patissonhttp://blog.tedpattison.net/default.aspx Lars Fastruphttp://www.fastrup.net CarstenKeutmannhttp://keutmann.blogspot.com Keith Richie http://blog.krichie.com Bill Baer http://blogs.technet.com/b/wbaer

23. SharePoint Solution Accelerators andSystem Center PLAN SharePoint Asset Inventory Tool Microsoft System Center Capacity Planner SharePoint Capacity Planner Microsoft System Center Virtual Machine Manager Microsoft System Center Configuration Manager Microsoft System Center Microsoft System Center Configuration Manager OPERATE DELIVER Microsoft System Center Operations Manager Microsoft System Center Virtual Machine Manager SharePoint Configurator SharePoint Monitoring Toolkit