SharePoint-upgrade_15 Oct 2010


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Key MessagePresenter NotesSpeak from the slide.
  • Key MessagePresenter NotesReview what you have just discussed. This is the high-level approach that you will take to a customers upgrade.[Present from the slide]
  • Key MessageSharePoint 2010 is a 64-bit platform. This is going to be a big step for many customers.Presenter NotesHardware and System SoftwarePlan for upgrading 32-bit hardware that is currently running SharePoint 2007 to 64-bit hardware. SharePoint 2010 will only be available in a 64-bit version. Plan for upgrading 32-bit hardware that is currently running SQL Server for SharePoint 2007 storage. SharePoint 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005. Plan for upgrading your Windows Server Operating System to Windows Server 2008 64-bit or above. SharePoint 2010 will require Windows Server 2008 64-bit or above. Deploy Service Pack 2 for Windows SharePoint Service 3.0 and Service Pack 2 for SharePoint Server 2007. Service Pack 2 is a requirement for upgrading SharePoint Server 2007 to SharePoint 2010. Consider your desktop browser strategy if you have a large population of Internet Explorer 6 users. Internet Explorer 6 will not be a supported browser for SharePoint 2010. SharePoint 2010 will support a broader range of standards based browsers such as Internet Explorer 7, Internet Explorer 8 and FireFox 3.x. Development PlatformPlan for upgrading SharePoint development environments to 64 bit. The Visual Studio 2008 extensions for Windows SharePoint Services (VSeWSS), version 1.3 support 64 bit development, debugging and deployment to SharePoint Server 2007 today.Consider packaging all custom code that you deploy to SharePoint as SharePoint Solutions in WSP files. SharePoint 2010 has new technology that makes this solution deployment format more valuable. You can read about the SharePoint Solution format.Microsoft recommends Visual Studio 2008 for SharePoint Server 2007 development and Visual Studio 2010 for SharePoint 2010 development. There will be two types of upgrade provided for projects. Visual Studio 2008 SharePoint Workflow projects will be upgraded to Visual Studio 2010 and continue to work in SharePoint Server 2007. Visual Studio 2008 extensions for Windows SharePoint Services (VSeWSS) projects will be upgraded to Visual Studio 2010 and in the process will be migrated to SharePoint 2010 projects.Many of your SharePoint 2007 applications will work in SharePoint 2010. In specific cases where Microsoft deprecates an API, it will be providing detailed written guidance for developers on how to upgrade custom code, and any deprecated API’s will issue warnings on compile with recommendations for changes.
  • Key MessageTake the opportunity of an upgrade to cleanup your farm.Presenter NotesAs part of your upgrade you should take the opportunity to clean up your environment. There are a variety of stsadm command options to use.
  • SharePoint-upgrade_15 Oct 2010

    1. 1. Upcoming Event:<br />SharePoint Insights<br />Wired2Win Webinar Series<br />Date: Oct 28th 2010<br />Time: 10am – 11 am PDT<br />Register at:<br /> / SPInsights<br />
    2. 2. SharePoint 2010 Upgrade: Tips, Tricks and PitfallsWired2Win Webinar Series<br />Vineet Arora<br /><br />CTO<br />WinWire Technologies Inc.<br />
    3. 3. Agenda<br />SharePoint 2010 Overview<br />Upgrade process<br />Learn<br />Prepare<br />Test<br />Implement<br />Validate<br />Best practices<br />
    4. 4. SharePoint - Evolution<br />
    5. 5. New SharePoint 2010 Features <br />There are lots of of new features that may be used to supersede controls you have implemented in your MOSS 2007 sites<br />Server Ribbon<br />Publish process<br />Auto spell-check<br />Unpublish items check<br />One-Click page authoring<br />Content Organizer<br />Multilingual options<br />Digital media <br />Silverlight viewer<br />Video streaming<br />Site Asset Library<br />Cross-browser rich text editor with valid markup<br />No need for custom solution<br />Metadata store upgrades<br />Enterprise taxonomies<br />Folksonomies<br />Rating<br />Tagging<br />Social feedback<br />Dynamic Rollup Filtering<br />Site-based workflows<br />
    6. 6. Preparing For Upgrade<br />
    7. 7. Upgrade Cycle: Overview<br />
    8. 8. <ul><li>64 bit only
    9. 9. Operating System
    10. 10. SQL server
    11. 11. Missing dependencies
    12. 12. UI changes
    13. 13. Lack of space
    14. 14. Forms Authentication Providers
    15. 15. In-Place
    16. 16. Database Attach
    17. 17. Content
    18. 18. Profile
    19. 19. Project
    20. 20. WID to SQL Migration
    21. 21. Read-only content databases
    22. 22. Parallel upgrades:
    23. 23. Multiple temporary farms
    24. 24. Parallel database attach
    25. 25. AAM redirection</li></ul>Upgrade Cycle: Learn<br />Common issues<br />Prerequisites<br />Upgrade methods<br />Downtime mitigation<br />
    26. 26. Hardware and System Software<br />64-bit all the way<br />Hardware and system software<br />SharePoint Server 2010 is 64-bit only<br />SharePoint Server 2010 requires 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2<br />SharePoint Server 2010 requires 64-bit SQL Server 2008 or 64-bit SQL Server 2005 <br />Development<br />Visual Studio 2008 extensions for Windows SharePoint Services (VSeWSS), version 1.3<br />Visual Studio 2010 <br />
    27. 27. Best Practices<br />Update your servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later<br />Ensure that the environment is fully functioning before you perform an upgrade<br />Run the pre-upgrade checker to look for potential issues<br />Perform a trial upgrade on a test farm first<br />Plan for capacity<br />Back up your environment<br />Optimize your environment before upgrade<br />
    28. 28. MOSS 2007 Farm services<br />Each SSP upgrades into:<br />A Search service app<br />A User Profiles service app<br />An Excel service app<br />An App Registry back-compat service app<br />A new managed metadata service app<br />Web application associations are preserved<br />A proxy is created for each service app <br />New databases are created as needed<br />
    29. 29. Upgrade Cycle: Prepare<br />
    30. 30. Upgrade Planning<br />Customer Communications<br />Farm/Customizations Surveys<br />Upgrade/Customizations Testing<br />Environment Cleanup<br />Hardware Build-out<br />Customizations Deployment<br />Backups Before Upgrade<br />Operations Scheduling<br />Rollback/Restore Plan<br />Post-Upgrade Activities<br />Ongoing Support Calls<br />
    31. 31. Farm/Customizations Surveys <br />Gather information<br />Pre-upgrade checker (Updated in Oct 2009 CU)<br />Manual inspection process<br />Comparison process (WinDiff):<br />New server with same version and patch level<br />Compare Web Server Extensions directory<br />Compare IIS directory<br />Compare GAC directory<br />Determine impact<br />stsadm -o EnumAllWebs (Updated in Oct 2009 CU)<br />Collect customizations<br />stsadm -o ExportIPFSAdminObjects<br />
    32. 32. Environment Cleanup<br />Delete Stale Sites and Webs (Backup First )<br />stsadm -o DeleteSite [-force] [-gradualdelete]<br />stsadm -o DeleteWeb [-force] <br />Remove Extraneous Document Versions<br />Primarily user driven, OM operations or tools help<br />Cleanup Templates, Features, & Web Parts<br />Primarily user driven, OM operations or tools help<br />Repair Data Issues<br />stsadm -o DatabaseRepair [-deletecorruption]<br />stsadm -o ForceDeleteList<br />stsadm -o VariationsFixupTool<br />
    33. 33. Upgrade Cycle: Test<br />
    34. 34. Upgrade Testing<br />Recommendations<br />Full survey first<br />Test server side customizations<br />Verify in both Visual Upgrade modes<br />Consider preview environments<br />Similar hardware<br />Use real datasets<br />Don’t ignore warnings<br />Upgrade Issues<br />Large lists<br />Modified databases<br />Customizations<br />Authentication providers<br />
    35. 35. Upgrade Cycle: Implement<br />
    36. 36. SharePoint 2010 Migration – Process<br />
    37. 37. Example of Operations Scheduling<br />Example:<br />Planned 36 hours outage.<br />Up to 54 hours emergency outage if rollback is required.<br />Downtime mitigation processes such as read-only databases can be used to reduce outage time.<br />
    38. 38. Upgrade Cycle: Validate<br />
    39. 39. Post-Upgrade Activities - I’ve finished upgrade, what’s next?<br />Find and Fix Issues<br />Missing Templates<br />Deprecated Templates<br />SSP Admin Site<br />Great Plains (STSPKPL)<br />Missing Features<br />Deprecated Features<br />PortalLayouts<br />Missing Assemblies<br />Web parts (STSPKPL)<br />Forms Based Authentication<br />Modify config files<br />Fix-up user identifiers<br />User Experience<br />Unghosted pages<br />Non-reghostable pages<br />Incompatible HTML<br />Content Issues<br />Large/wide lists<br />
    40. 40. Upgrade Failure Prevention<br />Perform Farm Analysis<br />stsadm -o PreUpgradeCheck(Updated in Oct 2009 CU)<br />stsadm -o EnumAllWebs(Updated in Oct 2009 CU)<br />Get Farm Healthy (Spring Cleaning)<br />Gather/Install Server Side Customizations<br />stsadm -o ExportIPFSAdminObjects<br />Test Upgrade Beforehand<br />Perform Database Content Check (optional)<br />Test-SPContentDatabase<br />
    41. 41. Upgrade Failure Recovery<br />Determine cause of failure<br />Status Page & Upgrade Logs:<br />Error log<br />Full upgrade log<br />Customizations Management Commands:<br />Test-SPContentDatabase<br />stsadm -o EnumAllWebs<br />Fix issue(s)<br />Install missing or updated customizations<br />Activate missing services; farm, web app settings<br />Resume upgrade<br />Farm upgrade command<br />Content database specific upgrade command<br />Service specific upgrade commands<br />
    42. 42. Questions<br />