High Level Project Plan for the MOSS 2007 Patching Project

I was recently involved in the medium scale MOSS farm upgrade. This blog entry outlines the high level project activities required for the MOSS RTM to SP1 or latest patch or cumulative update upgrade. Hope it will be useful to anyone planning the MOSS upgrade project.

Analyze the Requirements and SharePoint farm

  • Project Kickoff Meeting
  • On boarding on Site – Desktop, Email, Badge, Remote Access
  • Gain access to SharePoint Servers and Farm environments
  • Gain the SharePoint Service and SQL accounts/passwords
  • Review the server hardware configuration, server OS versions, and software (SharePoint and SQL) versions
  • Analyze and run the health check on the SharePoint Environment – Server, Farm, SSP, Central Admin, and Index/Query/WFE/DB Servers
  • Review SharePoint Customizations

Develop Communication/ User Notification Plan

  • Identify the schedule for upgrade
  • Strategy to notify users for upgrade

Develop the Backup and Rollback Strategy

  • Review the current Backup/Restore Process
  • Develop Backup Plans
  • Develop Rollback Plans for Disaster Recovery and Customizations

Develop Deployment Plan

  • Identify the deployment team
  • Identify the users and processes that will be affected
  • Identify the servers that will be affected
  • Develop high level upgrade plan and checklists
  • Develop upgrade re-try strategy. You can force the upgrade using the psconfig command or SharePoint Products and Technologies Configuration Wizard
  • Develop upgrade monitoring strategy using upgrade logs

Develop Test Plan

  • Develop upgrade verification test cases – SharePoint/SQL versions
  • Develop upgrade validation test cases – Customizations and features are working after upgrade

Stabilize the SharePoint farm

  • Configure the SharePoint Farm to run proper services
  • Review and Resolve the application event log errors on SharePoint/SQL servers for any persistence errors
  • Review and Resolve Crawl Log Errors
  • Run the best Practices Analyzer and fix the issues found by the tool
  • Remove the erroneous or unused databases on the SQL sever
  • Verify that all the front end servers are running same patch as the server hosting central admin site.
  • Verify that Drive Configuration of the SharePoint servers is sufficient. Make sure IIS logs, SharePoint logs, and index/query locations are other than C drive.

Prepare for Production Upgrade and Migration

  • Verify no upgrade timer jobs are running on front end servers
  • Verify the permissions and accounts needed for installation. Define upgrade installation account and password. In most cases, it is farm administrator account.
  • Verify login to all the SharePoint servers with installation account
  • Verify the adequate disk space on the MOSS and SQL servers for upgrade logs, index, and installation binaries
  • Verify the hardware, software, network requirements
  • Download the installation media and create a installation source on the shared network
  • Run the orphan repair tool to remove orphaned lists and paths
  • Defragment the SharePoint databases

Perform the Backup (A minimum recommendation)

  • Backup the farm from the central administration site on the running farm – Index
  • Backup the databases prior to the upgrade on the stopped farm using SQL Server management plans – Content DBs
  • Backup the customizations on the SharePoint farm – 12-Hive directory, Inetpub directory, IIS Meta Base, GAC, and AAM settings
  • Backup the Server Image – Ghosting the front-end servers

Perform the Upgrade

  • Notify users for upgrade start
  • Bring the front-end server offline by stopping the World Wide Web Publishing Service from the services snap-in
  • Optional for DB Upgrade – Prepare and Detach the large content databases or content databases with large number of site collections. Use the STSADM preparetomove and deletecontentdb commands
  • On the server running the central admin site, Install WSS 3.0 SP1, MOSS 2007 SP1, WSS 3.0 Cumulative Update, and MOSS 2007 Cumulative Update binaries without running the SharePoint configuration wizard after each installation. At the end, Run the SharePoint Products and Technologies Configuration wizard on the server and stop when the wizard reaches the OK prompt.
  • On the all other MOSS servers in the farm, Install WSS 3.0 SP1, MOSS 2007 SP1, WSS 3.0 Cumulative Update, and MOSS 2007 Cumulative Update binaries without running the SharePoint configuration wizard after each installation. At the end, Run the SharePoint Products and Technologies Configuration wizard on the server and stop when the wizard reaches the OK prompt.
  • On the Server running central admin, complete the SharePoint Products and Technologies Configuration wizard dialog box by clicking OK. This will upgrade the database.
  • On the other MOSS servers in the farm, complete the SharePoint Products and Technologies Configuration wizard dialog box by clicking OK. This will simply connect these servers to the upgraded database.
  • Optional for DB Upgrade – Reattach and Upgrade the Content Databases. You must attach one at a time. MOSS doesn’t support multiple database upgrades at the same time. Use the STSADM addcontentdb command.
  • Reinstall the Foxit PDF IFilter
  • Bring the front-end server online by starting the World Wide Web Publishing Service from the services snap-in
  • On the SharePoint (WFE and Application) servers, verify the SP1 upgrade and Cumulative
  • Update Installation by checking upgrade logs, MOSS/WSS DLL Versions, and Central Admin Site versions.
  • On the DB servers, verify the SP1 upgrade and Cumulative Update Installation by checking SQL Schema Version
  • Test and Validate the Upgrade. Make sure upgrade didn’t wipe out any customizations. Reapply the customizations, if it’s missing anything.
  • Perform the full farm backup on the SharePoint farm after the upgrade
  • Notify users for upgrade successful
  • Kick-off the full crawl on the SharePoint farm
  • Support the Upgrade

Along with this article, here are additional resources from Microsoft.

Microsoft Upgrade Resource Center
http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

TechNet – Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

Planning and Deploying Service Pack 1 for Microsoft Office SharePoint Server 2007 in a Multi-server Environment
http://office.microsoft.com/download/afile.aspx?AssetID=AM102511281033

Checklist: Deploying Service Pack 1 for Microsoft Office SharePoint Server 2007
http://office.microsoft.com/download/afile.aspx?AssetID=AM102772401033

Advertisements
This entry was posted in Planning, SP2007 Admin. Bookmark the permalink.

2 Responses to High Level Project Plan for the MOSS 2007 Patching Project

  1. bruizcastro says:

    I am new to the migration process so bare with me….
    What do you mean by “Verify no upgrade timer jobs are running on front end servers”. How I can stop them from running? I have poked around and I can’t figure it out. I am assuming I will perform this at the MOSS farm? Thanks in advance

  2. Nik Patel says:

    it’s been long time I have posted this article.. I believe I just meant by standard upgrade timer jobs on central admin.. Just ensure there are no older upgrade jobs are running.. This is especially needed if you have recently upgraded to latest cumulative patch or service packs..

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s