Your SlideShare is downloading. ×
SharePoint-upgrade_15 Oct 2010
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

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.
  • Transcript

    • 1. Upcoming Event:
      SharePoint Insights
      Wired2Win Webinar Series
      Date: Oct 28th 2010
      Time: 10am – 11 am PDT
      Register at: / SPInsights
    • 2. SharePoint 2010 Upgrade: Tips, Tricks and PitfallsWired2Win Webinar Series
      Vineet Arora
      WinWire Technologies Inc.
    • 3. Agenda
      SharePoint 2010 Overview
      Upgrade process
      Best practices
    • 4. SharePoint - Evolution
    • 5. 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
      Social feedback
      Dynamic Rollup Filtering
      Site-based workflows
    • 6. Preparing For Upgrade
    • 7. Upgrade Cycle: Overview
    • 8. Upgrade Cycle: Learn
      Common issues
      Upgrade methods
      Downtime mitigation
    • 26. 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
      Visual Studio 2008 extensions for Windows SharePoint Services (VSeWSS), version 1.3
      Visual Studio 2010
    • 27. 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
    • 28. 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
    • 29. Upgrade Cycle: Prepare
    • 30. 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
    • 31. 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
    • 32. 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
    • 33. Upgrade Cycle: Test
    • 34. Upgrade Testing
      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
      Authentication providers
    • 35. Upgrade Cycle: Implement
    • 36. SharePoint 2010 Migration – Process
    • 37. Example of Operations Scheduling
      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.
    • 38. Upgrade Cycle: Validate
    • 39. 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
      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
    • 40. 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)
    • 41. Upgrade Failure Recovery
      Determine cause of failure
      Status Page & Upgrade Logs:
      Error log
      Full upgrade log
      Customizations Management Commands:
      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
    • 42. Questions