1. SharePoint 2010 Upgrade: Tips, Tricks and PitfallsWired2Win Webinar Series Vineet Arora Vineet.Arora@WinWire.com CTO WinWire Technologies Inc.

2. Agenda SharePoint 2010 Overview Upgrade process Learn Prepare Test Implement Validate Best practices

3. SharePoint - Evolution

4. New SharePoint 2010 Features There are lots of of new features that may be used to supersede controls you have implemented in your MOSS 2007 sites Server Ribbon Publish process Auto spell-check Unpublish items check One-Click page authoring Content Organizer Multilingual options Digital media Silverlight viewer Video streaming Site Asset Library Cross-browser rich text editor with valid markup No need for custom solution Metadata store upgrades Enterprise taxonomies Folksonomies Rating Tagging Social feedback Dynamic Rollup Filtering Site-based workflows

5. Preparing For Upgrade

6. Upgrade Cycle: Overview

8. Operating System

9. SQL server

10. Missing dependencies

11. UI changes

12. Lack of space

13. Forms Authentication Providers

14. In-Place

15. Database Attach

16. Content

17. Profile

18. Project

19. WID to SQL Migration

20. Read-only content databases

21. Parallel upgrades:

22. Multiple temporary farms

23. Parallel database attach

24. AAM redirectionUpgrade Cycle: Learn Common issues Prerequisites Upgrade methods Downtime mitigation

25. Hardware and System Software 64-bit all the way Hardware and system software SharePoint Server 2010 is 64-bit only SharePoint Server 2010 requires 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2 SharePoint Server 2010 requires 64-bit SQL Server 2008 or 64-bit SQL Server 2005 Development Visual Studio 2008 extensions for Windows SharePoint Services (VSeWSS), version 1.3 Visual Studio 2010

26. Best Practices Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later Ensure that the environment is fully functioning before you perform an upgrade Run the pre-upgrade checker to look for potential issues Perform a trial upgrade on a test farm first Plan for capacity Back up your environment Optimize your environment before upgrade

27. MOSS 2007 Farm services Each SSP upgrades into: A Search service app A User Profiles service app An Excel service app An App Registry back-compat service app A new managed metadata service app Web application associations are preserved A proxy is created for each service app New databases are created as needed

28. Upgrade Cycle: Prepare

29. Upgrade Planning Customer Communications Farm/Customizations Surveys Upgrade/Customizations Testing Environment Cleanup Hardware Build-out Customizations Deployment Backups Before Upgrade Operations Scheduling Rollback/Restore Plan Post-Upgrade Activities Ongoing Support Calls

30. Farm/Customizations Surveys Gather information Pre-upgrade checker (Updated in Oct 2009 CU) Manual inspection process Comparison process (WinDiff): New server with same version and patch level Compare Web Server Extensions directory Compare IIS directory Compare GAC directory Determine impact stsadm -o EnumAllWebs (Updated in Oct 2009 CU) Collect customizations stsadm -o ExportIPFSAdminObjects

31. Environment Cleanup Delete Stale Sites and Webs (Backup First ) stsadm -o DeleteSite [-force] [-gradualdelete] stsadm -o DeleteWeb [-force] Remove Extraneous Document Versions Primarily user driven, OM operations or tools help Cleanup Templates, Features, & Web Parts Primarily user driven, OM operations or tools help Repair Data Issues stsadm -o DatabaseRepair [-deletecorruption] stsadm -o ForceDeleteList stsadm -o VariationsFixupTool

32. Upgrade Cycle: Test

33. Upgrade Testing Recommendations Full survey first Test server side customizations Verify in both Visual Upgrade modes Consider preview environments Similar hardware Use real datasets Don’t ignore warnings Upgrade Issues Large lists Modified databases Customizations Authentication providers

34. Upgrade Cycle: Implement

35. SharePoint 2010 Migration – Process

36. Example of Operations Scheduling Example: Planned 36 hours outage. Up to 54 hours emergency outage if rollback is required. Downtime mitigation processes such as read-only databases can be used to reduce outage time.

37. Upgrade Cycle: Validate

38. Post-Upgrade Activities - I’ve finished upgrade, what’s next? Find and Fix Issues Missing Templates Deprecated Templates SSP Admin Site Great Plains (STSPKPL) Missing Features Deprecated Features PortalLayouts Missing Assemblies Web parts (STSPKPL) Forms Based Authentication Modify config files Fix-up user identifiers User Experience Unghosted pages Non-reghostable pages Incompatible HTML Content Issues Large/wide lists

39. Upgrade Failure Prevention Perform Farm Analysis stsadm -o PreUpgradeCheck(Updated in Oct 2009 CU) stsadm -o EnumAllWebs(Updated in Oct 2009 CU) Get Farm Healthy (Spring Cleaning) Gather/Install Server Side Customizations stsadm -o ExportIPFSAdminObjects Test Upgrade Beforehand Perform Database Content Check (optional) Test-SPContentDatabase

40. Upgrade Failure Recovery Determine cause of failure Status Page & Upgrade Logs: Error log Full upgrade log Customizations Management Commands: Test-SPContentDatabase stsadm -o EnumAllWebs Fix issue(s) Install missing or updated customizations Activate missing services; farm, web app settings Resume upgrade Farm upgrade command Content database specific upgrade command Service specific upgrade commands

41. Questions