Mar 25
Pre-Upgrade Procedure Considerations

This list is a high level checklist I have used a number of times when doing an upgrade of SharePoint and self reminders before I move forward with building an advanced farm.


  • Backup and image everything in your current environment
  • Build new STG environment while concurrently running the older or defunct farm
    • SharePoint 2010 is 64 bit only, so make certain your hardware supports this
    • Make certain that you install FAST and WebApps on all severs
    • Patch Everything!
  • PreUpgrade Check on previous installations of SharePoint stsadm -o preupgradecheck
    • Provisioning Tool
    • Familiarize Self with PowerShell Cmddlets
      • Test-SPContentDatabase to test the DB first!
      • Upgrade-SPContentDatabase
  • Deploy all Solutions that you know you will need!
  • Visual upgrade should have a defined switch over date; communicate this
    • 90 days
  • Execute the Attach Content DB
    • Use the real production data to identify trouble areas, determine upgrade performance, evaluate techniques, downtime, etc…
  • Create New Service Apps
  • Schedule Upgrade Process


  • Test Various Upgrade Methods
    • In-Place
    • DB Attach methods using backups
      • Preferred Method
    • Attach Content DB's (Migrate DB's one at a time to new DB)
      • Side by side gradual upgrade
  • Determine any downtime if any at all
    • Read-only will trim the UI as if all sites were marked read-only allowing users read access to the content while the upgrade takes place.
  • Validate Upgrade Cycle Process
    • Event Failures
    • Event viewer
      • ULS logs \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12 or 14\Logs
    • Use the SharePoint Health Analyzer to identify environmental problems with your installation; this SharePoint tool could be the key to your success
  • Data Issues
    • Orphaned DB's
    • BDC


There are no comments for this post.

 ‭(Hidden)‬ Blog Tools